Bug 103402 - new Up2Date with updated SSL cert needs Python-2.2.2
Summary: new Up2Date with updated SSL cert needs Python-2.2.2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Fanny Augustin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-29 20:19 UTC by David Simmons
Modified: 2007-04-18 16:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-08-29 22:49:17 UTC
Embargoed:


Attachments (Terms of Use)

Description David Simmons 2003-08-29 20:19:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716

Description of problem:
I've read through the latest info on the updated SSL info.  After
downloading the newest up2dates (normal & gnome).....and following the
instructions to:

rpm -Fvh up2date*.rpm

I receive the following message:

[dsimmons@localhost dsimmons]$ rpm -Fvh up2date*
error: Failed dependencies:
        python >= 2.2.2 is needed by up2date-3.1.23.2-1
        rhpl >= 0.81-2 is needed by up2date-3.1.23.2-1
[dsimmons@localhost dsimmons]$

but when I try to run up2date python - it doesn't work (of course)...and
when I look around using the APT-GET function with stable - I don't find
that the latest stable is 2.2.2???!!!??

looks like the horse is before the cart?

Thanks for any help/info on how to get my machine working with RHN

Dave





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


How reproducible:
Always

Steps to Reproduce:
1. download up2date (and gnome.rpm)
2. follow directions to install:

rpm -Fvh up2date*.rpm
3. install will fail on base system (ie. non developer/unstable) - Apt can't
find python-2.2.2!?
    

Additional info:

Comment 1 Bill Nottingham 2003-08-29 22:49:17 UTC
You've downloaded the wrong version for 8.0. The correct version is:

up2date-3.0.7.2-1.


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