Bug 199838 - Missing *.pyc files after yum upgrade
Summary: Missing *.pyc files after yum upgrade
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-soundcard
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Martin Stransky
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-23 05:29 UTC by Jim Cornette
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-07-24 12:12:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jim Cornette 2006-07-23 05:29:52 UTC
Description of problem:
After upgrading from an installed package to a newer version of the package,
some .pyc files are missing when querying the rpm database. Previous bugs were
filed for other s-c-* packages. This package still exhibits the problem.
The problem seems to happen because some files that are already owned by the
package are rm *.pyc during the cleanup stage of rpm.

Version-Release number of selected component (if applicable):
system-config-soundcard-2.0.1-1

How reproducible:
Upgrade system via pup or yum

Steps to Reproduce:
1. run yum update
2. rpm -qaV |grep missing >rpm-missing.txt
3. review file for results
  
Actual results:
missing     /usr/share/system-config-soundcard/probeCard.pyc
missing     /usr/share/system-config-soundcard/soundcard.pyc
missing     /usr/share/system-config-soundcard/soundcardBackend.pyc
missing     /usr/share/system-config-soundcard/soundcardBackendHal.pyc
missing     /usr/share/system-config-soundcard/soundcardBackendKudzu.pyc
missing     /usr/share/system-config-soundcard/soundcardBackendProc.pyc
missing     /usr/share/system-config-soundcard/soundcardBackendSoundCard.pyc
missing     /usr/share/system-config-soundcard/system-config-soundcard.pyc


Expected results:
Query to come back with no problems detected.

Additional info:
mozilla and s-c-* rpms seem to be the highest failures.


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