From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040626 Firefox/0.9.1

Description of problem:
One of the package headers in /var/spool/up2date got cut short
(probably network failure).  up2date would silently die while trying
to load the package headers afterward.  Running up2date --nox
<package> would result in a message box being displayed saying
"Unknown Error" (the message box being displayed while the --nox flag
is not the bug being addressed here).  Turning on debugging and
verbose output revealed that it was stopping after reading a small
number of headers.  Re/moving the headers will force them to be
redownloaded and works around the problem.

up2date should at least state that it failed to load a package header
from the disk, and which header it was trying to load.  It would be
better, though if it tried to re-download a file that couldn't be
loaded properly and only give a warning message if the download failed
then tried to continue on, ignoring the damaged package.

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


How reproducible:
Always

Steps to Reproduce:
1. mv /var/spool/up2date/XFree86-Xvfb-4.3.0-68.EL.i386.hdr
/var/spool/up2date/XFree86-Xvfb-4.3.0-68.EL.i386.hdr.orig
2. head -c 123244
/var/spool/up2date/XFree86-Xvfb-4.3.0-68.EL.i386.hdr.orig
>/var/spool/up2date/XFree86-Xvfb-4.3.0-68.EL.i386.hdr
3. up2date
    

Actual Results:  up2date would die while trying to read the package
headers.

Expected Results:  up2date would try to work around the damaged
package header, and would not crash.

Additional info: