Bug 22669

Summary: up2date crash
Product: [Retired] Red Hat Linux Reporter: Thiago Vinhas <tvinhas>
Component: up2dateAssignee: Preston Brown <pbrown>
Status: CLOSED WORKSFORME QA Contact: Aaron Brown <abrown>
Severity: high Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-12-21 15:55:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Thiago Vinhas 2000-12-21 15:55:31 UTC

I was using up2date to download the glibc-devel-2.2-9.i386.rpm package using the command up2date -u (I'm registered with the RedHat Network). When it was on something about 70/75 % it has crashed. Here is the complete output:

[thiago@sampa-novo ~]$ up2date -u

Retrieving list of all available packages...

Removing installed packages from list of updates...
Removing packages marked to skip from list...
Getting headers for available packages...
Removing packages with files marked to skip from list...
Testing package set / solving RPM inter-dependencies...
The following packages were added to your selection to satify dependencies:
Name                                    Version        Release
kernel-headers                          2.4.0          0.26
Retrieving selected packages.
Traceback (innermost last):
  File "/usr/local/sbin/up2date", line 394, in ?
  File "/usr/local/sbin/up2date", line 377, in main
    sys.exit(batchRun(onlyList, pkgNames, fullUpdate))
  File "/usr/local/sbin/up2date", line 231, in batchRun
    res = up2date.hasBadSignature(pkg)
  File "/usr/share/rhn/up2date/up2date.py", line 809, in hasBadSignature
    hdr = rpm.headerFromPackage(fd)[0]
rpm.error: error reading package

Comment 1 Preston Brown 2000-12-27 21:54:04 UTC
Is the error repeatable?  I.e. does it happen consistently?  

If so, please remove all files in /var/spool/up2date and try again.  If the 
error still persists, re-open this bug.  Also, please make sure you have the 
latest errata version of Up2date.