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

python310-berkeleydb.aarch64: W: package-with-huge-docs 74%
python311-berkeleydb.aarch64: W: package-with-huge-docs 71%
python312-berkeleydb.aarch64: W: package-with-huge-docs 72%
More than half the size of your package is documentation. Consider splitting
it into a -doc subpackage.

python310-berkeleydb.aarch64: E: non-executable-script /usr/lib64/python3.10/site-packages/berkeleydb/dbshelve.py 644 /usr/bin/env python
python311-berkeleydb.aarch64: E: non-executable-script /usr/lib64/python3.11/site-packages/berkeleydb/dbshelve.py 644 /usr/bin/env python
python312-berkeleydb.aarch64: E: non-executable-script /usr/lib64/python3.12/site-packages/berkeleydb/dbshelve.py 644 /usr/bin/env python
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.

python310-berkeleydb-devel.aarch64: E: no-binary
python311-berkeleydb-devel.aarch64: E: no-binary
python312-berkeleydb-devel.aarch64: E: no-binary
The package should be of the noarch architecture because it doesn't contain
any binaries.

python310-berkeleydb.aarch64: W: files-duplicate /usr/share/doc/packages/python310-berkeleydb/html/images/bitcoin.png /usr/share/doc/packages/python310-berkeleydb/bitcoin.png
python311-berkeleydb.aarch64: W: files-duplicate /usr/share/doc/packages/python311-berkeleydb/html/images/bitcoin.png /usr/share/doc/packages/python311-berkeleydb/bitcoin.png
python312-berkeleydb.aarch64: W: files-duplicate /usr/share/doc/packages/python312-berkeleydb/html/images/bitcoin.png /usr/share/doc/packages/python312-berkeleydb/bitcoin.png
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
    ExtractRpm                                   0.1              28.2               
    SignatureCheck                               0.1              24.7               
    TOTAL                                        0.5             100.0               

 7 packages and 0 specfiles checked; 6 errors, 6 warnings, 18 filtered, 6 badness; has taken 0.5 s