mumps-openmpi4-devel-static-compat.armv7hl: W: devel-dependency mumps-devel-static Your package has a dependency on a devel package but it's not a devel package itself. libmumps5-openmpi4.armv7hl: W: explicit-lib-dependency libblacs2-openmpi4 You must let rpm find the library dependencies by itself. Do not put unneeded explicit Requires: tags. mumps-openmpi4.src: W: invalid-spec-name The spec file name (without the .spec suffix) must match the package name ("Name:" tag). Either rename your package or the specfile. mumps-openmpi4-devel.armv7hl: W: no-dependency-on mumps-openmpi4*/mumps-openmpi4-libs/libmumps-openmpi4* libmumps5-openmpi4-compat.armv7hl: W: no-version-in-last-changelog libmumps5-openmpi4.armv7hl: W: no-version-in-last-changelog mumps-openmpi4-devel-static-compat.armv7hl: W: no-version-in-last-changelog mumps-openmpi4-devel-static.armv7hl: W: no-version-in-last-changelog mumps-openmpi4-devel.armv7hl: W: no-version-in-last-changelog mumps-openmpi4-examples.armv7hl: W: no-version-in-last-changelog mumps-openmpi4.src: W: no-version-in-last-changelog The latest changelog entry doesn't contain a version. Please insert the version that is coherent with the version of the package and rebuild it. libmumps5-openmpi4.armv7hl: W: shared-lib-calls-exit /usr/lib/mpi/gcc/openmpi4/lib/libmumps_common.so.5.3.5 exit@GLIBC_2.4 libmumps5-openmpi4.armv7hl: W: shared-lib-calls-exit /usr/lib/mpi/gcc/openmpi4/lib/libpord.so.5.3.5 exit@GLIBC_2.4 This library package calls exit() or _exit(), probably in a non-fork() context. Doing so from a library is strongly discouraged - when a library function calls exit(), it prevents the calling program from handling the error, reporting it to the user, closing files properly, and cleaning up any state that the program has. It is preferred for the library to return an actual error code and let the calling program decide how to handle the situation. libmumps5-openmpi4-compat.armv7hl: W: shlib-policy-missing-lib libmumps5-openmpi4.armv7hl: W: shlib-policy-missing-lib Your package starts with 'lib' as part of its name, but does not provide any libraries. It must not be called a lib-package then. Give it a more sensible name. 7 packages and 0 specfiles checked; 0 errors, 15 warnings.