============================ 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: 3 opensp.spec: E: superfluous-%clean-section The spec section %clean should not be used any longer. RPM provides its own clean logic. opensp.x86_64: W: self-obsoletion sp obsoletes sp opensp.x86_64: W: self-obsoletion sp_libs obsoletes sp_libs opensp-devel.x86_64: W: self-obsoletion sp-devel obsoletes sp-devel 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. opensp.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. opensp.spec:115: W: make-check-outside-check-section # make check Make check or other automated regression test should be run in %check, as they can be disabled with a rpm macro for short circuiting purposes. opensp.spec:91: W: macro-in-comment %patch opensp.spec:92: W: macro-in-comment %patch opensp.spec:100: W: macro-in-comment %{sgml_dir} opensp.spec:119: W: macro-in-comment %{INSTALL_DIR} opensp.spec:119: W: macro-in-comment %{_includedir} opensp.spec:128: W: macro-in-comment %{_includedir} opensp.spec:155: W: macro-in-comment %{INSTALL_DIR} opensp.spec:156: W: macro-in-comment %{INSTALL_DATA} opensp.spec:230: W: macro-in-comment %doc opensp.spec:250: W: macro-in-comment %{_datadir} 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. opensp.spec:245: W: libdir-macro-in-noarch-package (main package) %{_libdir}/lib*.so.* opensp.spec:255: W: libdir-macro-in-noarch-package opensp-devel %{_libdir}/lib*.so opensp.spec:256: W: libdir-macro-in-noarch-package opensp-devel %exclude %{_libdir}/*a The %{_libdir} or %{_lib} macro was found in a noarch package in a section that gets included in binary packages. This is most likely an error because these macros are expanded on the build host and their values vary between architectures, probably resulting in a package that does not work properly on all architectures at runtime. Investigate whether the package is really architecture independent or if some other dir/macro should be instead. opensp.x86_64: W: binary-or-shlib-calls-gethostbyname /usr/lib64/libosp.so.5.0.0 The binary calls gethostbyname. Please port the code to use getaddrinfo. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files BinariesCheck 0.2 55.2 TOTAL 0.3 100.0 3 packages and 0 specfiles checked; 1 errors, 19 warnings, 54 filtered, 1 badness; has taken 0.3 s