============================ rpmlint session starts ============================ rpmlint: 2.6.1 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: 5 libtidy-devel.x86_64: W: obsolete-not-provided libtidy-0_99-0-devel If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. tidy.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. tidy-doc.noarch: W: files-duplicate /usr/share/doc/packages/tidy-doc/api/search/pages_e.js /usr/share/doc/packages/tidy-doc/api/search/all_16.js tidy-doc.noarch: W: files-duplicate /usr/share/doc/packages/tidy-doc/api/search/classes_0.js /usr/share/doc/packages/tidy-doc/api/search/all_5.js Your package contains duplicated files that are not hard- or symlinks. You should use the %fdupes macro to link the files to one. libtidy-devel.x86_64: E: double-slash-in-pkgconfig-path /usr/lib64/pkgconfig/tidy.pc libdir=${exec_prefix}//usr/lib64 This pkg-config file contains a path with a double slash ('//') in it. This will break debugedit when stripping debug symbols during package building if these paths have been passed to gcc, and fail with the following error: canonicalization unexpectedly shrank by one character. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files ExtractRpm 0.4 60.6 TOTAL 0.7 100.0 5 packages and 0 specfiles checked; 1 errors, 4 warnings, 9 filtered, 1 badness; has taken 0.7 s