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

sblim-cim-client2-manual.noarch: W: wrong-file-end-of-line-encoding /usr/share/doc/packages/sblim-cim-client2-2.2.5/org/sblim/cimclient/samples/indication.xml
This file has wrong end-of-line encoding, usually caused by creation or
modification on a non-Unix system. It could prevent it from being displayed
correctly in some circumstances.

sblim-cim-client2-javadoc.noarch: W: package-with-huge-docs 100%
sblim-cim-client2-manual.noarch: W: package-with-huge-docs 100%
More than half the size of your package is documentation. Consider splitting
it into a -doc subpackage.

sblim-cim-client2.spec:41: E: obsolete-suse-version-check 1010
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.

sblim-cim-client2.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                                   0.5              35.0               
    FilesCheck                                   0.4              24.9               
    BuildRootAndDateCheck                        0.2              10.1               
    ZipCheck                                     0.1               9.2               
    TOTAL                                        1.5             100.0               

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