Learn more about these different git repos.
Other Git URLs
Hi, it's me again with my horrible mutant baby, texlive. In 2020, texlive is a massive collection of noarch subpackages, generated from 9000+ tarballs. When texlive is assigned an s390x builder, it creates the perfect environment for everyone's favorite s390x bug:
DEBUG util.py:600: error: unpacking of archive failed on file /builddir/build/SOURCES/almendra.tar.xz;5eb43105: cpio: read failed - Inappropriate ioctl for device DEBUG util.py:600: error: /builddir/build/originals/texlive-2020-20.fc33.src.rpm cannot be installed
What makes it inappropriate? Who can say what offends an s390x's tender sensitivities? Nevertheless, this I/O error causes the build failure.
Since this bug has been omnipresent for years now, and since I doubt that either "build a rocket, put s390x on it, and shoot it into the sun" or "fix s390x" is likely to be well received (or happen), could we either:
1) Have a blacklist of packages which never get s390x as a noarch builder
or (more to my preference)
2) Can we simply configure Fedora koji to not use s390x build nodes for noarch builds?
I admit that neither of these solves the s390x problem, but it at least hides it from texlive. Please?
Fedora can do the second one by some ugly configuration. 1) Create channel which contains usable builders (like 'default' - s390) 2) Create policy for texlive package to use it
@kevin Is it something you are willing to do?
Metadata Update from @tkopecek: - Custom field Size adjusted to None
It would be great to document that step-by-step process in our upstream docs. Maybe a new section on https://docs.pagure.org/koji/defining_hub_policies "How to steer a troublesome package to x86_64 builders".
We actually started work on this a while back, but then hit a freeze and the person doing the work had other comitments.
We can try and restart it, but I am not sure it will have very much priority given our datacenter move work.
I've filed https://pagure.io/releng/issue/9451 to track that work.
Login to comment on this ticket.