============================ rpmlint session starts ============================ rpmlint: 2.8.0 configuration: /opt/testing/lib64/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 rpmlintrc: /home/abuild/rpmbuild/SOURCES/glibc.rpmlintrc checks: 41, packages: 2 glibc-cross-ppc64le-src.src: E: unused-rpmlintrc-filter "glibc-profile.* devel-file-in-non-devel-package.*/usr/lib.*/lib.*_p\.a" glibc-cross-ppc64le-src.src: E: unused-rpmlintrc-filter "glibc\..* non-devel-file-in-devel-package" glibc-cross-ppc64le-src.src: E: unused-rpmlintrc-filter "binary-or-shlib-calls-gethostbyname /usr/bin/getent" glibc-cross-ppc64le-src.src: E: unused-rpmlintrc-filter "unstripped-binary-or-object" glibc-cross-ppc64le-src.src: E: unused-rpmlintrc-filter "shared-library-without-dependency-information /usr/lib.*/ld.*\.so" glibc.spec:1443: 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". glibc.spec:1100: W: macro-in-comment %{_libexecdir} 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. glibc-cross-ppc64le-src.src: E: invalid-spec-name The spec file name (without the .spec suffix) must match the package name ('Name:' tag). cross-ppc64le-glibc-devel.noarch: W: files-duplicate /usr/powerpc64le-suse-linux/sys-root/usr/lib64/libutil.a /usr/powerpc64le-suse-linux/sys-root/usr/lib64/libanl.a:/usr/powerpc64le-suse-linux/sys-root/usr/lib64/libdl.a:/usr/powerpc64le-suse-linux/sys-root/usr/lib64/libpthread.a:/usr/powerpc64le-suse-linux/sys-root/usr/lib64/librt.a Your package contains duplicated files that are not hard- or symlinks. You should use the %fdupes macro to link the files to one. cross-ppc64le-glibc-devel.noarch: E: filelist-forbidden-fhs23 /usr/powerpc64le-suse-linux File violates FHS 2.3. glibc.spec:278: E: buildarch-instead-of-exclusivearch-tag i686 Use ExclusiveArch instead of BuildArch (or BuildArchitectures) to restrict build on some specific architectures. Only use BuildArch with noarch Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files ExtractRpm 6.1 91.4 SignatureCheck 0.2 2.5 SpecCheck 0.2 2.3 TOTAL 6.7 100.0 2 packages and 0 specfiles checked; 8 errors, 3 warnings, 134 filtered, 8 badness; has taken 6.8 s