============================ 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/mozilla-nss-rpmlintrc checks: 41, packages: 8 mozilla-nss.src: E: unused-rpmlintrc-filter "shlib-policy-name-error" mozilla-nss.src: E: unused-rpmlintrc-filter "shlib-policy-missing-lib" mozilla-nss.src: E: unused-rpmlintrc-filter "shlib-policy-missing-suffix" mozilla-nss.spec:518: W: shared-dir-glob-in-files %{_bindir}/* 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". mozilla-nss-devel.x86_64: E: rpath-in-buildconfig /usr/bin/nss-config lines 129 mozilla-nss-devel.x86_64: E: rpath-in-buildconfig /usr/bin/nss-util-config lines 112 This build configuration file contains rpaths which will be introduced into dependent packages. mozilla-nss.spec:252: W: macro-in-comment %{SOURCE2} mozilla-nss.spec:379: W: macro-in-comment %{buildroot} mozilla-nss.spec:379: W: macro-in-comment %{_libdir} mozilla-nss.spec:456: W: macro-in-comment %{buildroot} mozilla-nss.spec:456: W: macro-in-comment %{_lib} mozilla-nss.spec:456: W: macro-in-comment %{buildroot} mozilla-nss.spec:456: W: macro-in-comment %{_libdir} mozilla-nss.spec:456: W: macro-in-comment %{buildroot} mozilla-nss.spec:456: W: macro-in-comment %{_bindir} mozilla-nss.spec:456: W: macro-in-comment %{buildroot} mozilla-nss.spec:456: W: macro-in-comment %{nssdbdir} mozilla-nss.spec:457: W: macro-in-comment %{buildroot} mozilla-nss.spec:457: W: macro-in-comment %{_lib} mozilla-nss.spec:457: W: macro-in-comment %{buildroot} mozilla-nss.spec:457: W: macro-in-comment %{_libdir} mozilla-nss.spec:457: W: macro-in-comment %{buildroot} mozilla-nss.spec:457: W: macro-in-comment %{_bindir} mozilla-nss.spec:457: W: macro-in-comment %{buildroot} mozilla-nss.spec:457: W: macro-in-comment %{nssdbdir} mozilla-nss.spec:458: W: macro-in-comment %{buildroot} mozilla-nss.spec:458: W: macro-in-comment %{nssdbdir} mozilla-nss.spec:459: W: macro-in-comment %{buildroot} mozilla-nss.spec:462: W: macro-in-comment %{buildroot} mozilla-nss.spec:462: W: macro-in-comment %{nssdbdir} mozilla-nss.spec:462: W: macro-in-comment %{buildroot} mozilla-nss.spec:462: W: macro-in-comment %{nssdbdir} mozilla-nss.spec:463: W: macro-in-comment %{buildroot} mozilla-nss.spec:463: W: macro-in-comment %{nssdbdir} 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 ExtractRpm 2.5 64.8 BinariesCheck 0.4 11.1 BashismsCheck 0.4 10.9 SignatureCheck 0.3 7.7 TOTAL 3.8 100.0 8 packages and 0 specfiles checked; 5 errors, 29 warnings, 33 filtered, 5 badness; has taken 3.8 s