[EPEL-devel] Re: Default for 'dnf copr enable'
On Tue, Jun 28, 2022 at 12:09 AM Carl George wrote: > > On Mon, Apr 11, 2022 at 8:38 AM Miroslav Suchý wrote: > > > > Hi. > > I want to get your feedback: > > > > When you enable Copr repository you can run: > >dnf copr enable myname/project epel-9-x86_64 > > The last parameter is optional and most people usually runs: > >dnf copr enable myname/project > > > > Dnf-plugins-core tries to guess [3] the correct chroot. On Fedora it is > > easy. > > For Fedora 35 it is fedora-35-$arch. > > But for RHEL/Centos/Centos Stream it is a bit tricky. > > > > E.g. for C9S we now defaults to centos-stream-9-$arch. But this gets some > > pushback [1,2]. I want to know if this opinion > > is minority or whether majority of people wants this. > > I do not think there is an option which is correct. So it is about choosing > > a default which is correct for most people. > > > > Can you please tell me what is good default for you: > > > > Centos Stream 9: > > 1) epel-9-$arch > > 2) centos-stream-9-$arch > > 3) centos-stream+epel-next-9-$arch > > 4) no default, print error and let user explicitly declare the chroot > > > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=2058471 > > [2] > > https://gitlab.com/redhat/centos-stream/rpms/dnf-plugins-core/-/merge_requests/7 > > [3] > > https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plugins/copr.py#L472 > > > > Miroslav > > ___ > > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > > To unsubscribe send an email to epel-devel-le...@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.fedoraproject.org > > Do not reply to spam on the list, report it: > > https://pagure.io/fedora-infrastructure > > In most cases, epel-9-$arch will be the correct choice. In the bug > [0] it is suggested that when the guess is wrong it's simple to add > the chroot as an explicit argument. Instead of making the majority of > users do `dnf copr enable epel-9-`, why can't we have a > tiny number of users do `dnf copr enable > centos-stream-9-` and have the plugin guess the correct thing > for the majority of users? > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=2058471#c1 > It should have never been changed to behave differently in the first place. The only real acceptable alternative other than the main epel chroots is to have it use epel-next chroots for CentOS Stream. However, those are not available in COPR at this time, so we use the EPEL ones. -- 真実はいつも一つ！/ Always, there's only one truth! ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Default for 'dnf copr enable'
On Mon, Apr 11, 2022 at 8:38 AM Miroslav Suchý wrote: > > Hi. > I want to get your feedback: > > When you enable Copr repository you can run: >dnf copr enable myname/project epel-9-x86_64 > The last parameter is optional and most people usually runs: >dnf copr enable myname/project > > Dnf-plugins-core tries to guess [3] the correct chroot. On Fedora it is easy. > For Fedora 35 it is fedora-35-$arch. > But for RHEL/Centos/Centos Stream it is a bit tricky. > > E.g. for C9S we now defaults to centos-stream-9-$arch. But this gets some > pushback [1,2]. I want to know if this opinion > is minority or whether majority of people wants this. > I do not think there is an option which is correct. So it is about choosing a > default which is correct for most people. > > Can you please tell me what is good default for you: > > Centos Stream 9: > 1) epel-9-$arch > 2) centos-stream-9-$arch > 3) centos-stream+epel-next-9-$arch > 4) no default, print error and let user explicitly declare the chroot > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=2058471 > [2] > https://gitlab.com/redhat/centos-stream/rpms/dnf-plugins-core/-/merge_requests/7 > [3] > https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plugins/copr.py#L472 > > Miroslav > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@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.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure In most cases, epel-9-$arch will be the correct choice. In the bug [0] it is suggested that when the guess is wrong it's simple to add the chroot as an explicit argument. Instead of making the majority of users do `dnf copr enable epel-9-`, why can't we have a tiny number of users do `dnf copr enable centos-stream-9-` and have the plugin guess the correct thing for the majority of users? [0] https://bugzilla.redhat.com/show_bug.cgi?id=2058471#c1 -- Carl George ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0dde709329 chromium-102.0.5005.115-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing bird2-2.0.10-1.el7 rpminspect-1.10-1.el7 Details about builds: bird2-2.0.10-1.el7 (FEDORA-EPEL-2022-28caa5886e) BIRD Internet Routing Daemon Update Information: # BIRD 2.0.10 (2022-06-16)* BGP performance improvements * BFD: New `strict bind` option * RPKI: VRF support * Allow use of 240.0.0.0/4 as a private range * BIRD client uses exit status to report errors * Important bugfixes ChangeLog: * Tue Jun 28 2022 Robert Scheck - 2.0.10-1 - Upgrade to 2.0.10 (#2101352) References: [ 1 ] Bug #2101352 - bird-2.0.10 is available https://bugzilla.redhat.com/show_bug.cgi?id=2101352 rpminspect-1.10-1.el7 (FEDORA-EPEL-2022-c7bcd29f38) Build deviation compliance tool Update Information: Upgrade to rpminspect-1.10 ChangeLog: * Mon Jun 27 2022 David Cantrell - 1.10-1 - Upgrade to rpminspect-1.10 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
