Hi Florian, > Yes, I understood that. x86_64 buildroots only have x86_64 packages in > Koji. You cannot build and run 32-bit binaries (unless you put them > together completely from scratch, without help from i686 RPM packages). alright, thank you for clarifying! Curiously though, the Koji build for epel9 does find and install a `glibc-static.i686` package from the `build` repo: https://kojipkgs.fedoraproject.org//work/tasks/9858/81959858/root.log I presume this is a CentOS package and has nothing to do with Fedora's glibc32 hack, but I still find it interesting that it is found on epel9 but not on epel8. Is there an overview of - or a simple way to find out - how many and which Fedora packages currently rely on the glibc32 hack? > Do we have CI for EPEL? You could run the tests there. Given that I'm a freshman Fedora developer, I'm not familiar with that part of the Fedora infrastructure yet. Could someone with pertinent knowledge weigh in on this topic? Thanks, Christoph
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
