============================ rpmlint session starts ============================
rpmlint: 2.6.1
configuration:
    /opt/testing/lib/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: 4

perl-Text-ChaSen.armv6hl: W: self-obsoletion chasen-perl obsoletes chasen-perl
The package obsoletes itself. This is known to cause errors in various tools
and should thus be avoided, usually by using appropriately versioned Obsoletes
and/or Provides and avoiding unversioned ones.

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

chasen-devel.armv6hl: E: no-binary
The package should be of the noarch architecture because it doesn't contain
any binaries.

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

chasen.spec:35: W: macro-in-comment %description
chasen.spec:94: W: macro-in-comment %description
chasen.spec:110: W: macro-in-comment %description
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
    BashismsCheck                                0.4              54.4               
    BinariesCheck                                0.1              22.3               
    TOTAL                                        0.7             100.0               

 4 packages and 0 specfiles checked; 1 errors, 6 warnings, 27 filtered, 1 badness; has taken 0.7 s