============================ 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: 42, packages: 7 alsa.spec:287: 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". alsa.spec:27: E: obsolete-suse-version-check 1200 alsa.spec:79: E: obsolete-suse-version-check 1310 alsa.spec:82: E: obsolete-suse-version-check 1200 alsa.spec:126: E: obsolete-suse-version-check 1110 The specfile contains a comparison of %suse_version against a suse release that is no longer in maintenance. Consider removing obsolete parts of your spec file to make it more readable. alsa.i586: E: no-binary alsa-devel.i586: E: no-binary alsa-topology-devel.i586: E: no-binary The package should be of the noarch architecture because it doesn't contain any binaries. alsa.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. alsa-devel.i586: W: files-duplicate /usr/include/sys/asoundlib.h /usr/include/asoundlib.h alsa-docs.noarch: W: files-duplicate /usr/share/doc/packages/alsa-docs/search/pages_1.js /usr/share/doc/packages/alsa-docs/search/all_1.js alsa-docs.noarch: W: files-duplicate /usr/share/doc/packages/alsa-docs/search/pages_2.js /usr/share/doc/packages/alsa-docs/search/all_2.js alsa-docs.noarch: W: files-duplicate /usr/share/doc/packages/alsa-docs/search/variables_a.js /usr/share/doc/packages/alsa-docs/search/all_d.js alsa-docs.noarch: W: files-duplicate /usr/share/doc/packages/alsa-docs/search/pages_c.js /usr/share/doc/packages/alsa-docs/search/all_e.js Your package contains duplicated files that are not hard- or symlinks. You should use the %fdupes macro to link the files to one. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files FilesCheck 0.9 23.3 ExtractRpm 0.9 22.6 SpecCheck 0.5 14.4 BashismsCheck 0.4 10.1 BuildRootAndDateCheck 0.3 7.7 FilelistCheck 0.2 4.6 BinariesCheck 0.1 3.8 SUIDPermissionsCheck 0.1 2.9 SignatureCheck 0.1 2.9 TOTAL 3.8 100.0 7 packages and 0 specfiles checked; 7 errors, 7 warnings, 96 filtered, 7 badness; has taken 3.9 s