============================ rpmlint session starts ============================ rpmlint: 2.4.0 configuration: /opt/testing/lib/python3.10/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 QMPlay2-devel.armv6hl: E: no-binary The package should be of the noarch architecture because it doesn't contain any binaries. QMPlay2.spec:102: W: macro-in-comment %setup QMPlay2.spec:102: W: macro-in-comment %{name} QMPlay2.spec:102: W: macro-in-comment %{version} QMPlay2.spec:103: W: macro-in-comment %patch1 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 BinariesCheck 2.9 70.3 21 rpm2cpio 0.5 12.0 SignatureCheck 0.2 5.3 SpecCheck 0.2 4.5 TOTAL 4.1 100.0 120 3 packages and 0 specfiles checked; 1 errors, 4 warnings, 15 filtered, 1 badness; has taken 4.1 s