Hi, On Wed, Jun 24, 2009 at 12:42:00PM -0500, David C. Rankin wrote:

Listmates, Peter:

I have experienced a Yast SW Management update package failure that stops the update process:

Subprocess failed. Error: RPM failed: install-info: menu item `gcc' already exists, for file `gcc' error: %post(gjdoc-0.7.9-2.10.noarch) scriptlet failed, exit status 1

Frustrating part is that when you start an update that will take several hours, leave and then check back hours later (like at lunchtime) only to find the update has stopped at 17% and you still have hours to go :(

I guess this is just a bad gjdoc rpm that needs to be rebuilt.

Yes, and it may have a packaging error that needs to be fixed, so a rebuild might not suffice. Such packaging errors can get in the way, yes, and there is not much of a way around it sometimes. (Your options being: reporting the bug / uninstalling the package / updating manually (--force/--nodeps/--noscripts are your friends) Not really a bug in the software management. Although one could argue that yast shouldn't abort but rather continue with the other packages. So in a way, it could be seen as a bug. I believe that yum wouldn't abort (from memory, I didn't check). As the file in question is /repositories/Java:/packages/openSUSE_11.0/noarch/gjdoc-0.7.9-2.10.noarch.rpm, it is a build service package built for openSUSE 11.0 where not necessarily somebody is available to keep it in good shape all the time, nevertheless I would suggest to report the bug to the maintainers of the Java:packages project. % osc maintainer Java:packages | tail -1 mvyskocil, mvyskocil Michal Vyskocil Cc'ed :-)

P.S. kde4.3 Beta 2, just keeps getting better! It should be in great shape for 11.2.

Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development