Hello mirror admins,
this mirror http://mirror1.hs-esslingen.de seem to keep up to 4 versions of openSUSE Leap 15.3 Beta rpms (15.3 oss ftp repo)
Can you please investigate or somehow force re-sync the data?
Thank you
Best regards
Lubos Kocman Release Manager openSUSE Leap
On Montag, 19. April 2021, 17:33:07 CEST Lubos Kocman wrote:
Hello mirror admins,
this mirror http://mirror1.hs-esslingen.de seem to keep up to 4 versions of openSUSE Leap 15.3 Beta rpms (15.3 oss ftp repo)
Can you please investigate or somehow force re-sync the data?
that is a misunderstanding, I think. download.opensuse.org just shows 4 versions.
However, download.o.o redirected to hs-esslingen for
http://mirror1.hs-esslingen.de/pub/Mirrors/ftp.opensuse.org/distribution/lea...
which does not exist there.
So, either wrong rpm-md was delivered or the redirector db was not in sync with reality.
Adrian Schröter wrote:
On Montag, 19. April 2021, 17:33:07 CEST Lubos Kocman wrote:
Hello mirror admins,
this mirror http://mirror1.hs-esslingen.de seem to keep up to 4 versions of openSUSE Leap 15.3 Beta rpms (15.3 oss ftp repo)
Can you please investigate or somehow force re-sync the data?
that is a misunderstanding, I think. download.opensuse.org just shows 4 versions.
On download.o.o, I also see 3, 4 or 5 versions of openSUSE Leap 15.3 Beta rpms.
Right now, http://mirror1.hs-esslingen.de seems okay though?
However, download.o.o redirected to hs-esslingen for
http://mirror1.hs-esslingen.de/pub/Mirrors/ftp.opensuse.org/distribution/lea...
which does not exist there.
Instead, I see glibc-devel-static-2.31-7.13.aarch64.rpm
On 19/04/2021 18.42, Per Jessen wrote:
Right now, http://mirror1.hs-esslingen.de seems okay though?
However, download.o.o redirected to hs-esslingen for
http://mirror1.hs-esslingen.de/pub/Mirrors/ftp.opensuse.org/distribution/lea...
which does not exist there.
Instead, I see glibc-devel-static-2.31-7.13.aarch64.rpm
http://download.opensuse.org/distribution/leap/15.3/repo/oss/aarch64/glibc-d...
shows here
Found 9 mirrors which handle this country (DE)
https://ftp.gwdg.de/pub/opensuse/distribution/leap/15.3/repo/oss/aarch64/gli... (de, prio 110)
http://opensuse.mirror.iphh.net/distribution/leap/15.3/repo/oss/aarch64/glib... (de, prio 100)
http://suse.uni-leipzig.de/pub/ftp.opensuse.org/opensuse/distribution/leap/1... (de, prio 50)
http://mirror.de.leaseweb.net/opensuse/distribution/leap/15.3/repo/oss/aarch... (de, prio 100)
http://opensuse.schlundtech.de/distribution/leap/15.3/repo/oss/aarch64/glibc... (de, prio 100)
http://mirror.braun-software-solutions.de/opensuse/distribution/leap/15.3/re... (de, prio 100)
http://ftp.uni-bayreuth.de/linux/opensuse/distribution/leap/15.3/repo/oss/aa... (de, prio 50)
http://mirror1.hs-esslingen.de/pub/Mirrors/ftp.opensuse.org/distribution/lea... (de, prio 100)
http://ftp.tu-ilmenau.de/mirror/opensuse/distribution/leap/15.3/repo/oss/aar... (de, prio 30)
so for some reason, the DB still has the old entry listed, and 8 out of 9 mirrors are already updated and return 404. Correctly so. If you were wondering, uni-leipzig is the only one with old file.
I checked that replication to mirrordb2 looks fine.
Maybe a problem with the mirrorbrain scanner?
On Mon, 19 Apr 2021 21:48:27 +0200 "Bernhard M. Wiedemann" bwiedemann@suse.de wrote:
Maybe a problem with the mirrorbrain scanner?
There is *always* a race between "when the mirror synced" and "when we scan".
darix
On Mon, Apr 19, 2021 at 03:33:07PM +0000, Lubos Kocman wrote:
this mirror http://mirror1.hs-esslingen.de seem to keep up to 4 versions of openSUSE Leap 15.3 Beta rpms (15.3 oss ftp repo)
What does that exactly mean?
Can you please investigate or somehow force re-sync the data?
We are regularly syncing from stage.opensuse.org and rsync reports no errors. Not sure what to do.
Adrian
-
Adrian Reber -
Adrian Schröter -
Bernhard M. Wiedemann -
Lubos Kocman -
Marcus Rueckert -
Per Jessen