[opensuse-factory] Access denied to bugzilla and running Factory day to day
Hello everybody, First a bit on my background: I've been running openSUSE for a year, and switched almost exclusively (have a 12.2 chroot that I only had to use once) to Factory on my home system for about 2 months now (too brave? until now it worked great). The plan was to run the lastest software, help by reporting bugs, learn more about packaging and OBS and maybe try to help with some SRs. So far this has worked great, I did all of the above except reporting bugs (I'm only affected by one that I'll report soon). I do zypper dup every day, sometimes it complains about problems. If that happens I cancel the update and try again the next day, usually in at most a few days it gets into an upgradable state again. However, it's been a while since I get: Problem: marble-4.8.5-1.7.x86_64 requires marble-data = 4.8.5, but this requirement cannot be provided Looking at this, it seems plasma-addons stayed at 4.8.5 and it requires marble-4.8.5 which is gone. Why did plasma-addons stay at 4.8.5? Because SR [1] was declined by somebody in the legal team. The decline reason points to [2] where I get: You are not authorized to access bug #779736. That's not very nice, I'm now completely in the dark as to why plasma-addons wasn't upgraded and how long will it keep blocking the rest of my upgrade. I understand that the legal issues might be sensitive but I have a feeling this time they're not and I think it's bad to split the community into SUSE employees that can see everything and "the rest". Exactly at this point I want to postpone the upgrade anyway until the Xorg and Mesa issues Coolo pointed out get fixed (thanks for that by the way! very important for people testing day to day to avoid major breakage if it's already known) but the principle remains: everybody should be able to see why a SR got rejected to know what can be done about it to move forward. To summarize: * having some bugs available just to SUSE employees is in my opinion bad * what should happen to plasma-addons so that it gets upgraded to 4.9.1? * am I doing things correctly to stay on top of Factory? are others doing the same? is Factory meant to be used day to day if you have some troubleshooting and system recovery skills? * thanks for a great distribution, and a very stable development version of it, keep up the good work! [1] https://build.opensuse.org/request/show/133585 [2] https://bugzilla.novell.com/show_bug.cgi?id=779736 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 20.09.2012 23:36, Catalin Iacob wrote:
Looking at this, it seems plasma-addons stayed at 4.8.5 and it requires marble-4.8.5 which is gone. Why did plasma-addons stay at 4.8.5? Because SR [1] was declined by somebody in the legal team. The decline reason points to [2] where I get: You are not authorized to access bug #779736.
The legal bugs are private between the legal team and those that can fix it. It's a bit paranoid default, but it is as it is.
To summarize: * having some bugs available just to SUSE employees is in my opinion bad
This is not about SUSE employees. Legal bugs can't be seen by SUSE employees either. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sep 21, 12 10:56:50 +0200, Stephan Kulow wrote:
On 20.09.2012 23:36, Catalin Iacob wrote:
Looking at this, it seems plasma-addons stayed at 4.8.5 and it requires marble-4.8.5 which is gone. Why did plasma-addons stay at 4.8.5? Because SR [1] was declined by somebody in the legal team. The decline reason points to [2] where I get: You are not authorized to access bug #779736.
The legal bugs are private between the legal team and those that can fix it. It's a bit paranoid default, but it is as it is.
Catalin, if you want to take action here, I've added you to #779736. One could argue that the issue is not new, and we should allow the update, while the issue is being discussed. (Ciaran will beat me for suggesting this). cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 say #263A!__/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Jeff Hawn, J.Guild, F.Imendoerffer, HRB 16746 (AG Nuernberg), Maxfeldstrasse 5, 90409 Nuernberg, Germany SuSE. Supporting Linux since 1992. ☺ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 20 Sep 2012 23:36:42 Catalin Iacob wrote:
To summarize: * having some bugs available just to SUSE employees is in my opinion bad
I think most contributers have felt this way about BNC bugzilla at one point or another; but the legalese of a bug notwithstanding, I recognise that many of the openSUSE lead honcho's have taken care and effort in the last couple of years to try and open up as many internal bug reports as possible to the community. In addition to this type of issue related to legality, there's another class of bug that you might occasionally find yourself unable to view... Security issues often have an embargo on disclosure to allow support teams to prepare an update. While I personally would rather have immediate knowledge of the issue, I understand that I have to swallow a small amount of time based obfuscation for the greater good. Gladly, I think the frustration you found in this bug report has now become the exception rather than the norm and I think AJ, coolo and others inside suse and novell have helped encourage this ethos of sharing internal reports with the greater community. For your own sanity it's worth keeping an eye on the annoying bugs[1]
* what should happen to plasma-addons so that it gets upgraded to 4.9.1?
If you don't get a direct answer to this you can ask on #opensuse-kde IRC or opensuse-kde@ mailing list.
* am I doing things correctly to stay on top of Factory? are others doing the same? is Factory meant to be used day to day if you have some troubleshooting and system recovery skills?
Many people live at the cutting/bleeding edge of factory. If you examine individual packages via 'osc'[2] (latest from openSUSE:Tools repo), or the web based client for the build service[3], you can notice that almost every package in factory has it's own 'devel' project where most of the heavy lifting and development is done. For the most part, maintainers submit known working states of their packages to factory and the factory project maintainers and autogroups handle the integration. When theres significant and predictable problems such as the mesa/xorg issue or a new gcc or such like, we get a heads up on the factory ML. In short, if you know your way around your system you will probably not have any significant problems using factory ;) [1] http://en.opensuse.org/openSUSE:Most_annoying_bugs [2] http://en.opensuse.org/openSUSE:OSC [3] https://build.opensuse.org/project/show?project=openSUSE:Factory -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Sep 22, 2012 at 1:34 PM, Graham Anderson <graham.anderson@gmail.com> wrote:
In short, if you know your way around your system you will probably not have any significant problems using factory ;)
Thanks for the clear reply Graham. It's in line with what I thought but it's good to have confirmation. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Catalin Iacob -
Graham Anderson -
Juergen Weigert -
Stephan Kulow