============================ 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 xml-commons-apis.noarch: W: self-obsoletion xerces-j2-xml-apis obsoletes xerces-j2-xml-apis xml-commons-apis.noarch: W: self-obsoletion xml-commons-jaxp-1.1-apis obsoletes xml-commons-jaxp-1.1-apis xml-commons-apis.noarch: W: self-obsoletion xml-commons-jaxp-1.2-apis obsoletes xml-commons-jaxp-1.2-apis xml-commons-apis.noarch: W: self-obsoletion xml-commons-jaxp-1.3-apis obsoletes xml-commons-jaxp-1.3-apis xml-commons-apis.noarch: W: self-obsoletion xml-commons-jaxp-1.4-apis obsoletes xml-commons-jaxp-1.4-apis The package obsoletes itself. This is known to cause errors in various tools and should thus be avoided, usually by using appropriately versioned Obsoletes and/or Provides and avoiding unversioned ones. xml-commons-apis-javadoc.noarch: W: package-with-huge-docs 100% xml-commons-apis-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. xml-commons-apis.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.3 37.3 ZipCheck 0.2 21.3 FilesCheck 0.1 15.6 TOTAL 0.8 100.0 4 packages and 0 specfiles checked; 0 errors, 8 warnings, 32 filtered, 0 badness; has taken 0.9 s