fedora-infrastructure

#9984 epel8-next repos in mirrormanager
Closed: Fixed by adrian. Opened by carlwgeorge.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

Please add the following repositories to mirrormanager.

All archful repos are for aarch64, ppc64le, and x86_64 only. epel8-next will not have s390x.

When do you need this to be done by? (YYYY/MM/DD)

ASAP

@adrian Can you take a look at this, thanks.
Edited by mohanboddu

Metadata Update from @mohanboddu:
- Issue assigned to adrian
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

I would need https://pagure.io/fedora-infrastructure/issue/9985 for testing.

9985 is fixed now. :)

Following repositories do now exist in the database and should be ready to use:

pub/epel/next/8/Everything/ppc64le                                     | epel-next-8
pub/epel/next/8/Everything/aarch64                                     | epel-next-8
pub/epel/testing/next/8/Everything/aarch64                             | epel-testing-next-8
pub/epel/next/8/Everything/aarch64/debug                               | epel-next-debug-8
pub/epel/testing/next/8/Everything/aarch64/debug                       | epel-testing-next-debug-8
pub/epel/testing/next/8/Everything/x86_64/debug                        | epel-testing-next-debug-8
pub/epel/next/8/Everything/ppc64le/debug                               | epel-next-debug-8
pub/epel/testing/next/8/Everything/x86_64                              | epel-testing-next-8
pub/epel/next/8/Everything/x86_64/debug                                | epel-next-debug-8
pub/epel/next/8/Everything/x86_64                                      | epel-next-8
pub/epel/testing/next/8/Everything/ppc64le                             | epel-testing-next-8
pub/epel/next/8/Everything/SRPMS                                       | epel-next-source-8
pub/epel/testing/next/8/Everything/ppc64le/debug                       | epel-testing-next-debug-8
pub/epel/testing/next/8/Everything/SRPMS                               | epel-testing-next-source-8

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

Is the goal for the mirrormanager repo names to be more similar to the repo ids or the filesystem path? The non-testing repos seem to match the repo ids pretty well, but the testing repos names are inconsistent.

repo id: epel
mirrormanager name: epel-8
path: pub/epel/8/Everything/$basearch/
repo id: epel-debuginfo
mirrormanager name: epel-debug-8
path: pub/epel/8/Everything/$basearch/debug/
repo id: epel-source
mirrormanager name: epel-source-8
path: pub/epel/8/Everything/SRPMS/
repo id: epel-testing
mirrormanager name: testing-epel8
path: pub/epel/testing/8/Everything/$basearch/
repo id: epel-testing-debuginfo
mirrormanager name: testing-debug-epel8
path: pub/epel/testing/8/Everything/$basearch/debug/
repo id: epel-testing-source
mirrormanager name: testing-source-epel8
path: pub/epel/testing/8/Everything/SRPMS/

repo id: epel-next
mirrormanager name: epel-next-8
path: pub/epel/next/8/Everything/$basearch/
repo id: epel-next-debuginfo
mirrormanager name: epel-next-debug-8
path: pub/epel/next/8/Everything/$basearch/debug/
repo id: epel-next-source
mirrormanager name: epel-next-source-8
path: pub/epel/next/8/Everything/SRPMS/
repo id: epel-next-testing
mirrormanager name: epel-testing-next-8
path: pub/epel/testing/next/8/Everything/$basearch/
repo id: epel-next-testing-debuginfo
mirrormanager name: epel-testing-next-debug-8
path: pub/epel/testing/next/8/Everything/$basearch/debug/
repo id: epel-next-testing-source
mirrormanager name: epel-testing-next-source-8
path: pub/epel/testing/next/8/Everything/SRPMS/

Unfortunately MirrorManager repository naming is a mess. There is no clear structure.

I saw that you followed playground naming in the ticket but I tried to follow original epel repository naming. Whatever is selected some names will not match. I tried to follow:
prefix-(debug,source)-version

prefix can be anything from epel, epel-testing, epel-next, epel-testing-next.

prefix is based on the path epel/testing/next results in epel-testing-next.

We can still delete it and name it differently but no matter what we select there will be repositories which do not fit the existing scheme.

Yeah I see what you mean. I was thinking about trying to preserve the "epel-next" string in repo names (e.g. epel-next-testing-8), but I see the value in standardizing on having the repo name based on the path going forward. I'll move forward with what is set up now, thanks for clarifying!
Metadata

medium-gain medium-trouble ops

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.