============================ 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
rpmlintrc:
    /home/abuild/rpmbuild/SOURCES/suse-module-tools.rpmlintrc
checks: 41, packages: 3

suse-module-tools.x86_64: E: systemd-service-without-service_del_postun boot-sysctl.service
suse-module-tools.x86_64: E: systemd-service-without-service_del_postun kernel-sysctl.service
The package contains a systemd service but doesn't contain a %postun with a
call to service_del_postun.

suse-module-tools.x86_64: W: potential-bashisms /usr/lib/module-init-tools/unblacklist
checkbashisms reported potential bashisms in a /bin/sh shell script, you might
want to manually check this script for bashisms.

suse-module-tools.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.

suse-module-tools.spec:173: W: macro-in-comment %{name}
suse-module-tools.spec:181: W: macro-in-comment %posttrans
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.6              84.5               
    TOTAL                                        0.8             100.0               

 3 packages and 0 specfiles checked; 2 errors, 4 warnings, 39 filtered, 2 badness; has taken 0.8 s