Bug 97670 - up2date fails because it can't find a header file on the server
up2date fails because it can't find a header file on the server
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
7.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-06-18 19:42 EDT by Joe Maus
Modified: 2007-04-18 12:54 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-20 16:57:06 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)

  None (edit)
Description Joe Maus 2003-06-18 19:42:32 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
I'm trying to create a new 7.0 server and while updating the system to 
the "current" release it fails.  I do not know what file is missing as that is 
not provided in the error message nor am I able to find any logs to indicate 
what it was trying to do when it failed. The error is:

Error - package not found - code 17 - file not found

The last header it downloaded was:

losetup-2.10r-5.i386.hdr

It used to fail on lynx - but I removed that package from the server since I 
did not need it.  

I have scheduled an update and hopefully it might provide more data once that 
runs.  This used to work, at least a few months ago it did.

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

How reproducible:
Always

Steps to Reproduce:
1. install 7.0 on a server (custom install - basically a server install expect 
install X, smb client and server, www, and e-mail.
2. register with RHN
3. run up2date - it fails about 37% of the way through the headers
    

Actual Results:  Up2date reports a failure (see above)

Expected Results:  Up2date should have told me what file it could not find - 
but it does not.

Additional info:  I have searched the archives and have found older reports of 
this kind - but nothing recent.  This suggests there is a server side problem.

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