============================ 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/apptainer-rpmlintrc checks: 41, packages: 6 apptainer.spec:167: 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". apptainer.armv6hl: W: no-soname /usr/libexec/apptainer/lib/offsetpreload.so The library has no soname. apptainer.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. apptainer.spec:72: W: macro-in-comment %ix86 There is a unescaped macro after a shell style comment in the specfile. Macros are expanded everywhere, so check if it can cause a problem in this case and escape the macro with another leading % if appropriate. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files ExtractRpm 8.5 71.8 BinariesCheck 2.8 23.3 SignatureCheck 0.2 2.0 TOTAL 11.9 100.0 6 packages and 0 specfiles checked; 0 errors, 4 warnings, 321 filtered, 0 badness; has taken 11.9 s