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

jimtcl.spec:103: 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".

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

jimtcl.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/jimdb /usr/bin/env jimsh
jimtcl-devel.armv7hl: E: env-script-interpreter (Badness: 9) /usr/bin/build-jim-ext /usr/bin/env jimsh
This script uses 'env' as an interpreter. For the rpm runtime dependency
detection to work, the shebang #!/usr/bin/env <interpreter>  needs to be
patched into #!/usr/bin/<interpreter>  otherwise the package dependency
generator merely adds a dependency on /usr/bin/env rather than the actual
interpreter /usr/bin/<interpreter>.  Alternatively, if the file should not be
executed, then ensure that it is not marked as executable or don't install it
in a path that is reserved for executables.

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

 4 packages and 0 specfiles checked; 3 errors, 1 warnings, 12 filtered, 19 badness; has taken 0.6 s