Rivet-plugins.ppc64le: W: devel-dependency Rivet-devel Your package has a dependency on a devel package but it's not a devel package itself. Rivet-devel.ppc64le: W: no-version-in-last-changelog Rivet-plugins.ppc64le: W: no-version-in-last-changelog Rivet.src: W: no-version-in-last-changelog libRivet-3_1_6.ppc64le: W: no-version-in-last-changelog python3-Rivet.ppc64le: 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. python3-Rivet.ppc64le: W: python-bytecode-inconsistent-mtime /usr/lib64/python3.6/site-packages/rivet/__pycache__/spiresbib.cpython-36.pyc 2021-05-26T13:46:18 /usr/lib64/python3.6/site-packages/rivet/spiresbib.py 2023-05-22T10:52:34 The timestamp embedded in this python bytecode file isn't equal to the mtime of the original source file, which will force the interpreter to recompile the .py source every time, ignoring the saved bytecode. Rivet-devel.ppc64le: W: script-without-shebang /usr/share/Rivet/ATLAS_2019_I1772071.plot This text file has executable bits set or is located in a path dedicated for executables, but lacks a shebang and cannot thus be executed. If the file is meant to be an executable script, add the shebang, otherwise remove the executable bits or move the file elsewhere. libRivet-3_1_6.ppc64le: W: shared-lib-calls-exit /usr/lib64/libRivet-3.1.6.so exit@GLIBC_2.17 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. Rivet-devel.ppc64le: W: zero-length /usr/share/doc/packages/Rivet-devel/AUTHORS Rivet-devel.ppc64le: W: zero-length /usr/share/doc/packages/Rivet-devel/NEWS 5 packages and 0 specfiles checked; 0 errors, 11 warnings.