============================ rpmlint session starts ============================ rpmlint: 2.5.0 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: 2 xselection.spec: E: superfluous-%clean-section The spec section %clean should not be used any longer. RPM provides its own clean logic. xselection.x86_64: W: self-obsoletion xselect obsoletes xselect 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. xselection.spec: W: no-%check-section The spec file does not contain an %check section. Even if some packages don't directly need it, section markers may be overridden in rpm's configuration to provide additional 'under the hood' functionality. Add the section, even if empty. xselection.x86_64: W: name-repeated-in-summary XSelection xselection.src: W: name-repeated-in-summary XSelection The name of the package is repeated in its summary. Make the summary brief and to the point without including redundant information in it. xselection.spec:47: W: macro-in-comment %define There is a unescaped macro after a shell style comment in the specfile. Macros are expanded everywhere, so check if it can cause a problem in this case and escape the macro with another leading % if appropriate. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files TOTAL 0.0 100.0 2 packages and 0 specfiles checked; 1 errors, 5 warnings, 5 filtered, 1 badness; has taken 0.0 s