On Fri, Apr 22, 2022 at 07:53:10PM +0200, Miro Hrončok wrote: > Hello, > > I've been trying to debug a segfault during %check that only occurs in epel9 > Koji, but not in mock. > > At the end, I compared the list of packages with: ...snip... > > This seems like my local mock has newer c9s packages than the Koji build > repo. Is that expected, or is pulling c9s packages into the build repo stuck > on Koji side? It's expected, because epel9 is going to be tracking RHEL9 as soon as it's out, so we cut the sync when CentOS stream 9 started tracking 9.1 packages. Your local mock likely has 9.1 packages. > Actually, I got an idea that EPEL 9 Koji might already be using (internal?) > RHEL 9.0, possibly I have missed this switch... However, the > centos-stream-release package contraditcs taht idea :/ > > I've checked with an EPEL 9 Next Koji scratchbuild and it got e.g. > pyproject-rpm-macros-1.0.1-1.el9. It's not using rhel9 (yet) just a snapshot of stream9 back when it was tracking 9.0. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
