============================ rpmlint session starts ============================ rpmlint: 2.8.0 configuration: /opt/testing/lib/python3.13/rpmlint/configdefaults.toml /opt/testing/share/rpmlint/cron-whitelist.toml /opt/testing/share/rpmlint/dbus-services.toml /opt/testing/share/rpmlint/device-files-whitelist.toml /opt/testing/share/rpmlint/licenses.toml /opt/testing/share/rpmlint/opensuse.toml /opt/testing/share/rpmlint/pam-modules.toml /opt/testing/share/rpmlint/permissions-whitelist.toml /opt/testing/share/rpmlint/pie-executables.toml /opt/testing/share/rpmlint/polkit-rules-whitelist.toml /opt/testing/share/rpmlint/scoring.toml /opt/testing/share/rpmlint/security.toml /opt/testing/share/rpmlint/sudoers-whitelist.toml /opt/testing/share/rpmlint/sysctl-whitelist.toml /opt/testing/share/rpmlint/systemd-tmpfiles.toml /opt/testing/share/rpmlint/users-groups.toml /opt/testing/share/rpmlint/world-writable-whitelist.toml /opt/testing/share/rpmlint/zypper-plugins.toml /etc/xdg/rpmlint/scoring-strict.override.toml checks: 41, packages: 3 valgrind.spec:249: W: shared-dir-glob-in-files %{_bindir}/* The %files section contains "%{_bindir}/*", "%{_datadir}/*", "%{_docdir}/*", "%{_includedir}/*" or "%{_mandir}/*". These can lead to packagers not noticing when upstream adds new and possibly conflicting files in these directories. Therefore, files in these directories should be explicitely listed like "%{_bindir}/foobar" or "%{_includedir}/foobar.h". valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/cachegrind-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/callgrind-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/dhat-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/drd-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/exp-bbv-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/helgrind-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/lackey-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/massif-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/memcheck-arm-linux valgrind.armv7hl: W: position-independent-executable-suggested /usr/libexec/valgrind/none-arm-linux This executable should be position independent (all binaries should). Check that it is built with -fPIE/-fpie in compiler flags and -pie in linker flags. valgrind-devel.armv7hl: E: no-binary The package should be of the noarch architecture because it doesn't contain any binaries. valgrind.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/callgrind_annotate /usr/bin/env perl valgrind.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/callgrind_control /usr/bin/env perl valgrind.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/cg_annotate /usr/bin/env python3 valgrind.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/cg_diff /usr/bin/env python3 valgrind.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/cg_merge /usr/bin/env python3 This script uses 'env' as an interpreter. For the rpm runtime dependency detection to work, the shebang #!/usr/bin/env needs to be patched into #!/usr/bin/ otherwise the package dependency generator merely adds a dependency on /usr/bin/env rather than the actual interpreter /usr/bin/. Alternatively, if the file should not be executed, then ensure that it is not marked as executable or don't install it in a path that is reserved for executables. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files ExtractRpm 2.2 75.5 BinariesCheck 0.4 13.2 TOTAL 3.0 100.0 3 packages and 0 specfiles checked; 6 errors, 11 warnings, 22 filtered, 46 badness; has taken 3.0 s