releng

#9629 PDC: do we want to store the EPEL compose?
Closed: Get back later by mohanboddu. Opened by pingou.

Closed: Get back later
Reopen Issue
  • Describe the issue

Currently toddlers import into PDC both Fedora and EPEL composes. We've had the discussion whether we wanted both or just the Fedora ones.

So I'm opening this ticket to ask for input on this. Do we want to keep the status quo or change?

Cc: @adamwill for input

I think both is fine, and might be helpfull someday...

I think both is fine, and might be helpfull someday...

I agree, but currently only Fedora one's are being used.

Metadata Update from @mohanboddu:
- Issue tagged with: groomed, high-gain, low-trouble

currently only Fedora one's are being used.

Thus my asking.

I don't really care about storing things in PDC however, having in mind the idea of replacing it, I'd like to identify what we actually want to store (and potentially why, so it helps figuring out what remains needed in the future).

Closing the ticket for now, but we need to import the composes for fedfind and OpenQA stuff, so, we need to import rawhide and branched composes at the least, but when we are ready to look at pdc replacement we can import epel composes as well.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Get back later
- Issue status updated to: Closed (was: Open)
Metadata
None

groomed high-gain low-trouble

None
None
None
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.