On 8/1/20 18:38, Kevin Fenzi wrote:
Greetings.
As you all should know, we stopped doing aarch64 epel7 builds a while
back, because rhel7.6 stopped supporting it, and thus there was no way
to keep going on with it.
However, we still have the epel7/aarch64 repos on our mirrors, just
static with the last content that was there:
https://dl.fedoraproject.org/pub/epel/7/aarch64/
https://dl.fedoraproject.org/pub/epel/testing/7/aarch64/
Do we have any metrics on usage? Like what we had for the ppc64 retirement?
Should we do something here? Options include:
1. Nothing, just leave them there and from time to time people will ask
why the new thing isn't in there and we will explain it's the old, no
longer updated repo.
2. Remove the repo and replace it with a empty one, but leave it in
mirrormanager. This will cause everyone to not get errors, but they
also will see that there's nothing there and ask why not and we will
explain that we stopped supporting it.
3. Remove the repo, remove the arch from mirrormanager. This would cause
errors for anyone who has the repo enabled and they would ask about it,
and we would tell them that it's no longer supported.
4. Some other more clever solution.
Thoughts?
I'm working on a rebuild for aarch64 based on CentOS, the same way is
done for armhfp, and I'm hoping to have a better idea after FOSDEM.
If I manage to do this, my plan would be to do option 1 until I have
something working, then do a post somewhere explaining the move, and
then introduce option 3, maybe around 7.8?
kevin
Pablo.
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
