Bug 205728 - up2date need restorecon in %post but have no dependency to policycoreutils
Summary: up2date need restorecon in %post but have no dependency to policycoreutils
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Clifford Perry
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-08 09:07 UTC by Klaus Ethgen
Modified: 2012-06-20 16:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 16:16:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Klaus Ethgen 2006-09-08 09:07:11 UTC 
Description of problem:
up2date need restorecon in %post but have no dependency to policycoreutils

How reproducible:
rpm -e policycoreutils
rpm -i up2date-*.rpm

Actual results:
/var/tmp/rpm-tmp.33832: line 11: restorecon: command not found
error: %post(up2date-4.4.69-25.i386) scriptlet failed, exit status 127
Comment 1 Red Hat Bugzilla 2007-04-12 01:12:30 UTC 
User bnackash's account has been closed
Comment 2 Pradeep Kilambi 2007-05-22 22:15:30 UTC 

*** This bug has been marked as a duplicate of 214305 ***
Comment 3 Klaus Ethgen 2007-05-23 05:56:23 UTC 
It is not a good Idea to close this bug as the duplicate bug 214305 is not 
accessable!

Please close the other bug or make them world readable.
Comment 4 Jiri Pallich 2012-06-20 16:16:52 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.
Note You need to log in before you can comment on or make changes to this bug.