On Mon, Mar 7, 2022 at 8:15 PM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > Thanks for your feedback, I'll respond inline. > > This begs several questions that would probably need to be clarified e.g. in > the packaging guidelines. For example: > > ------ > > I am adding a brand new package to multiple Fedora releases. The package is not > noarch. It successfully builds on i686. What am I supposed to do? > > a) build it on i686, until it fails there > b) excludearch %ix86 right away not to create a dead dep tree > c) excludearch %ix86 on F37+ only, as this is a F37 change I think new packages could probably exclude i686 on all branches, since with new packages, assuming the i686 packages are unused is always true. :) > ------- > > I am updating a package that no longer builds on i686. How do I know if I can > exclude it safely? What checks do I run? Am I allowed to push this update to > stable Fedora releases? If .spec files are maintained in a "use conditionals and merge everywhere" fashion, then the "ExcludeArch: i686" statement would need to be wrapped in a "%if %fedora >= 37" conditional. So no, in general the change for excluding i686 must not be pushed to stable branches. > ------- > > My package is noarch but has multiple arched dependencies. How do I properly > make Koji not attempt to build it on i686? I think this case is already covered in the Packaging Guidelines for "noarch packages with unported dependencies": https://docs.fedoraproject.org/en-US/packaging-guidelines/#_noarch_with_unported_dependencies Fabio _______________________________________________ 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