tickets #54605
closedFwd: [opensuse-buildservice] Repository publishing broken on b.o.o ?
100%
Description
Hi,
I was directed here from opensuse-buildservice@opensuse.org, see below:
I also attached a verbose log from curl and it turns out, the mirror is
ftp.gwdg.de.
Anything I can do about this?
Thanks
-Fritz
-------- Forwarded Message --------
Subject: Re: [opensuse-buildservice] Repository publishing broken on b.o.o ?
Date: Wed, 24 Jul 2019 11:29:12 +0200
From: Adrian Schröter adrian@suse.de
To: opensuse-buildservice@opensuse.org
CC: Fritz Elfert fritz@fritz-elfert.de
On Mittwoch, 24. Juli 2019, 11:14:45 CEST Fritz Elfert wrote:
Hi,
I recently noticed some strange discrepancy of the downloadable packages
that were created after building:The size/checksum of the rpm file on download.opensuse.org does not match
the metadata that is recorded in the repository's primary.xml.gzE.g:
When downloading
https://download.opensuse.org/repositories/home:/felfert/Fedora_29/x86_64/eh
s-devel-1.5.1-173.fc29.x86_64.rpmThe resulting size is 622240 bytes and the sha256sum is
eb77ce147162cd3ab9a997e31b865b3e22f7457327f12eac202e6b54210a4547However in the corresponding
https://download.opensuse.org/repositories/home:/felfert/Fedora_29/repodata/
064d3aa4fe373fa91f0edbfcc22328585f5bb381f3661b3d951accaa12baaf22-primary.xml
.gz
most likely a mirror is broken. Check with curl or wget from where it comes
really and report it to
please. (since the download infrastructure is not part of OBS).
thanks
adrian
The size is recorded as 622248 and the sha256 as
11524992b6ca3bc8f2bc0b7f82c0c3875c1c9ca3f87e8b9072cce2bff2331466Obviously, dnf complains when attempting to install or update the package.
I rebuilt the affected packages, but this did not help.
Any clues?Thanks
-Fritz
--
Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: adrian@suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Files
Updated by felfert almost 5 years ago
In the meantime, I tried some other mirrors:
ftp.lysator.liu.se: broken
provo-mirror.opensuse.org: intact
So it is a mirror problem indeed. The qustion is: How can one trigger a re-fetch?
As mentioned in my mail to opensuse-buildservice, I already tried a rebuild of the affected packages, but this did not help.
Updated by lrupp over 4 years ago
- Category set to Mirrors
felfert wrote:
ftp.lysator.liu.se: broken
provo-mirror.opensuse.org: intactSo it is a mirror problem indeed. The qustion is: How can one trigger a re-fetch?
As mentioned in my mail to opensuse-buildservice, I already tried a rebuild of the affected packages, but this did not help.
The only way to get this fixed is by talking to the admin of the broken mirror.
https://mirrors.opensuse.org lists only https://www.lysator.liu.se as contact and I'm not speaking Swedish... But will try...
Updated by pjessen over 4 years ago
There is a slight problem with lysator - afair, they want to sync from one address (hina.lysator), but access it only from another (ftp.lysator). That means we can't scan them after a push. Anyway, this is 6 months back, we did have some issues with the repo push when pontifex was suddenly upgraded.
Updated by felfert over 4 years ago
Hint: http://www.lysator.liu.se/index_en.html
Apparently, they also have an IRC channel at freenode.
Updated by pjessen about 4 years ago
- Status changed from New to Feedback
Do you still see a problem with Lysator, according to http://mirrors.opensuse.org, we think they are okay.
Updated by lrupp almost 4 years ago
- Status changed from Feedback to Closed
- Assignee set to pjessen
- % Done changed from 0 to 100
pjessen wrote:
Do you still see a problem with Lysator, according to http://mirrors.opensuse.org, we think they are okay.
No feedback for 3 months. Closing this ticket - feel free to reopen by replying via Email if the issue happens again.
Regards,
Lars