============================ 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: 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.armv6hl: E: no-binary
alsa-devel.armv6hl: E: no-binary
alsa-topology-devel.armv6hl: 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.armv6hl: 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_0.js /usr/share/doc/packages/alsa-docs/search/all_0.js
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_11.js /usr/share/doc/packages/alsa-docs/search/all_12.js
alsa-docs.noarch: W: files-duplicate /usr/share/doc/packages/alsa-docs/search/functions_0.js /usr/share/doc/packages/alsa-docs/search/all_2.js
alsa-docs.noarch: W: files-duplicate /usr/share/doc/packages/alsa-docs/search/pages_b.js /usr/share/doc/packages/alsa-docs/search/all_c.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.8              46.6               
    BashismsCheck                                0.3              16.2               
    SpecCheck                                    0.1               7.7               
    FilesCheck                                   0.1               6.9               
    TOTAL                                        1.7             100.0               

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