Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 106906

Summary:	up2date incorrectly displays "Package already downloaded"
Product:	[Fedora] Fedora	Reporter:	Michael Young <m.a.young>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	barryn, dave.habben, paul, sindrepb
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-07-14 16:28:24 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:
Bug Depends On:
Bug Blocks:	100644

Description Michael Young 2003-10-13 10:09:57 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031008

Description of problem:
While you are retrieving packages with 4.1.5-1 from a non-RHN source (eg.
rawhide via yum), the message over the download bar claims "Package already
downloaded" while it is downloading the package, even though it clearly isn't.
This is merely confusing, it doesn't seem to affect functionality.

Comment 1 Dave Habben 2003-10-18 23:50:09 UTC

Looks like a duplicate of bug 107444, one of these should be closed.

Comment 2 Bill Nottingham 2003-10-20 22:51:28 UTC

*** Bug 107444 has been marked as a duplicate of this bug. ***

Comment 3 Barry K. Nathan 2003-10-22 17:56:02 UTC

This is still happening with up2date 4.1.7.

Comment 4 Miloslav Trmac 2004-03-01 09:21:24 UTC

*** Bug 107623 has been marked as a duplicate of this bug. ***

Comment 5 Barry K. Nathan 2004-07-14 15:42:18 UTC

I'm pretty sure that this was fixed before FC1 final. I'm *definitely*
sure it's fixed in FC2 (I just tested right now). Thus, this bug
should be closed.

Comment 6 Michael Young 2004-07-14 16:28:24 UTC

Closing as fixed in current release.