Hello EPEL.
I have just found out that the pybind11 component from c9s / RHEL 9 CRB has
been built in EPEL 9 in different version:
$ repoquery -q --repo=c9s-crb-source pybind11
pybind11-0:2.6.2-3.el9.src
pybind11-0:2.6.2-4.el9.src
$ repoquery -q --repo=RHEL9-CRB-source pybind11
pybind11-0:2.6.2-4.el9.src
$ repoquery -q --repo=epel9-source pybind11
pybind11-0:2.9.1-1.el9.src
$ repoquery -q --repo=c9s-crb pybind11-devel python3-pybind11
pybind11-devel-0:2.6.2-3.el9.i686
pybind11-devel-0:2.6.2-3.el9.x86_64
pybind11-devel-0:2.6.2-4.el9.i686
pybind11-devel-0:2.6.2-4.el9.x86_64
python3-pybind11-0:2.6.2-3.el9.x86_64
python3-pybind11-0:2.6.2-4.el9.x86_64
$ repoquery -q --repo=RHEL9-CRB pybind11-devel python3-pybind11
pybind11-devel-0:2.6.2-4.el9.i686
pybind11-devel-0:2.6.2-4.el9.x86_64
python3-pybind11-0:2.6.2-4.el9.x86_64
$ repoquery -q --repo=epel9 pybind11-devel python3-pybind11
pybind11-devel-0:2.9.1-1.el9.x86_64
python3-pybind11-0:2.9.1-1.el9.x86_64
I always assumed fedora-scm-requests admins would refuse such branch requests,
but apparently not:
https://pagure.io/releng/fedora-scm-requests/issue/42248
I've checked and we have more components that clash:
$ comm -12 <(repoquery -q
--repo=RHEL9-{BaseOS,AppStream,CRB,HighAvailability}-source -a | pkgname | sort
| uniq ) <(repoquery -q --repo=epel9-source -a | pkgname | sort | uniq)
libwmf
pybind11
tesseract
tesseract-tessdata
As well as "binary" RPMs:
$ comm -12 <(repoquery -q --repo=RHEL9-{BaseOS,AppStream,CRB,HighAvailability}
-a | pkgname | sort | uniq ) <(repoquery -q --repo=epel9 -a | pkgname | sort |
uniq)
anthy-unicode-devel
double-conversion-devel
libwmf
libwmf-lite
pybind11-devel
python3-pybind11
tesseract
tesseract-devel
tesseract-langpack-eng
tesseract-tessdata-doc
And apparently, this is not just CRB, but also AppStream:
$ repoquery -q --repo=RHEL9-{BaseOS,AppStream,CRB,HighAvailability}{,-source}
--queryformat='%{name} %{reponame}' libwmf pybind11 tesseract
tesseract-tessdata anthy-unicode-devel double-conversion-devel libwmf-lite
pybind11-devel python3-pybind11 tesseract-devel tesseract-langpack-eng
tesseract-tessdata-doc
anthy-unicode-devel RHEL9-CRB
double-conversion-devel RHEL9-CRB
libwmf RHEL9-AppStream
libwmf RHEL9-AppStream-source
libwmf-lite RHEL9-AppStream
pybind11 RHEL9-CRB-source
pybind11-devel RHEL9-CRB
python3-pybind11 RHEL9-CRB
tesseract RHEL9-AppStream
tesseract RHEL9-AppStream-source
tesseract-devel RHEL9-CRB
tesseract-langpack-eng RHEL9-AppStream
tesseract-tessdata RHEL9-AppStream-source
tesseract-tessdata-doc RHEL9-AppStream
Do I understand correctly that this is still *not* allowed? If so, what can we
do to prevent it?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
