============================ rpmlint session starts ============================
rpmlint: 2.6.1
configuration:
    /opt/testing/lib/python3.11/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: 4

libaom-devel.armv6hl: E: no-binary
The package should be of the noarch architecture because it doesn't contain
any binaries.

libaom.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.

libaom.spec:160: W: libdir-macro-in-noarch-package %{name}%{sover} %{_libdir}/%{name}.so.*
libaom.spec:164: W: libdir-macro-in-noarch-package devel %{_libdir}/%{name}.so
libaom.spec:165: W: libdir-macro-in-noarch-package devel %{_libdir}/pkgconfig/aom.pc
The %{_libdir} or %{_lib} macro was found in a noarch package in a section
that gets included in binary packages.  This is most likely an error because
these macros are expanded on the build host and their values vary between
architectures, probably resulting in a package that does not work properly on
all architectures at runtime. Investigate whether the package is really
architecture independent or if some other dir/macro should be instead.

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    ExtractRpm                                   0.1              35.7               
    TOTAL                                        0.4             100.0               

 4 packages and 0 specfiles checked; 1 errors, 4 warnings, 11 filtered, 1 badness; has taken 0.4 s