============================ 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 os-prober.spec:147: 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". os-prober.armv6hl: W: potential-bashisms /usr/bin/os-prober os-prober.armv6hl: W: potential-bashisms /usr/lib/os-probes/common/50mounted-tests os-prober.armv6hl: W: potential-bashisms /usr/lib/os-probes/50mounted-tests os-prober.armv6hl: W: potential-bashisms /usr/lib/os-probes/mounted/x86/05efi os-prober.armv6hl: W: potential-bashisms /usr/lib/os-probes/mounted/arm64/05efi os-prober.armv6hl: W: potential-bashisms /usr/lib/linux-boot-probes/mounted/powerpc/40yaboot os-prober.armv6hl: W: potential-bashisms /usr/lib/linux-boot-probes/50mounted-tests os-prober.armv6hl: W: potential-bashisms /usr/lib/linux-boot-probes/common/50mounted-tests checkbashisms reported potential bashisms in a /bin/sh shell script, you might want to manually check this script for bashisms. os-prober.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. os-prober.armv6hl: W: files-duplicate /usr/lib/linux-boot-probes/common/50mounted-tests /usr/lib/linux-boot-probes/50mounted-tests os-prober.armv6hl: W: files-duplicate /usr/lib/linux-boot-probes/mounted/common/40grub2 /usr/lib/linux-boot-probes/mounted/40grub2 os-prober.armv6hl: W: files-duplicate /usr/lib/linux-boot-probes/mounted/common/90fallback /usr/lib/linux-boot-probes/mounted/90fallback os-prober.armv6hl: W: files-duplicate /usr/lib/os-probes/common/50mounted-tests /usr/lib/os-probes/50mounted-tests os-prober.armv6hl: W: files-duplicate /usr/lib/os-probes/init/common/10filesystems /usr/lib/os-probes/init/10filesystems os-prober.armv6hl: W: files-duplicate /usr/lib/os-probes/mounted/common/40lsb /usr/lib/os-probes/mounted/40lsb os-prober.armv6hl: W: files-duplicate /usr/lib/os-probes/mounted/common/90linux-distro /usr/lib/os-probes/mounted/90linux-distro os-prober.armv6hl: W: files-duplicate /usr/lib/os-probes/mounted/x86/efi/20microsoft /usr/lib/os-probes/mounted/arm64/efi/20microsoft 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 BashismsCheck 1.7 92.8 TOTAL 1.9 100.0 2 packages and 0 specfiles checked; 0 errors, 18 warnings, 13 filtered, 0 badness; has taken 1.9 s