Bug 177225

Summary: yum check-update does not find updates
Product: [Fedora] Fedora Reporter: Kasper Dupont <bugzilla>
Component: yumAssignee: Jeremy Katz <katzj>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: katzj
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: FC5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-19 20:33:44 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 Kasper Dupont 2006-01-07 23:28:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050811 Fedora/1.7.10-1.1.1.legacy

Description of problem:
yum check-update does not show updates which has been released but not yet installed.

Version-Release number of selected component (if applicable):
yum-2.4.1-1.fc4

How reproducible:
Always

Steps to Reproduce:
1. yum check-update


Actual Results:  yum find no new packages

Expected Results:  yum should find 53 updates

Additional info:

The following 53 packages are available from http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/, but not yet installed on my system, and yum does not say anything about them.

cups-1.1.23-15.3.i386.rpm
cups-devel-1.1.23-15.3.i386.rpm
cups-libs-1.1.23-15.3.i386.rpm
cups-lpd-1.1.23-15.3.i386.rpm
eclipse-ecj-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-jdt-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-jdt-devel-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-pde-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-pde-devel-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-platform-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-platform-devel-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-rcp-3.1.1-1jpp_1fc.FC4.12.i386.rpm
eclipse-rcp-devel-3.1.1-1jpp_1fc.FC4.12.i386.rpm
ethereal-0.10.14-1.FC4.1.i386.rpm
ethereal-gnome-0.10.14-1.FC4.1.i386.rpm
gimp-2.2.10-0.fc4.1.i386.rpm
gimp-devel-2.2.10-0.fc4.1.i386.rpm
gnucash-1.8.12-0.fc4.i386.rpm
gnucash-backend-postgres-1.8.12-0.fc4.i386.rpm
irb-1.8.4-1.fc4.i386.rpm
kernel-2.6.14-1.1656_FC4.i686.rpm
kernel-devel-2.6.14-1.1656_FC4.i686.rpm
kernel-doc-2.6.14-1.1656_FC4.noarch.rpm
libswt3-gtk2-3.1.1-1jpp_1fc.FC4.12.i386.rpm
mod_auth_pgsql-2.0.1-8.1.i386.rpm
netpbm-10.31-1.FC4.i386.rpm
netpbm-devel-10.31-1.FC4.i386.rpm
netpbm-progs-10.31-1.FC4.i386.rpm
openoffice.org-calc-2.0.1.1-4.1.i386.rpm
openoffice.org-core-2.0.1.1-4.1.i386.rpm
openoffice.org-draw-2.0.1.1-4.1.i386.rpm
openoffice.org-graphicfilter-2.0.1.1-4.1.i386.rpm
openoffice.org-impress-2.0.1.1-4.1.i386.rpm
openoffice.org-javafilter-2.0.1.1-4.1.i386.rpm
openoffice.org-langpack-da_DK-2.0.1.1-4.1.i386.rpm
openoffice.org-langpack-de-2.0.1.1-4.1.i386.rpm
openoffice.org-langpack-fi_FI-2.0.1.1-4.1.i386.rpm
openoffice.org-langpack-nn_NO-2.0.1.1-4.1.i386.rpm
openoffice.org-langpack-sv-2.0.1.1-4.1.i386.rpm
openoffice.org-math-2.0.1.1-4.1.i386.rpm
openoffice.org-pyuno-2.0.1.1-4.1.i386.rpm
openoffice.org-testtools-2.0.1.1-4.1.i386.rpm
openoffice.org-writer-2.0.1.1-4.1.i386.rpm
openoffice.org-xsltfilter-2.0.1.1-4.1.i386.rpm
rdoc-1.8.4-1.fc4.i386.rpm
ri-1.8.4-1.fc4.i386.rpm
ruby-1.8.4-1.fc4.i386.rpm
ruby-devel-1.8.4-1.fc4.i386.rpm
ruby-docs-1.8.4-1.fc4.i386.rpm
ruby-libs-1.8.4-1.fc4.i386.rpm
ruby-mode-1.8.4-1.fc4.i386.rpm
ruby-tcltk-1.8.4-1.fc4.i386.rpm
util-linux-2.12p-9.13.i386.rpm

Comment 1 Seth Vidal 2006-01-08 00:43:42 UTC
let me guess. You're using the mirror lists?

If you are then probably whatever mirror it hit when you were running
check-update was not in sync with the mirror master.


Reopen the bug if this is not the case.

Comment 2 Kasper Dupont 2006-01-08 08:13:12 UTC
I'm using the default configuration, does that use mirror lists? How long time
does it take for a mirror to get the updates? Some of them had been available
for two days when I noticed the problem.

Comment 3 Seth Vidal 2006-01-08 15:20:25 UTC
the default configuration does use mirror lists.

Some of the mirrors are just not being updated anymore or only update once a week.

hence, the problem.



Comment 4 Kasper Dupont 2006-01-08 16:08:08 UTC
In that case I see two solutions. Either outdated mirrors should be removed from
the default configuration. Or yum should download enough information from the
master to be able to detect an outdated mirror and use another.

Comment 5 Kasper Dupont 2006-03-03 12:15:07 UTC
If this is not a bug in yum, it must be a bug in the mirror list. Changing
component from yum to fedora-release.

Comment 6 Seth Vidal 2006-03-03 15:43:23 UTC
It's not a fedora-release bug, either.

If anything it's an RFE against yum.


There's nothing here that is a bug at all.
But a feature request that may or may not be fulfilled.

Comment 7 Jeremy Katz 2006-04-19 20:33:44 UTC
The cachecookie stuff helps here and there is work underway to improve the
mirror infrastructure.