https://bugzilla.novell.com/show_bug.cgi?id=402435 User gilles.sabourin@free.fr added comment https://bugzilla.novell.com/show_bug.cgi?id=402435#c1 --- Comment #1 from Gilles Sabourin 2008-06-21 12:09:57 MDT --- As soon as KDE session opens, updater icon is grey and updater returns the message : "System is busy : another check will start soon". After a short while it shows a triangle an returns Exit Status: 127 I put a "set -x" in shell script /usr/sbin/zypper_install to track the bug, but the script exhibits no error : problem's origin does not come from the way zypper is launched, but instead by a problem encountered by zypper itself. I have no clue to go further. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=402435 User tgoettlicher@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=402435#c3 Thomas Göttlicher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bnc-team-gnome@forge.provo.novell.com AssignedTo|tgoettlicher@novell.com |jkupec@novell.com --- Comment #3 from Thomas Göttlicher 2008-06-23 02:23:15 MDT --- Obviously a gnome update has broken zypper's dependencies. Jano, do you know how to fix? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=402435 User gilles.sabourin@free.fr added comment https://bugzilla.novell.com/show_bug.cgi?id=402435#c5 Gilles Sabourin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|gilles.sabourin@free.fr | --- Comment #5 from Gilles Sabourin 2008-06-26 12:00:20 MDT ---

You could try "verify system" function in YaST Software Management (i hope the 10.3 version has it).You could try "verify system" function in YaST Software Management (i hope the 10.3 version has it). No, it cannot work because this function checks only a few package set. If this function corrects that set, it'll bring regressions on other libraries not involved in the downgrading process (maybe you may even be blocked by dependencies). More safer and faster : a 10.3 format and complete reinstallation. But whenever you spend hours to build a development environment, this solution can't be a way.

As for this bug, what is it you want us to be fixed here? The object of the bug report is the updater applet functionality. I have no more security notifications, but I got a simple yellow triangle.

Didn't it tell you there are some dependency issues before performing the update? There are always dependencies problems with yast : how can I check whenever hundred of packages are to be updated? I'm trying to force since in the most cases, they are false positives : yast does not handle properly all uninstallation / installations cases.

What repositories did you use? GNOME:STABLE. This repository is also a nightmare dependencies, since there is always some applications not updated together with the updated libraries set. For example, an update can easily break evolution, ekiga, control-center2 ... just because they have not been build at the same time. This should your job to check that.

The last GNOME:STABLE update for 10.2 was even not applicable because of conflicts with whole KDE3 ! The simple user can easily check to activate GNOME:STABLE repository in community repositories and update from it, and hence you can't say anymore that GNOME:STABLE usage is for experimented users only! I am switching now to openSUSE 11.0 to avoid this problem ... until next GNOME:STABLE update for 11.0 ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=402435 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=402435#c7 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #7 from Ján Kupec 2008-07-08 10:31:40 MDT --- So you probably mean this OpenSUSE Build Service repository: http://download.opensuse.org/repositories/GNOME:/STABLE/ OK, so this indeed is a bug in the packages in that repo, not much we can do in zypper. So back to your comment #2: (In reply to comment #2 from Gilles Sabourin)

What I am supposed to do now ? are you aware you have to check your updates, especially gnome updates ???

Just to be sure: are you aware that with OBS repos, you're on your own? What we do check is installation/upgrade of stable releases + applying official updates from software.opensuse.org. All the rest is out of our scope. If you feel our tools don't work with such repos very much, this bugzilla is the place to complain/suggest how it should be, but this time it is just a broken community repository. That is between you and the maintainers of that repo and their will/spare time to do something about it. Please contact some of the maintainers directly if it's still a problem, you'll find them here: https://build.opensuse.org/project/show?project=GNOME%3ASTABLE Log in using your bugzilla account. (In reply to comment #5 from Gilles Sabourin)

...

Didn't it tell you there are some dependency issues before performing the update? There are always dependencies problems with yast : how can I check whenever hundred of packages are to be updated? I'm trying to force since in the most

You must expect something like this when updating so many packages from repos like gnome:stable (which is hundreds of 11.0 packages applied to 10.2 or 103). You should always check the

cases, they are false positives : yast does not handle properly all uninstallation / installations cases.

Of course, the possibilities are quite huge, we can only focus on some use cases as i mentioned above.

The simple user can easily check to activate GNOME:STABLE repository in community repositories and update from it, and hence you can't say anymore that GNOME:STABLE usage is for experimented users only!

Perhaps we can't say this, but we can say we do not support this use case. You're on your own.

I am switching now to openSUSE 11.0 to avoid this problem ... until next GNOME:STABLE update for 11.0 ?

If you want to avoid these problems, stick with the stable release. If you want new gnome packages, expect some troubles with the update. Note that i don't speak for the GNOME:STABLE maintainers, they may have other opinion on this, but i speak from the package management point of view. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=402435 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=402435#c9 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jkupec@novell.com |sbrabec@novell.com Status|REOPENED |NEW --- Comment #9 from Ján Kupec 2008-07-09 01:16:52 MDT --- (In reply to comment #8 from Gilles Sabourin)

RESOLVED INVALID? Why bug #402433 has been accepted and treated then, with same problem origin, but with more serious side effects (HAL was broken) ?

I don't know. Please ask Stanislav Brabec, the one responsible for that but I would guess because he, and the GNOME:STABLE team wants to keep the repo in good shape.

...

If you want to avoid these problems, stick with the stable release. If you want new gnome packages, expect some troubles with the update. You mean that GNOME:STABLE releases are not stable releases?

I mean updating 10.2 or 10.3 system with gnome packages from 11.0 (current GNOME:STABLE state) is not an officially supported use case and it is meant as a service for those who want to take the pain of resolving the problems with it. If you saw bug #402433 fixed, it was probably a good will of the assignee or the GNOME:STABLE team.

And you made no answer about comment #6; I suggest that you remove libicu 3.8

I did - i suggested to tell this to some of the maintainers of that OBS repository. OK, Standa Brabec is one of them, reassigning to him. But keep in mind he does not have to fix this, so avoid ranting like "What I am supposed to do now ? are you aware you have to check your updates, especially gnome updates ???". Stando, correct me if i'm wrong about the purpose of the GNOME:STABLE OBS project. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.