============================ rpmlint session starts ============================
rpmlint: 2.8.0
configuration:
    /opt/testing/lib/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
checks: 41, packages: 2

systemtap-docs.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.

systemtap-docs.noarch: W: files-duplicate /usr/share/doc/packages/systemtap/examples/profiling/pf4.tcl /usr/share/doc/packages/systemtap/examples/general/py2example.tcl:/usr/share/doc/packages/systemtap/examples/general/py3example.tcl:/usr/share/doc/packages/systemtap/examples/memory/last_100_frees.tcl:/usr/share/doc/packages/systemtap/examples/process/auditbt.tcl:/usr/share/doc/packages/systemtap/examples/process/mutex-contention.tcl:(and 1 more)
systemtap-docs.noarch: W: files-duplicate /usr/share/doc/packages/systemtap/examples/profiling/latencytap.tcl /usr/share/doc/packages/systemtap/examples/interrupt/scf.tcl:/usr/share/doc/packages/systemtap/examples/io/io_submit.tcl:/usr/share/doc/packages/systemtap/examples/io/mbrwatch.tcl:/usr/share/doc/packages/systemtap/examples/process/chng_cpu.tcl:/usr/share/doc/packages/systemtap/examples/process/sleepingBeauties.tcl
systemtap-docs.noarch: W: files-duplicate /usr/share/doc/packages/systemtap/examples/memory/hw_watch_sym.tcl /usr/share/doc/packages/systemtap/examples/memory/hw_watch_addr.tcl
Your package contains duplicated files that are not hard- or symlinks. You
should use the %fdupes macro to link the files to one.

systemtap-docs.noarch: W: bin-sh-syntax-error /usr/share/doc/packages/systemtap/examples/process/strace.stp
systemtap-docs.noarch: W: bin-sh-syntax-error /usr/share/doc/packages/systemtap/examples/process/noptrace.stp
systemtap-docs.noarch: W: bin-sh-syntax-error /usr/share/doc/packages/systemtap/examples/io/eatmydata.stp
systemtap-docs.noarch: W: bin-sh-syntax-error /usr/share/doc/packages/systemtap/examples/process/psig.stp
systemtap-docs.noarch: W: bin-sh-syntax-error /usr/share/doc/packages/systemtap/examples/process/threadstacks.stp
A /bin/sh shell script contains a POSIX shell syntax error. This might
indicate a potential bash-specific feature being used, try dash -n <file> for
more detailed error message.

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    ExtractRpm                                   1.9              68.5               
    FilesCheck                                   0.3              10.3               
    BashismsCheck                                0.2               8.0               
    BuildRootAndDateCheck                        0.1               3.6               
    TOTAL                                        2.8             100.0               

 2 packages and 0 specfiles checked; 0 errors, 9 warnings, 3 filtered, 0 badness; has taken 2.9 s