============================ 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: 37

boost-devel.x86_64: E: no-binary
boost-jam.x86_64: E: no-binary
libboost_atomic-devel.x86_64: E: no-binary
libboost_chrono-devel.x86_64: E: no-binary
libboost_container-devel.x86_64: E: no-binary
libboost_context-devel.x86_64: E: no-binary
libboost_contract-devel.x86_64: E: no-binary
libboost_coroutine-devel.x86_64: E: no-binary
libboost_date_time-devel.x86_64: E: no-binary
libboost_fiber-devel.x86_64: E: no-binary
libboost_filesystem-devel.x86_64: E: no-binary
libboost_graph-devel.x86_64: E: no-binary
libboost_graph_parallel-devel.x86_64: E: no-binary
libboost_headers-devel.x86_64: E: no-binary
libboost_iostreams-devel.x86_64: E: no-binary
libboost_locale-devel.x86_64: E: no-binary
libboost_log-devel.x86_64: E: no-binary
libboost_math-devel.x86_64: E: no-binary
libboost_mpi-devel.x86_64: E: no-binary
libboost_mpi_python3-devel.x86_64: E: no-binary
libboost_nowide-devel.x86_64: E: no-binary
libboost_numpy3-devel.x86_64: E: no-binary
libboost_process-devel.x86_64: E: no-binary
libboost_program_options-devel.x86_64: E: no-binary
libboost_python3-devel.x86_64: E: no-binary
libboost_random-devel.x86_64: E: no-binary
libboost_regex-devel.x86_64: E: no-binary
libboost_serialization-devel.x86_64: E: no-binary
libboost_stacktrace-devel.x86_64: E: no-binary
libboost_test-devel.x86_64: E: no-binary
libboost_thread-devel.x86_64: E: no-binary
libboost_timer-devel.x86_64: E: no-binary
libboost_type_erasure-devel.x86_64: E: no-binary
libboost_url-devel.x86_64: E: no-binary
libboost_wave-devel.x86_64: E: no-binary
python3-boost_parallel_mpi.x86_64: E: no-binary
The package should be of the noarch architecture because it doesn't contain
any binaries.

boost-defaults.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                                   0.3              47.9               
    SignatureCheck                               0.2              38.3               
    TOTAL                                        0.6             100.0               

 37 packages and 0 specfiles checked; 36 errors, 1 warnings, 74 filtered, 36 badness; has taken 0.6 s