Bug 62883

Summary:	problems using update agent
Product:	[Retired] Red Hat Linux	Reporter:	Paul Moffitt <pmoffitt>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	gafton, mihai.ibanescu, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-04-05 20:38:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Moffitt 2002-04-07 00:37:39 UTC

Description of Problem: Yesterday (april 7 2002) I was trying to use update agent, which I have successfully used before.  However on several 
occasions , specifically when I tried to download kdeadmin or gnorpm, I received the message: a package providing lib rpmio-4.0.3.so could not be 
found.  However when I went to the redhat channel in openprojects,  they told me to check a few things, and evidently I do have that particular file.  
Other update downloads worked ok.  As I said, I have not come across this problem before.


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


How Reproducible:  I don't know if you can reproduce it, other than using update agent and trying to download those two particular updates.


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Adrian Likins 2002-04-09 21:13:43 UTC

which version of the up2date client?

If you have packages which require an older version of
rpm, and there isnt a newer version of that package
available from us, you get an unresolveable dep, as
you indicate.

But I would also make sure you have the latest up2date,
since it has better handling of these cases.

Comment 2 Adrian Likins 2004-04-05 20:38:14 UTC

No response, and I haven't seen any reports
like this with current releases, so
closing as "currentrelease"