Hi,
Due to a dependency on Eclipse, findbugs-contrib can no longer be built on non-64-bit architectures. According to https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_bui...:
If a Fedora package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch.
So I added ExcludeArch to the findbugs-contrib spec:
https://src.fedoraproject.org/rpms/findbugs-contrib/c/35db66939b8d262a6c0494...
which I based on a similar change for eclipse itself:
https://src.fedoraproject.org/rpms/eclipse/c/1b7ea00088e02a126cf0f47777031f9...
For some reason though, the findbugs-contrib build earlier today for the F31 mass rebuild was done on an i686 builder:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1323580 https://koji.fedoraproject.org/koji/taskinfo?taskID=36487003
and failed with an error:
BUILDSTDERR: error: Architecture is excluded: i386
The same thing happened with a recent Koschei build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=36306707
Have I gone about this the wrong way?
Rich
"RF" == Richard Fearn richardfearn@gmail.com writes:
RF> According to RF> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_bui...:
If a Fedora package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch.
Sure, but also just a small bit further down the document is https://docs.fedoraproject.org/en-US/packaging-guidelines/#_noarch_with_unpo... which tells you what to do if you have a noarch package that has dependencies which are not present on all architectures.
This involves some rather odd magic in koji, and so what is in the guidelines is the best information that we've been able to extract from releng and the koji source code.
Can you try the ExclusiveArch: method shown in the example, keeping in mind that you must explicitly list "noarch" at the end? Of course, a successful build isn't a guarantee because the build host you get may be completely random. What we'd like to know is if someone finds a failure using the recommended method (which would imply that we need to get something fixed or find another way to accomplish this).
- J<
Dne 25. 07. 19 v 23:07 Jason L Tibbitts III napsal(a):
"RF" == Richard Fearn richardfearn@gmail.com writes:
RF> According to RF> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_bui...:
If a Fedora package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch.
Sure, but also just a small bit further down the document is https://docs.fedoraproject.org/en-US/packaging-guidelines/#_noarch_with_unpo... which tells you what to do if you have a noarch package that has dependencies which are not present on all architectures.
This involves some rather odd magic in koji, and so what is in the guidelines is the best information that we've been able to extract from releng and the koji source code.
Can you try the ExclusiveArch: method shown in the example, keeping in mind that you must explicitly list "noarch" at the end? Of course, a successful build isn't a guarantee because the build host you get may be completely random. What we'd like to know is if someone finds a failure using the recommended method (which would imply that we need to get something fixed or find another way to accomplish this).
These tickets might be of interest:
https://pagure.io/releng/issue/7671
https://pagure.io/koji/issue/789
Vít
- J<
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
Thanks, Jason and Vit, for your replies. Unfortunately it looks like many of findbugs-contrib's Java dependencies are being retired at the moment, so I need to decide what to do about that first...
Rich
On Sat, Aug 17, 2019, 11:33 Richard Fearn richardfearn@gmail.com wrote:
Thanks, Jason and Vit, for your replies. Unfortunately it looks like many of findbugs-contrib's Java dependencies are being retired at the moment, so I need to decide what to do about that first...
Let me suggest joining the Java SIG (if you haven't already), taking over the orphaned / retired packages your own packages depend on, and adding them to the set of packages maintained by the SIG.
That's probably the most productive way forward, provided you even want to continue maintaining findbugs-contrib.
Fabio
Rich
-- Richard Fearn richardfearn@gmail.com _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
-
Fabio Valentini -
Jason L Tibbitts III -
Richard Fearn -
Vít Ondruch