Red Hat Bugzilla – Bug 122088
up2date cannot find the updated component when launched although "Check for update" reports available updates
Last modified: 2007-11-30 17:10:41 EST
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:
Created attachment 99817 [details] Screen shot of the fault sit.
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.
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.
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
FAILS_QA: need a test plan adrian.
since there is no more up2date, marking "wontfix".