============================ rpmlint session starts ============================
rpmlint: 2.6.1
configuration:
    /opt/testing/lib64/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: 5

python-empy.spec:19: W: python-module-def %{?!python_module:%define python_module() python-%{**} python3-%{**}}
The spec file contains a conditional definition of python_module macro, this
macro is present in recent versions of python-rpm-macros. The following
conditional python_module macro definition can be removed:
%{?!python_module:%define python_module() python-%{**} python3-%{**}}

python310-empy.noarch: I: package-supports-update-alternatives
python311-empy.noarch: I: package-supports-update-alternatives
python312-empy.noarch: I: package-supports-update-alternatives
python313-empy.noarch: I: package-supports-update-alternatives
python310-empy.noarch: E: non-executable-script /usr/lib/python3.10/site-packages/em.py 644 /usr/bin/env python3
python310-empy.noarch: E: non-executable-script /usr/lib/python3.10/site-packages/emdoc.py 644 /usr/bin/env python3
python310-empy.noarch: E: non-executable-script /usr/lib/python3.10/site-packages/emhelp.py 644 /usr/bin/env python3
python310-empy.noarch: E: non-executable-script /usr/lib/python3.10/site-packages/emlib.py 644 /usr/bin/env python3
python311-empy.noarch: E: non-executable-script /usr/lib/python3.11/site-packages/em.py 644 /usr/bin/env python3
python311-empy.noarch: E: non-executable-script /usr/lib/python3.11/site-packages/emdoc.py 644 /usr/bin/env python3
python311-empy.noarch: E: non-executable-script /usr/lib/python3.11/site-packages/emhelp.py 644 /usr/bin/env python3
python311-empy.noarch: E: non-executable-script /usr/lib/python3.11/site-packages/emlib.py 644 /usr/bin/env python3
python312-empy.noarch: E: non-executable-script /usr/lib/python3.12/site-packages/em.py 644 /usr/bin/env python3
python312-empy.noarch: E: non-executable-script /usr/lib/python3.12/site-packages/emdoc.py 644 /usr/bin/env python3
python312-empy.noarch: E: non-executable-script /usr/lib/python3.12/site-packages/emhelp.py 644 /usr/bin/env python3
python312-empy.noarch: E: non-executable-script /usr/lib/python3.12/site-packages/emlib.py 644 /usr/bin/env python3
python313-empy.noarch: E: non-executable-script /usr/lib/python3.13/site-packages/em.py 644 /usr/bin/env python3
python313-empy.noarch: E: non-executable-script /usr/lib/python3.13/site-packages/emdoc.py 644 /usr/bin/env python3
python313-empy.noarch: E: non-executable-script /usr/lib/python3.13/site-packages/emhelp.py 644 /usr/bin/env python3
python313-empy.noarch: E: non-executable-script /usr/lib/python3.13/site-packages/emlib.py 644 /usr/bin/env python3
This text file contains a shebang or is located in a path dedicated for
executables, but lacks the executable bits and cannot thus be executed. If the
file is meant to be an executable script, add the executable bits, otherwise
remove the shebang or move the file elsewhere.

python-empy.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
    TOTAL                                        0.2             100.0               

 5 packages and 0 specfiles checked; 16 errors, 2 warnings, 26 filtered, 16 badness; has taken 0.2 s