On Wed, Mar 18, 2026 at 1:10 PM Chris Adams <[email protected]> wrote: > > Once upon a time, Richard W.M. Jones <[email protected]> said: > > On Mon, Mar 16, 2026 at 09:02:32PM -0500, Chris Adams wrote: > > > I maintain the perl-WWW-Mechanize-Chrome package, which is noarch. > > > Currently, I have build tests disabled because there were several issues > > > with the tests themselves, but a developer has been cleaning them up. > > > The tests use chromium-headless, but I realized that that's not built on > > > s390x. > > > > Good suggestions already, but also wouldn't it be better for the > > upstream package skip tests where the prerequisites are not available? > > Then you wouldn't need to do anything and it'd work (albeit with out > > the full range of tests) even if built on s390x. > > The whole point of the module is to use the Chrome devtools interface to > operate the browser under remote control. Trying to run the tests > without Chrome/Chromium is rather pointless... it's about like saying > the perl module should handle skipping tests when perl isn't available. > > Plus, when tests are enabled, the SRPM BuildRequires: chromium. The > dependency cannot be satisfied on s390x, so simply trying to build there > would fail.
If you use something like %ifarch x86_64 aarch64 BuildRequires: chromium-headless %endif then this would work - the build's dependencies are resolved on each target architecture. Fabio -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
