============================ 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: 31 jetty-minimal-javadoc.noarch: W: package-with-huge-docs 99% More than half the size of your package is documentation. Consider splitting it into a -doc subpackage. jetty-minimal.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 3.9 54.7 FilesCheck 1.4 19.4 BuildRootAndDateCheck 0.6 8.9 SignatureCheck 0.5 6.6 ZipCheck 0.2 2.8 BashismsCheck 0.2 2.2 FilelistCheck 0.1 1.8 TagsCheck 0.1 1.5 TOTAL 7.0 100.0 31 packages and 0 specfiles checked; 0 errors, 2 warnings, 101 filtered, 0 badness; has taken 7.2 s