Bug 155282 - "Rpm Exception" on update while installing apparmor-utils package
Summary: "Rpm Exception" on update while installing apparmor-utils package
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Beta 6
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Dominic W Reynolds
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-04 11:59 UTC by Christian Boltz
Modified: 2006-05-12 22:38 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
screenshot showing the full error message (30.29 KB, image/png)
2006-03-04 11:59 UTC, Christian Boltz 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2006-03-04 11:59:11 UTC 
I got an error message on update from beta3 to beta6 saying "apparmor-utils-2.0.9 is already installed".

I'll attach a screenshot showing the full error message. 

You can find the y2logs at
https://bugzilla.novell.com/attachment.cgi?id=71245&action=view

rpm -q lists two apparmor-utils packages:
# rpm -q apparmor-utils
apparmor-utils-2.0-5
apparmor-utils-2.0-9
Comment 1 Christian Boltz 2006-03-04 11:59:57 UTC 
Created attachment 71246 [details]
screenshot showing the full error message
Comment 2 Klaus Kämpf 2006-03-04 12:20:59 UTC 
Hmm, seems to be a packaging bug of the installed 2.0-5 package:

Subprocess failed. Error: RPM failed: Shutting down
preun(apparmor-utils-2.0-5.noarch) scriptlet failed, exit status 7

So rpm refuses to uninstall it when upgrading to 2.0-9

(Beta->Beta upgrades are not 'officially' supported ;-) )
Comment 3 Seth R Arnold 2006-04-07 22:26:02 UTC 
Christian, thanks for the report. Package upgrades have flaky, but we believe that we have the upgrade logic correct now.

Please re-open if this bug re-appears; thanks.
Comment 4 Christian Boltz 2006-05-12 22:38:12 UTC 
I didn't see any more error messages about this in later betas and the RCs :-)

Thanks for fixing this!