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_reques... [3] https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plug...
Miroslav
On Mon, Apr 11, 2022 at 1:37 PM Miroslav Suchý msuchy@redhat.com wrote:
Can you please tell me what is good default for you:
Centos Stream 9:
- epel-9-$arch
- centos-stream-9-$arch
- centos-stream+epel-next-9-$arch
- no default, print error and let user explicitly declare the chroot
As someone who has experienced some of the challenges, if I have to choose from those, 4 is the only one that for me results in the least surprise (you know what you are getting).
However, is there a 5th option? That would check to see if there are builds in only one chroot, and select that (with message), and if there more than one chroot that contains builds reject the request. I suppose there is also a 6th option, which would be to enable all the chroots (and let the section enabled, priorities and package versioning sort it all out). I don't really like 5 or 6, as they can lead to later surprises, but they at least have some appeal for some common use cases.
On Mon, Apr 11, 2022 at 8:38 AM Miroslav Suchý msuchy@redhat.com 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:
- epel-9-$arch
- centos-stream-9-$arch
- centos-stream+epel-next-9-$arch
- 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_reques... [3] https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plug...
Miroslav _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@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... 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 <copr> epel-9-<arch>`, why can't we have a tiny number of users do `dnf copr enable <copr> centos-stream-9-<arch>` and have the plugin guess the correct thing for the majority of users?
[0] https://bugzilla.redhat.com/show_bug.cgi?id=2058471#c1
On Tue, Jun 28, 2022 at 12:09 AM Carl George carl@redhat.com wrote:
On Mon, Apr 11, 2022 at 8:38 AM Miroslav Suchý msuchy@redhat.com 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:
- epel-9-$arch
- centos-stream-9-$arch
- centos-stream+epel-next-9-$arch
- 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_reques... [3] https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plug...
Miroslav _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@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... 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 <copr> epel-9-<arch>`, why can't we have a tiny number of users do `dnf copr enable <copr> centos-stream-9-<arch>` and have the plugin guess the correct thing for the majority of users?
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.
epel-devel@lists.fedoraproject.org