$ make sync-repositories ... Found: ['epel-6', 'epel-6-testing', 'epel-7', 'epel-7-testing', 'epel-8', 'epel-8-testing', 'epel-9', 'epel-9-testing', 'fedora-34', 'fedora-34-updates', 'fedora-34-updates-testing', 'fedora-35', 'fedora-35-updates', 'fedora-35-updates-testing', 'fedora-rawhide'] epel-6 !! Failed to get 'https://dl.fedoraproject.org/pub/epel/6/x86_64/repodata//repomd.xml' <Response [404]> epel-6-testing !! Failed to get 'https://dl.fedoraproject.org/pub/epel/testing/6/x86_64/repodata/repomd.xml' <Response [404]> epel-7 Downloading file: https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata//79414ba9...
EPEL 6 should not be used since it is currently unsupported. We will likely need to maintain an ignore-list for when PDC has unsupported releases listed as active.
What the difference between supported and active releases then?
I looked into this and can't find a good definition of what "active" means in PDC. Perhaps Bodhi would be a better source for this info? https://bodhi.fedoraproject.org/releases/
https://pdc.fedoraproject.org/rest_api/v1/product-versions/?active=true returns that from epel-6 product only epel-6-updates release active, so the problem is in https://pagure.io/fork/abitrolly/fedora-packages-static/blob/94bf8a0300efa66ac778238b328b3f080bbfe4bf/f/bin/fetch-repository-dbs.py#_285 get_repository_urls_for() that decides what repos are there.
epel-6
epel-6-updates
get_repository_urls_for()
EPEL 6 is deprecated, so that repo should not even be pulled by us even if there is a bug preventing it from being pulled currently. I'll probably ask releng what's up with this.
https://docs.fedoraproject.org/en-US/epel/#end_of_life_releases
Login to comment on this ticket.