#12121 create EPEL 8.9 archive snapshot
Closed: Fixed a month ago by jnsamyak. Opened a month ago by carlwgeorge.

  • Describe the issue

RHEL 8.10 was released today. Releng usually creates snapshots of the EPEL repository on RHEL minor version release day.

  • When do you need this? (2024-05-22)

Sorry for the tight timing, but there really is a tight window for this. Doing it before today would have missed valid EPEL 8 builds that work on RHEL 8.9. Doing it after today will result in EPEL 8 builds in the snapshot that were built against RHEL 8.10 libraries.

  • When is this no longer needed or useful? (2024-05-22)

See last answer.

  • If we cannot complete your request, what is the impact?

While it is a discouraged practice, we know there are users who manually pin to minor versions of their OS and want to consume EPEL packages that will work. When they use the main EPEL repo, they discover problem caused by the mismatch. While we could just let them manually search old koji builds for a working artifact, using an archived repo (even if unmaintained) is a much better experience. This snapshot is also useful as a historical reference of the EPEL repository over time.

So, I checked how Kevin did it last time from here: https://pagure.io/releng/issue/12088

Gonna follow the same process

login to compose-rawhide01 (this machine has archive volume rw)

rsync -avH /pub/epel/8/ /srv/fedora_ftp_archive/epel/8.9-2024-05-22/ --link-dest=/srv/fedora_ftp_archive/epel/8.8.2023-11-14/

rsync -avH /pub/epel/8/ /srv/fedora_ftp_archive/epel/testing/8.9-2024-05-22/ --link-dest=/srv/fedora_ftp_archive/epel/8.8.2023-11-14/

cd /srv/fedora_ftp_archive/epel/

ln -s 8.9-2024-05-22 8.9

@kevin, can you confirm this once, meanwhile I'll run this if there is something that needs correction here we will do that

Metadata Update from @jnsamyak:
- Issue tagged with: high-trouble, medium-gain, ops

a month ago

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

a month ago

Yes, that looks about right to me... :)

This is done, we can close this!

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

a month ago

Log in to comment on this ticket.

Boards 1
Ops Status: Backlog