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

lout.spec:118: 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".

lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vbas
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vbgr
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vdia
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vequ
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vfmt
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vgra
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vmat
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vpie
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vprg
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vref
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vstr
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vtbl
lout.armv6hl: E: script-without-shebang /usr/share/lout/doc/user/vtyp
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.

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    ExtractRpm                                   0.5              64.2               
    FilesCheck                                   0.1              13.1               
    TOTAL                                        0.8             100.0               

 2 packages and 0 specfiles checked; 13 errors, 1 warnings, 53 filtered, 13 badness; has taken 0.8 s