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

btrfsprogs.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-%{**}}

btrfsprogs.spec:22: E: obsolete-suse-version-check 1310
btrfsprogs.spec:71: E: obsolete-suse-version-check 1310
btrfsprogs.spec:78: E: obsolete-suse-version-check 1310
The specfile contains a comparison of %suse_version against a suse release
that is no longer in maintenance. Consider removing obsolete parts of your
spec file to make it more readable.

btrfsprogs-bash-completion.armv6hl: E: no-binary
libbtrfs-devel.armv6hl: E: no-binary
libbtrfsutil-devel.armv6hl: E: no-binary
The package should be of the noarch architecture because it doesn't contain
any binaries.

btrfsprogs.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
    ExtractRpm                                   2.1              68.9               
    BinariesCheck                                0.4              11.9               
    BashismsCheck                                0.2               4.9               
    SignatureCheck                               0.1               4.7               
    TOTAL                                        3.0             100.0               

 10 packages and 0 specfiles checked; 6 errors, 2 warnings, 44 filtered, 6 badness; has taken 3.1 s