Bug 22003 - up2date fails to "Get Header for Avail Packages"
Summary: up2date fails to "Get Header for Avail Packages"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 7.0
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-09 16:12 UTC by Need Real Name
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-12-13 00:37:51 UTC
Embargoed:


Attachments (Terms of Use)
up2date error (854 bytes, text/plain)
2000-12-09 16:14 UTC, Need Real Name
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2000:138 0 high SHIPPED_LIVE New, enhanced Update Agent for Red Hat Linux 6.x, 7.0 available 2000-12-21 05:00:00 UTC

Description Need Real Name 2000-12-09 16:12:02 UTC
Upgraded a workstation install from 6.2 to 7.0. Installed
2.0.6-1 from the CD via "rpm- ivh" since it was not
initially on my 6.2. The app worked several times and then
began to error out on "Get Headers for Available
Packages".

Error messages received refer to:

libglade.py
gui.py
up2date.py
gtk.py

My search did not find a similar bug report.

Comment 1 Need Real Name 2000-12-09 16:14:49 UTC
Created attachment 6250 [details]
up2date error

Comment 2 Need Real Name 2000-12-09 16:21:41 UTC
Decided to make a low priority and severity since the work-around
is to manually ftp the desired RPM upgrades from the Red Hat
web site.

Comment 3 Need Real Name 2000-12-13 00:37:47 UTC
(12/12/2000) Per submitter: I decided to once again remove the
up2date application. I notices a message about /var/spool/up2date
not being empty. As root, I removed all the rpm and hdr files and
then removed the directory. I downloaded and installed up2date
again and it completed downloading the headers, as well as
the packages themselves. Seems like my config must have "froze"
or something. Seems like the bug can be closed.

Comment 4 Preston Brown 2000-12-21 19:39:23 UTC
fixed in errata being released shortly.


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