Red Hat Bugzilla – Bug 175353
Package update synchronization: Repositories claim that updates are available before packages are physically present on servers
Last modified: 2007-11-30 17:11:18 EST
Description of problem:
I tried to search for any duplicates of this bug/problem in the bugzilla
database but came up short since I also don't quite know what to search for. If
this is, in fact, a duplicate, my apologies for the noise. Also, this is a
all-packages repository-wide problem but the bug entry page here forces me to
enter a component, so I guessed.
When attempting to run APT-GET on the extras packages, the servers show that
updates are present and these updates are taken into account in the download
computations. Attempts to download the packages fail because they are not
physically present on the server(s).
I am using ayo.*.freshrpms.net extras repositories, doesn't matter which mirror.
This also happens with the main repository. Perhaps this is a freshrpms server
Version-Release number of selected component (if applicable):
Need to jump in and see the updates reported before the packages are on the
server. Difficult to say how to reproduce this.
Steps to Reproduce:
1. See above.
Error output from Synaptic for RPM:
W: Failed to fetch
404 Not Found
All files that are reported as available should be present for download.
What should happen is that updates should not be marked as present until the
physical packages are also present first. This prevents constant
checking/polling for updates that are already reported as needed but no packages
available due to mirror updating.
I wonder why this was assigned to me? Reassigning to Matthias who is more
likely to be able to say something about freshrpms.net mirrors...
Well, this problem is know, and I don't have any magic solution for it. The
problem is that the apt metadata is generated on a private mirror server, then
sent to the main ayo.freshrpms.net server, which is ftp.heanet.ie currently. But
that public server seems to sync Fedora updates less often than the private
server, so apt ends up telling you that updates are available, although they
aren't yet in reality.
The best long term solution to this problem is to have apt use repomd metadata
and rely on the main Fedora generated metadata instead of on the one generated
"off site", since it'll always be in sync with the packages actually present on
I'm going to resolve this bug as DEFERRED, as :
- It is not directly related to Fedora packages or Fedora infrastructures
- The proper fix will be to have an apt package that supports repomd, which
will luckily happen some day, since Panu has been working on it.