============================ 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: 41, packages: 4

binaryen.spec:104: E: rpm-buildroot-usage %postun rm %{buildroot}%{_prefix}/lib/debug/usr/bin/wasm-merge.debug
binaryen.spec:105: E: rpm-buildroot-usage %postun rm %{buildroot}%{_prefix}/lib/debug/usr/bin/wasm-fuzz-lattices.debug
$RPM_BUILD_ROOT or %{buildroot} must not be touched during %build or %prep
stage, as it will break short circuit builds and will not persist to %install
stage in a normal build, leading to unexpected package build behavior.

libbinaryen.aarch64: E: non-empty-%postun /sbin/ldconfig
Scriptlets for the interpreter mentioned in the message should be empty.
One common case where they are unintentionally not is when the specfile
contains comments after the scriptlet and before the next section. Review
and clean up the scriptlet contents if appropriate.

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

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

Check time report (>1% & >0.1s):
    Check                            Duration (in s)   Fraction (in %)  Checked files
    ExtractRpm                                   1.5              48.4               
    BinariesCheck                                1.0              31.0               
    SharedLibraryPolicyCheck                     0.5              15.8               
    TOTAL                                        3.1             100.0               

 4 packages and 0 specfiles checked; 4 errors, 1 warnings, 26 filtered, 4 badness; has taken 3.2 s