============================ 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: 4

libotf.spec:79: W: shared-dir-glob-in-files %{_bindir}/*
libotf.spec:85: W: shared-dir-glob-in-files %{_includedir}/*
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".

libotf.armv6hl: E: script-without-shebang /usr/share/licenses/libotf/COPYING
This text file has executable bits set or is located in a path dedicated for
executables, but lacks a shebang and cannot thus be executed. If the file is
meant to be an executable script, add the shebang, otherwise remove the
executable bits or move the file elsewhere.

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

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

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    ExtractRpm                                   0.3              37.3               
    BashismsCheck                                0.2              32.0               
    BinariesCheck                                0.1              19.7               
    TOTAL                                        0.7             100.0               

 4 packages and 0 specfiles checked; 2 errors, 3 warnings, 19 filtered, 2 badness; has taken 0.7 s