Mailinglist Archive: opensuse-buildservice (351 mails)

< Previous Next >
Re: [opensuse-buildservice] mirrors not in sync
  • From: Peter Poeml <poeml@xxxxxxx>
  • Date: Thu, 10 Jul 2008 15:55:41 +0200
  • Message-id: <20080710135541.GC7933@xxxxxxx>
Hi Chris,

On Wed, Jul 09, 2008 at 10:29:16PM +0000, Christian wrote:

repoview not listed on

Filename: repositories/openSUSE:/Tools/SLE_10/openSUSE:Tools.repo
Client IP address:
Found 8 mirrors: 3 country, 2 region, 2 elsewhere

Mirrors in the same country (DE):
(score 100)
(score 100)

Kind regards

What exactly do you expect?

It is a matter of fact that
1) only few mirrors mirror the buildservice repositories. Due to the
size of the tree we only find partial (or outdated) mirrors.
2) it takes time to get them in sync for new content, even though
content is pushed to some mirrors right after publishing, but syncs
need to be queued, and the build service publishes a lot. Due to
the size of the tree

Thus, the above looks normal.

The file repoview-0.5.2-74.1.i586.rpm (which you probably are looking
for) is available on three mirrors right now:
But it is available on anyway.

BTW, the mirror system works in a way that it takes some decisions which
content to mirror and which not. For example, it might decide that
debuginfo packages are never mirrored. Thus, use the canonical download
address ( -- it will send you
to a mirror _if_ possible.

"If possible" also implies another exception: the file you mentioned
above (.repo) will never be sent to a mirror. This is an exception that
it shares Together with other repository metadata. Such data are _too_
hard to get in sync on mirrors, because they change frequently and
contain checksums, so the slightest mistake will make the client err


% curl -sI
HTTP/1.1 200 OK
Date: Thu, 10 Jul 2008 10:12:07 GMT
Server: Apache/2.2.8 (Linux/SUSE)
Last-Modified: Thu, 10 Jul 2008 09:38:46 GMT
ETag: "3002a263-fd-451a8310af580"
Accept-Ranges: bytes
Content-Length: 253
Content-Type: application/x-yum-repo

the file will always delivered by itself.

Which doesn't mean that it is also mirrored. Forbidding to mirror them
would make mirrors less useful. But only can
deliver the file correctly in all cases.

Another reason for this is that _only_ sets
correct cache-control headers. Mirrors don't do this. Thus, with using a
mirror, you'd experience problems whey you get stale copies of metadata
from a web cache, which arbitrarily caches it, and which refers to
packages that no longer exist.

If you are interested to know more about this, there is a 1 hour talk I held
last week about this, available as ogg video here:

I hope I could explain these things in a way that make them clearer.
Contact: admin@xxxxxxxxxxxx (a.k.a. ftpadmin@xxxxxxxx)
#opensuse-mirrors on

SUSE LINUX Products GmbH
Research & Development
< Previous Next >
This Thread