============================ rpmlint session starts ============================
rpmlint: 2.6.1
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
    /etc/xdg/rpmlint/scoring-strict.override.toml
checks: 41, packages: 2

dita.noarch: W: package-with-huge-docs 95%
More than half the size of your package is documentation. Consider splitting
it into a -doc subpackage.

dita.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.

dita.spec:72: W: macro-in-comment %patch
dita.spec:102: W: macro-in-comment %{INSTALL_DIR}
dita.spec:102: W: macro-in-comment %{sgml_config_dir}
dita.spec:103: W: macro-in-comment %{INSTALL_DIR}
dita.spec:103: W: macro-in-comment %{xml_config_dir}
dita.spec:151: W: macro-in-comment %config
dita.spec:151: W: macro-in-comment %{sgml_config_dir}
dita.spec:152: W: macro-in-comment %doc
dita.spec:153: W: macro-in-comment %{sgml_dir}
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                                   0.1              38.1               
    TOTAL                                        0.4             100.0               

 2 packages and 0 specfiles checked; 0 errors, 11 warnings, 4 filtered, 0 badness; has taken 0.4 s