============================ rpmlint session starts ============================
rpmlint: 2.8.0
configuration:
    /opt/testing/lib64/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: 42, packages: 4

corosync.aarch64: W: tmpfile-not-in-filelist /var/log/cluster
corosync.aarch64: W: tmpfile-not-in-filelist /var/lib/corosync
Please add the specified file to your %files section as %ghost so users can
easily query who created the file, it gets uninstalled on package removal and
finally other rpmlint checks see it.

corosync.aarch64: W: obsolete-not-provided libcfg6
corosync.aarch64: W: obsolete-not-provided libcmap4
corosync.aarch64: W: obsolete-not-provided libcorosync_common4
corosync.aarch64: W: obsolete-not-provided libcpg4
corosync.aarch64: W: obsolete-not-provided libquorum5
corosync.aarch64: W: obsolete-not-provided libsam4
corosync.aarch64: W: obsolete-not-provided libtotem_pg5
corosync.aarch64: W: obsolete-not-provided libvotequorum8
If a package is obsoleted by a compatible replacement, the obsoleted package
should also be provided in order to not cause unnecessary dependency breakage.
If the obsoleting package is not a compatible replacement for the old one,
leave out the Provides.

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

corosync.aarch64: W: name-repeated-in-summary Corosync
corosync.src: W: name-repeated-in-summary Corosync
The name of the package is repeated in its summary. Make the summary brief and
to the point without including redundant information in it.

corosync.aarch64: W: install-file-in-docs /usr/share/doc/corosync/INSTALL
A file whose name suggests that it contains installation instructions is
included in the package. Such instructions are often not relevant for already
installed packages.

corosync.aarch64: W: files-duplicate /usr/share/doc/packages/corosync/LICENSE /usr/share/doc/corosync/LICENSE
Your package contains duplicated files that are not hard- or symlinks. You
should use the %fdupes macro to link the files to one.

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    BinariesCheck                                0.4              30.1               
    ExtractRpm                                   0.2              18.5               
    SUIDPermissionsCheck                         0.2              15.7               
    BashismsCheck                                0.1              12.5               
    TOTAL                                        1.2             100.0               

 4 packages and 0 specfiles checked; 0 errors, 15 warnings, 25 filtered, 0 badness; has taken 1.2 s