Bug 188356 - libbeable headers corrupt, cannot upgrade
libbeable headers corrupt, cannot upgrade
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: beagle (Show other bugs)
5
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-08 07:33 EDT by Bill Jones
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-06-21 05:43:53 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)
text file of actual output (281 bytes, text/plain)
2006-04-08 07:33 EDT, Bill Jones
no flags Details

  None (edit)
Description Bill Jones 2006-04-08 07:33:07 EDT
Description of problem:
http://download.fedoraproject.org/pub/fedora/linux/core/development/i386/Fedora/RPMS/libbeagle-0.2.3-5.i386.rpm:

[Errno -1] Header is not complete.
Trying other mirror.
Error: failure: Fedora/RPMS/libbeagle-0.2.3-5.i386.rpm from development: 
[Errno
256] No more mirrors to try.


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

How reproducible:
everytime =(

Steps to Reproduce:
1. su - -c "yum upgrade"
  
Actual results:
http://download.fedoraproject.org/pub/fedora/linux/core/development/i386/Fedora/RPMS/libbeagle-0.2.3-5.i386.rpm:

[Errno -1] Header is not complete.
Trying other mirror.
Error: failure: Fedora/RPMS/libbeagle-0.2.3-5.i386.rpm from development: 
[Errno
256] No more mirrors to try.


Expected results:
yum upgrade of beagle would actually work

Additional info:
none.
Comment 1 Bill Jones 2006-04-08 07:33:07 EDT
Created attachment 127504 [details]
text file of actual output
Comment 2 Alexander Larsson 2006-06-21 05:43:53 EDT
This is certainly not a beagle bug. More of a yum server settup issue. I haven't
seen more reports of it though, and we've released later versions, so I'm
closing this.

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