Similar to #11811 but for EL 8.6, not 8.8.
Describe the issue https://dl.fedoraproject.org/pub/archive/epel/ seems to be missing the 8.6* branches.
When do you need this? (YYYY/MM/DD) ASAP.
When is this no longer needed or useful? (YYYY/MM/DD) Some unknown time in the future when ISVs no longer need to be able to test with EL 8.6.
If we cannot complete your request, what is the impact? We are unable to do backward compatibility testing, bug report testing, and generally supporting users that still need to be on EL 8.6. I would suspect, but cannot confirm this would also effect people on a RHEL 8.6.z release.
Thanks!
I do not think this is going to be possible to do.
We don't have any snapshot or copy of what epel8 looked like that long ago. ;(
Perhaps someone else can think of a way to do it, but I can't off hand...
This is not something that can be easily done. All of the X.Y sub-directories have been a manual process which could only be done during a narrow window of time where packages would be 'copied' regularly to say 8.2 until 8.3 came out. Once 8.3 came out it would be a manual last sync done by a volunteer. After I stopped volunteering on this, it wasn't taken up by anyone else.
Doing more than this has been seen as needing a dedicated worker who has never been funded internally or externally.
The following may not be the only way of doing this, but it would be how I would have try to do this. I would need to go through all the builds marked for EL-8 and then go through their buildlogs to see if they were built with redhat-release-8.6 or earlier. If they are, then I would collect all those packages into a 'package' set and get the latest of them that will 'repoclose'
This would be a lot of work and probably bring the NFS server to its knees in parts due to the number of trees needing to be looked at.
Yeah, lets talk about it in the releng meeting tomorrow... but I don't see any easy way.
Metadata Update from @kevin: - Issue tagged with: high-trouble, medium-gain, meeting, ops
So, we talked about it in the releng and epel meetings, but we didn't think it would be at all easy to do, so sadly, we just aren't going to be able to do it at this time.
Sorry.
Metadata Update from @kevin: - Issue close_status updated to: Can't Fix - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.