============================ rpmlint session starts ============================
rpmlint: 2.8.0
configuration:
    /opt/testing/lib64/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:294: 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:86: E: obsolete-suse-version-check 1310
alsa.spec:89: E: obsolete-suse-version-check 1200
alsa.spec:133: 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.aarch64: 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.aarch64: 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
    ExtractRpm                                   0.9              47.7               
    BashismsCheck                                0.3              14.9               
    FilesCheck                                   0.2              10.4               
    SignatureCheck                               0.1               5.8               
    TOTAL                                        1.8             100.0               

 7 packages and 0 specfiles checked; 5 errors, 7 warnings, 96 filtered, 5 badness; has taken 1.9 s