============================ rpmlint session starts ============================ rpmlint: 2.7.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 rpmlintrc: /home/abuild/rpmbuild/SOURCES/fabtests-rpmlintrc checks: 41, packages: 2 fabtests.src: E: unused-rpmlintrc-filter "no-manual-page-for-binary fi_.*" fabtests.src: E: unused-rpmlintrc-filter "no-manual-page-for-binary runfabtests.sh" fabtests.src: E: unused-rpmlintrc-filter "no-manual-page-for-binary rft_yaml_to_junit_xml" fabtests.spec:56: 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". fabtests.spec: W: no-%check-section The spec file does not contain an %check section. Please check if the package has a testsuite and what it takes to enable the testsuite as part of the package build. If it is not possible to run it in the build environment (OBS/koji) or no testsuite exists, then please ignore this warning. You should not insert an empty %check section. fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_av.py /usr/share/fabtests/pytest/shm/test_av.py fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_cntr.py /usr/share/fabtests/pytest/shm/test_cntr.py fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_cq.py /usr/share/fabtests/pytest/shm/test_cq.py fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_dom.py /usr/share/fabtests/pytest/shm/test_dom.py fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_eq.py /usr/share/fabtests/pytest/shm/test_eq.py fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_mr.py /usr/share/fabtests/pytest/shm/test_mr.py fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_sighandler.py /usr/share/fabtests/pytest/shm/test_sighandler.py fabtests.armv7hl: W: files-duplicate /usr/share/fabtests/pytest/sm2/test_ubertest.py /usr/share/fabtests/pytest/shm/test_ubertest.py fabtests.armv7hl: W: files-duplicate /usr/share/man/man1/fi_unmap_mem.1.gz /usr/share/man/man1/fi_av_test.1.gz:/usr/share/man/man1/fi_av_xfer.1.gz:/usr/share/man/man1/fi_cm_data.1.gz:/usr/share/man/man1/fi_cntr_test.1.gz:/usr/share/man/man1/fi_cq_data.1.gz:(and 40 more) Your package contains duplicated files that are not hard- or symlinks. You should use the %fdupes macro to link the files to one. fabtests.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/rft_yaml_to_junit_xml /usr/bin/env ruby fabtests.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/runfabtests.py /usr/bin/env python3 fabtests.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/runfabtests.sh /usr/bin/env bash fabtests.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/runmultinode.py /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 BinariesCheck 1.2 61.7 ExtractRpm 0.5 25.3 TOTAL 2.0 100.0 2 packages and 0 specfiles checked; 7 errors, 11 warnings, 26 filtered, 39 badness; has taken 2.0 s