============================ rpmlint session starts ============================ rpmlint: 2.6.1 configuration: /opt/testing/lib/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 apache2-devel.armv7hl: W: potential-bashisms /usr/share/apache2/build/instdso.sh checkbashisms reported potential bashisms in a /bin/sh shell script, you might want to manually check this script for bashisms. apache2-devel.armv7hl: E: no-binary The package should be of the noarch architecture because it doesn't contain any binaries. apache2.spec:738: W: macro-in-comment %{_libdir} apache2.spec:785: W: macro-in-comment %{_libdir} 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. apache2.spec:829: W: libdir-macro-in-noarch-package (main package) %dir %{_libdir}/apache2-%{mpm} apache2.spec:830: W: libdir-macro-in-noarch-package (main package) %dir %{_libdir}/apache2 apache2.spec:831: W: libdir-macro-in-noarch-package (main package) %{_libdir}/apache2/*.so 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. apache2-devel.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 SpecCheck 0.2 33.3 BashismsCheck 0.2 29.7 TOTAL 0.6 100.0 2 packages and 0 specfiles checked; 2 errors, 6 warnings, 19 filtered, 2 badness; has taken 0.6 s