============================ 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: 16 linux-glibc-devel.spec:170: W: shared-dir-glob-in-files %{_includedir}/* The %files section contains "%{_bindir}/*", "%{_datadir}/*", "%{_docdir}/*", "%{_includedir}/*" or "%{_mandir}/*". These can lead to packagers not noticing when upstream adds new and possibly conflicting files in these directories. Therefore, files in these directories should be explicitely listed like "%{_bindir}/foobar" or "%{_includedir}/foobar.h". linux-glibc-devel.i586: E: no-binary The package should be of the noarch architecture because it doesn't contain any binaries. linux-glibc-devel.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. linux-glibc-devel.spec:106: W: macro-in-comment %{_includedir} 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. cross-aarch64-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/aarch64-suse-linux cross-arm-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/arm-suse-linux-gnueabi cross-hppa-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/hppa-suse-linux cross-i386-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/i586-suse-linux cross-loongarch64-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/loongarch64-suse-linux cross-m68k-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/m68k-suse-linux cross-mips-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/mips-suse-linux cross-ppc64-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/powerpc64-suse-linux cross-ppc64le-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/powerpc64le-suse-linux cross-riscv64-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/riscv64-suse-linux cross-s390x-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/s390x-suse-linux cross-sparc-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/sparc-suse-linux cross-sparc64-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/sparc64-suse-linux cross-x86_64-linux-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/x86_64-suse-linux File violates FHS 2.3. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files ExtractRpm 6.8 32.0 FilesCheck 4.3 20.3 BuildRootAndDateCheck 2.9 13.5 FilelistCheck 2.7 12.9 BashismsCheck 1.7 8.0 FileDigestCheck 0.7 3.2 SUIDPermissionsCheck 0.4 1.7 SpecCheck 0.3 1.3 SignatureCheck 0.2 1.1 PythonCheck 0.2 1.1 TOTAL 21.2 100.0 16 packages and 0 specfiles checked; 15 errors, 3 warnings, 510 filtered, 15 badness; has taken 22.2 s