Bug 153291 - RHEL-3 up2date creates rpm -v clutter
RHEL-3 up2date creates rpm -v clutter
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: up2date (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Connor
Beth Nackashi
:
Depends On:
Blocks: 155571 156320
  Show dependency treegraph
 
Reported: 2005-04-04 11:17 EDT by Neil Horman
Modified: 2014-03-30 21:38 EDT (History)
5 users (show)

See Also:
Fixed In Version: RHBA-2005-712
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-28 13:15:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch of fc-2 spec file change to prevent up2date from recompiling pyc files after install (825 bytes, patch)
2005-04-04 11:17 EDT, Neil Horman
no flags Details | Diff

  None (edit)
Description Neil Horman 2005-04-04 11:17:50 EDT
Description of problem:
This is a duplicate ticket of bz#69205.  A customer has noted that when up2date
runs, it recompiles its pyc files, and as such rpm -v reports them as modified.
 This has been corrected in FC-2 forward, and the customer  would like the fix
backported to RHEL-3

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. install up2date
2. run up2date
3. run rpm -v up2date
  
Actual results:
up2date modifies its pyc file, and rpm reports the change

Expected results:
up2date should avoid recompiling these files.

Additional info:
Comment 1 Neil Horman 2005-04-04 11:17:51 EDT
Created attachment 112653 [details]
patch of fc-2 spec file change to prevent up2date from recompiling pyc files after install
Comment 6 Adrian Likins 2005-05-16 14:06:55 EDT
u6 will get up2date 4.4.x, which solves this issues
Comment 7 Debbie McGrath 2005-06-08 10:18:49 EDT
This bug is considered MustFix for RHEL 3 U6 by RHN Engineering.
Comment 9 Debbie McGrath 2005-06-21 17:24:35 EDT
Dev & PM ACKs for U6
Comment 13 Beth Nackashi 2005-07-04 12:31:36 EDT
Retested against up2date-4.4.23-3:

[root@test07 root]# rpm -q up2date
up2date-4.4.26-3
[root@test07 root]# up2date -uf

Fetching Obsoletes list for channel: rhel-i386-as-3...

Fetching Obsoletes list for channel: rhn-tools-rhel-3-as-i386...

Fetching Obsoletes list for channel: redhat-rhn-proxy-4.0-as-i386-3...

Fetching Obsoletes list for channel: playpen-4AS...

Fetching Obsoletes list for channel: support-4AS...

Fetching Obsoletes list for channel: playpen-3AS...

Fetching Obsoletes list for channel: support-3AS...

Fetching Obsoletes list for channel: playpen-java-3AS...

Name                                    Version        Rel     
----------------------------------------------------------

All packages are currently up to date

[root@test07 root]# rpm -Vf /usr/bin/up2date
SM5....T c /etc/sysconfig/rhn/up2date
S.5....T c /etc/sysconfig/rhn/up2date-uuid

(/etc/sysconfig/rhn/sources is missing ... bug 162071)

This shows that the up2date config files were changed.  This is ok, right?  I
don't have output stating what this should look like ... and since
/usr/share/rhn/up2date_client/up2date.pyc is not in the rpm -Vf output, this bug
is probably fixed.  But I need confirmation that this output is correct.
Comment 14 Bastien Nocera 2005-07-05 09:26:02 EDT
This looks good indeed.
Comment 15 Beth Nackashi 2005-07-05 12:13:03 EDT
thanks, moving to PROD_READY
Comment 16 Todd Warner 2005-09-23 17:44:29 EDT
PROD_READY is a deprecated state. This bug is now RELEASE_PENDING.
Comment 17 Red Hat Bugzilla 2005-09-28 13:15:49 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-712.html

Note You need to log in before you can comment on or make changes to this bug.