On Mon, 22 Nov 2021 at 10:15, Neal Gompa <ngompa13(a)gmail.com> wrote:
On Mon, Nov 22, 2021 at 10:12 AM Carl George <carl(a)redhat.com> wrote:
>
> On Mon, Nov 22, 2021 at 8:37 AM Vitaly Zaitsev via devel
> <devel(a)lists.fedoraproject.org> wrote:
> >
> > On 22/11/2021 15:00, Pavel Raiskup wrote:
> > > - builds will require a valid Red Hat subscription (the no-cost variant is
> I will point out that it's trivial to avoid dealing with a
> subscription by doing koji scratch builds, or by using the existing
> oraclelinux-epel-8-x86_64 mock chroot, or by submitting equivalent
> {clone}-epel-8-{arch} chroots to mock-core-configs for your preferred
> clone. Mass retiring all of your epel8 packages seems like an
> overreaction to me, but it is your choice. If you do decide to go
> that route I hope you're welcoming to other maintainers that offer to
> co-maintainer your packages to be responsible for the epel8 branch
> going forward. Ideally you would also send an email to epel-devel
> beforehand to avoid a quick retire/unretire churn for the packages
> other maintainers are interested in keeping around.
>
Note that I've submitted a PR to switch from CentOS Linux to
AlmaLinux[1] for similar reasons (my workflow would be totally broken
if I had to deal with the foibles of subscription-manager for building
packages).
[1]:
https://github.com/rpm-software-management/mock/pull/803
I would personally like to go this route (Alma+EPEL) myself. Yes I
work for Red Hat and even if I didn't I could get the copies of the
code via the Red Hat Developers program.. but dealing with a
subscription manager while trying to build on Fedora 3X etc has not
been reliable for me. [And saying that I could use a dedicated RHEL8
virtual machine is only going to work for EL8. You would need to have
fedpkg and similar tools in EPEL-9 for the tools to work in EL9.]
--
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard
battle. -- Ian MacClaren