============================ 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: 2 ffado.spec:68: W: suse-update-desktop-file-deprecated %suse_update_desktop_file is deprecated The usage of %suse_update_desktop_file is deprecated and changes should be migrated to the upstream. Please check the build log for details. ffado.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. ffado.spec:291: W: libdir-macro-in-noarch-package ffado-devel %{_libdir}/%{tname}*.so ffado.spec:292: W: libdir-macro-in-noarch-package ffado-devel %{_libdir}/pkgconfig/%{tname}.pc ffado.spec:297: W: libdir-macro-in-noarch-package libffado%{sover} %{_libdir}/%{tname}.so.%{sover}* 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. ffado-mixer.src: E: invalid-spec-name The spec file name (without the .spec suffix) must match the package name ('Name:' tag). Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files ExtractRpm 0.2 60.3 TOTAL 0.3 100.0 2 packages and 0 specfiles checked; 1 errors, 5 warnings, 7 filtered, 1 badness; has taken 0.3 s