Bug 122088

Summary: up2date cannot find the updated component when launched although "Check for update" reports available updates
Product: [Fedora] Fedora Reporter: Need Real Name <rwaultz>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED WONTFIX QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: genchev, mattdm
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: 2007-04-10 16:51:36 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: 120092    
Attachments:
Description Flags
Screen shot of the fault sit. none

Description Need Real Name 2004-04-30 11:35:44 UTC 
Description of problem:
"Launch up2date" cannot find the updated component although "Check for
update" reports existing updates 

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

How reproducible:

Steps to Reproduce:
1. Installed FC2 Test3 from scratch
2. Performed up2date. Update ~61 packages successfully
3. Performed check for update. Reported perl-Net-DNS-0.45-2 available
over existing perl-Net-DNS-0.31-3.2.
4. Clicked 'Launch up2date' button. No action. (Message: Your system
is fully updated. No new packages are needed)

A screenshot (.png) is available on request.
  
Actual results:
rpm -q outputs:
up2date-4.3.17-1
yum-2.0.7-0.20040416
perl-Net-DNS-0.31-3.2


Expected results:


Additional info:
Comment 1 Need Real Name 2004-04-30 11:38:49 UTC 
Created attachment 99817 [details]
Screen shot of the fault sit.
Comment 2 Genadi Enchev 2004-04-30 15:42:51 UTC 
I have the same problem here. The tool shows that 9 updates are
available, but when I run up2date, it says "Your system is fully
ppdated. No new packages are needed". I didn't have any problems after
the up2date right after I installed my system.
Comment 3 Adrian Likins 2004-05-07 18:22:48 UTC 
This is a bug that wont get fixed till fc3/rhel4 (and/or
a version of up2date for fc2 that understand the rpm metadata
format instead of yum repos).

Basically, in order to make multllib systems (aka x86_64 boxes
with both a x86_64 and a i386 runtime) update correctly,
cross arch updates arent allowed. In this case, the issue
is perl-Net-DNS changed from a noarch package to a arch'ed
package, so up2date wont update it. The applet, however,
doesnt know that since it doesnt handle mulitlib.


The right fix is with more metadata from the server about
not only what arch a package is, but also what arch family 
it is (aka, this package is in the x86 vector, that package
is in the x86_64 vector, etc).

That said, it should probabaly allow noarch->arch updates
anyway, since it doesnt make sense to have biarch packages
installed at the same time that way.
Comment 4 Adrian Likins 2004-05-07 21:04:38 UTC 
fix for the noarch->arch package stuff just committed to
cvs. 4.3.19 or higher should have it

i386->i686 etcwill have to wait for fc3/rhel4
Comment 5 Todd Warner 2004-08-27 01:53:57 UTC 
FAILS_QA: need a test plan adrian.
Comment 6 Matthew Miller 2007-04-10 16:51:36 UTC 
since there is no more up2date, marking "wontfix".