On Mon, Mar 7, 2022 at 4:01 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote:
(snip)
> == Scope ==
> ==== Change owners ====
> * we will simiply stop building i686 pkg in rawhide
>
> ==== Other developers ====
> * may notice the multilib i686 java missing.
> * it is up to them to drop i686 builds or to povide workaround (if possible)
Hm, that sounds potentially risky way to do this. And also just breaks
stuff and leaves it to the package maintainers to fix things.
Did you consider adding a %{java_arches} macro that can be used to
limit builds of noarch Java packages to non-i686 architectures?
Did you check the dependency tree of the non-noarch Java packages? For
example, are there any important, non-Java packages that depend on
architecture-specific Java packages, like JNA?
For example, these packages might be problematic:
- jna ← jline
- jna ← libvirt-java
- jna ← mariadb-java-client
- jna ← scala
- jna ← svnkit
Will package maintainers need to exclude all those packages (and, in
turn, all their dependent packages) from i686?
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
