============================ 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
rpmlintrc:
    /home/abuild/rpmbuild/SOURCES/fftw3-rpmlintrc
checks: 42, packages: 9

fftw3.src: E: unused-rpmlintrc-filter "libfftw3\S+-gnu-\S+.x86_64: E: shlib-policy-name-error SONAME.*"
fftw3.src: E: unused-rpmlintrc-filter "libfftw3.* devel-file-in-non-devel-package"
fftw3.src: E: unused-rpmlintrc-filter "libfftw3.* hidden-file-or-dir"
fftw3.src: E: unused-rpmlintrc-filter "shlib-fixed-dependency"
fftw3.src: E: unused-rpmlintrc-filter "libfftw3.* shlib-policy-nonversioned-dir /usr/lib/hpc"
fftw3.src: E: unused-rpmlintrc-filter "libfftw3.* shlib-policy-nonversioned-dir /usr/share/lmod"
fftw3.spec:324: W: shared-dir-glob-in-files %{_bindir}/*
The %files section contains "%{_bindir}/*", "%{_datadir}/*", "%{_docdir}/*",
"%{_includedir}/*" or "%{_mandir}/*".  These can lead to packagers not
noticing when upstream adds new and possibly conflicting files in these
directories. Therefore, files in these directories should be explicitely
listed like "%{_bindir}/foobar" or "%{_includedir}/foobar.h".

fftw3.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.1              42.2               
    BashismsCheck                                0.6              22.4               
    BinariesCheck                                0.4              15.1               
    SharedLibraryPolicyCheck                     0.2               7.7               
    SignatureCheck                               0.1               4.4               
    TOTAL                                        2.7             100.0               

 9 packages and 0 specfiles checked; 6 errors, 2 warnings, 42 filtered, 6 badness; has taken 2.7 s