Closed
Bug 579530
Opened 14 years ago
Closed 13 years ago
be able to rpm -e scratchbox safely
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jhford, Assigned: rail)
References
Details
The currently deployed 'scratchbox' rpm has a %postun that really should be a %preun. This is broken because the actions in %postun absolutely need to be run before installation and are invalid after uninstall. They should also probably be run %preinst for good measure. The currently known issue with this is that running rpm -e scratchbox will cause /tmp to become 755 instead of 777 for the entire system (not just scratchbox!) which breaks lots of things. This is not a comprehensive list of issues that this will cause
Comment 1•14 years ago
|
||
Since we never run 'rpm -e' on production systems this is low priority.
Priority: -- → P5
Updated•13 years ago
|
Reporter | ||
Comment 2•13 years ago
|
||
actually, we need to fix this to properly uninstall scratchbox without totally horking the boxes its installed on.
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Summary: scratchbox rpm %postun should be %preun → be able to rpm -e scratchbox safely
Assignee | ||
Comment 3•13 years ago
|
||
As a workaround we can run the postinst script manually (or via puppet) and then run rpm -e --noscripts.
Assignee: nobody → rail
Priority: P5 → P2
Assignee | ||
Comment 4•13 years ago
|
||
Bug 548551 removes scratchbox from the slaves w/o using RPM scripts as a work around.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•