On Fri, 16 Jul 2021 at 17:59, Pavel Raiskup <praiskup(a)redhat.com> wrote:
We touched this topic several times before in our team. Perhaps we should move
on and do it... it would simplify a development (the yum/dnf hacks,
legacy systemd-nspawn hacks, podman requirement for building Fedora, etc.).
I created an issue [1], can you please vote there if you are concerned? If you
have a good argument for keeping the support, please write here or there (or
both).
[1]
https://github.com/rpm-software-management/mock/issues/755
First off, what does this mean:
1. you can't build EL7 packages anymore with mock? AKA we would need
to stop building EPEL7
2. you can't use "mock" on systems after the XYZ version?
Going from the graphs of growth, most of EL growth has been in EL7
since last year. That said.. I expect that if there is a version which
is 'known' to be the last working version of mock then people needing
it can 'keep' that version on those systems as long as they need.
Thank you,
Pavel
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproj...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.