be able to rpm -e scratchbox safely

RESOLVED WONTFIX

Status

Release Engineering
General
P2
normal
RESOLVED WONTFIX
8 years ago
4 years ago

People

(Reporter: jhford, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

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
Since we never run 'rpm -e' on production systems this is low priority.
Priority: -- → P5
Blocks: 701113
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
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
Blocks: 548551
(Assignee)

Comment 3

6 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

6 years ago
Bug 548551 removes scratchbox from the slaves w/o using RPM scripts as a work around.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.