The fwupd package has been rebased and no longer builds on arches that are not set in the %valgrind_arches macro. The new fwupd seems to look for and require valgrind support by default.

What were you trying to do that didn't work?

Build fwupd on riscv64.

What is the impact of this issue to you?

Just a FTBFS.

Please provide the package NVR for which the bug is seen:

fwupd-2.0.19-1.el10

How reproducible is this bug?:

Always.

Steps to reproduce

1. Install mock on a given riscv64 system
2. Configure mock against the proper build root
3. mock -r cfg fwupd-2.0.19-1.el10.src.rpm

Expected results

Successful build

Actual results

Failure to build due to valgrind missing.

Run-time dependency valgrind found: NO (tried pkgconfig)
meson.build:378:11: ERROR: Dependency "valgrind" not found, tried pkgconfig
A full log can be found at /builddir/build/BUILD/fwupd-2.0.19/redhat-linux-build/meson-logs/meson-log.txt
error: Bad exit status from /var/tmp/rpm-tmp.bLXttp (%build)
Bad exit status from /var/tmp/rpm-tmp.bLXttp (%build)
RPM build errors:
Child return code was: 1

Current workaround is to set riscv64 into valgrind_arches in redhat-rpmconfig