Bug 74619 - up2date with wrong depencies
up2date with wrong depencies
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
8.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-09-27 14:32 EDT by StK
Modified: 2015-01-07 19:00 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-20 15:44:13 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 StK 2002-09-27 14:32:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; QXW03306)

Description of problem:
After a unfinnished upgrade from 7.3 to null (because i only had the 1. CD), 
everything worked without any problems.
up2date -l listed a lot of packages remaining from the old 7.3.

I thought to better solve the new depencies in the new Redhat null, i first 
wanted to upgrade up2date itself.

But... after typing "up2date up2date"
i got errormessages like "error in line XY /????.py"..

So i guess up2date needs a newer python.

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


How reproducible:
Didn't try

Steps to Reproduce:
1. install 7.3, with gnome (or anything that needs CD2)
2. upgrade to null 
3. type up2date up2date
	

Additional info:
Comment 1 Adrian Likins 2002-10-01 17:51:57 EDT
upgrades to beta are pretty shaky territory, especially
with changes as big as 7.3->Null. It's quite possible
some needed package deps hadnt been added at that
point.

Do you still see this issue with 8.0?
Comment 2 StK 2002-10-01 18:02:07 EDT
I use 8.0 now, but i downloaded all CD's first (this time)
And... sorry, i don't want to try this again ;-)

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