============================ rpmlint session starts ============================ rpmlint: 2.5.0 configuration: /opt/testing/lib64/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 checks: 41, packages: 10 sqlite3-doc.noarch: E: zero-length /usr/share/doc/packages/sqlite3-doc/images/chart.wiki libsqlite3-0.x86_64: W: unstripped-binary-or-object /usr/lib64/libsqlite3.so.0.8.6 sqlite3.x86_64: W: unstripped-binary-or-object /usr/bin/sqlite3 sqlite3-tcl.x86_64: W: unstripped-binary-or-object /usr/lib64/tcl/sqlite3.46.0/libtclsqlite3.so libsqlite3-0.x86_64_v3: W: unstripped-binary-or-object /usr/lib64/libsqlite3.so.0.8.6 sqlite3.x86_64_v3: W: unstripped-binary-or-object /usr/bin/sqlite3 sqlite3-tcl.x86_64_v3: W: unstripped-binary-or-object /usr/lib64/tcl/sqlite3.46.0/libtclsqlite3.so This executable should be stripped from debugging symbols, in order to take less space and be loaded faster. This is usually done automatically at buildtime by rpm. sqlite3.spec:131: W: macro-in-comment %tarversion sqlite3.spec:131: W: macro-in-comment %docversion sqlite3.spec:188: W: macro-in-comment %{buildroot} sqlite3.spec:188: W: macro-in-comment %{_mandir} sqlite3.spec:192: W: macro-in-comment %{buildroot} sqlite3.spec:192: 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. Check time report (>1% & >0.1s): Check Duration (in s) Fraction (in %) Checked files ZipCheck 0.4 31.5 ExtractRpm 0.3 23.8 SignatureCheck 0.2 12.2 FilesCheck 0.1 8.8 TOTAL 1.3 100.0 10 packages and 0 specfiles checked; 1 errors, 12 warnings, 28 filtered, 1 badness; has taken 1.3 s