#11494 Epel 9 next ppc64le mirrors have problems
Closed: Fixed by praiskup. Opened by praiskup.

Original report: https://github.com/fedora-copr/copr/issues/2783

Seems like the the metaling provides wrong baseurl pattern:

$ curl 'https://mirrors.fedoraproject.org/metalink?repo=epel-next-9&arch=ppc64le'
<?xml version="1.0" encoding="utf-8"?>
<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Wed, 21 Jun 2023 11:36:57 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">
 <files>
  <file name="repomd.xml">
   <mm0:timestamp>1519154018</mm0:timestamp>
   <size>3068</size>
   <verification>
    <hash type="md5">a9918dad730aec1c339f9fce05cb01d3</hash>
    <hash type="sha1">13be7bda8c2da37a075dae3f40bbbdfe5845c592</hash>
    <hash type="sha256">94719c762e3e096a2c330d2292a9e76a8b935015a290d20fdbd7a2b920a09a5b</hash>
    <hash type="sha512">c241e00f6839a095c5c16df5e7305a9157a8d418f38547edc642378c6b3f53601cf0ee81034382aa1baa56d354fa5a2d9e67fc8b29523097e86f11a5b85c622b</hash>
   </verification>
   <resources maxconnections="1">
    <url protocol="https" type="https" location="US" preference="100">https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/next/9/Everything/ppc64le/Packages/os/repodata/repomd.xml</url>
    <url protocol="https" type="https" location="US" preference="99">https://dl.fedoraproject.org/pub/epel/next/9/Everything/ppc64le/Packages/os/repodata/repomd.xml</url>
    <url protocol="http" type="http" location="US" preference="99">http://dl.fedoraproject.org/pub/epel/next/9/Everything/ppc64le/Packages/os/repodata/repomd.xml</url>
   </resources>
  </file>
 </files>
</metalink>

The difference:

- http://dl.fedoraproject.org/pub/epel/next/9/Everything/ppc64le/Packages/os/repodata/repomd.xml
- http://dl.fedoraproject.org/pub/epel/next/9/Everything/ppc64le/repodata/repomd.xml

@adrian any ideas here?

I would expect others would have seen this if it was just wrong...

This is really strange. The timestamp is also really old:

date -ud @1519154018
Tue 20 Feb 19:13:38 UTC 2018

Maybe no one used it until now. That is the only idea I have. It was initially created wrong and no one noticed.

I can take a closer look tomorrow and see if I can fix it in the database. Moving repository location is something that needs to be fixed manually.

Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble

Maybe no one used it until now.

I also thought so, but this is a new thing eventually; e.g. this build just worked:
https://copr.fedorainfracloud.org/coprs/mjg/mupdf-git/build/6100835/

The repository should appear in about 1 hour in MirrorManager (metalink).

Metadata Update from @praiskup:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Thank you!

Metadata