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

python-simplebayes.src: W: tag-in-description Provides:
Something that looks like a tag was found in the package's description. This
may indicate a problem where the tag was not actually parsed as a tag but just
textual description content, thus being a no-op.  Verify if this is the case,
and move the tag to a place in the specfile where %description won't fool the
specfile parser, and rebuild the package.

python-simplebayes.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.

python311-simplebayes.noarch: W: files-duplicate /usr/lib/python3.11/site-packages/simplebayes/__pycache__/categories.cpython-311.pyc /usr/lib/python3.11/site-packages/simplebayes/__pycache__/categories.cpython-311.opt-1.pyc
python311-simplebayes.noarch: W: files-duplicate /usr/lib/python3.11/site-packages/simplebayes/__pycache__/category.cpython-311.pyc /usr/lib/python3.11/site-packages/simplebayes/__pycache__/category.cpython-311.opt-1.pyc
python312-simplebayes.noarch: W: files-duplicate /usr/lib/python3.12/site-packages/simplebayes/__pycache__/categories.cpython-312.pyc /usr/lib/python3.12/site-packages/simplebayes/__pycache__/categories.cpython-312.opt-1.pyc
python312-simplebayes.noarch: W: files-duplicate /usr/lib/python3.12/site-packages/simplebayes/__pycache__/category.cpython-312.pyc /usr/lib/python3.12/site-packages/simplebayes/__pycache__/category.cpython-312.opt-1.pyc
python313-simplebayes.noarch: W: files-duplicate /usr/lib/python3.13/site-packages/simplebayes/__pycache__/categories.cpython-313.pyc /usr/lib/python3.13/site-packages/simplebayes/__pycache__/categories.cpython-313.opt-1.pyc
python313-simplebayes.noarch: W: files-duplicate /usr/lib/python3.13/site-packages/simplebayes/__pycache__/category.cpython-313.pyc /usr/lib/python3.13/site-packages/simplebayes/__pycache__/category.cpython-313.opt-1.pyc
Your package contains duplicated files that are not hard- or symlinks. You
should use the %fdupes macro to link the files to one.

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

 4 packages and 0 specfiles checked; 0 errors, 8 warnings, 5 filtered, 0 badness; has taken 0.1 s