python3-lammps.x86_64: W: conflicts-with-provides python-lammps
The same symbolic name is provided and conflicted. This package might be
uninstallable, if versioning matches

lammps-data.noarch: W: files-duplicate /usr/share/lammps/potentials/Ni_Zuo_JPCA2020.snapparam /usr/share/lammps/potentials/Cu_Zuo_JPCA2020.snapparam
lammps.src:186: W: macro-in-comment %ix86
There is a unescaped macro after a shell style comment in the specfile. Macros
are expanded everywhere, so check if it can cause a problem in this case and
escape the macro with another leading % if appropriate.

lammps-data.noarch: W: no-version-in-last-changelog
lammps-devel.x86_64: W: no-version-in-last-changelog
lammps.src: W: no-version-in-last-changelog
lammps.x86_64: W: no-version-in-last-changelog
liblammps0.x86_64: W: no-version-in-last-changelog
python3-lammps.x86_64: 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.

liblammps0.x86_64: W: shared-lib-calls-exit /usr/lib64/liblammps.so.0 exit@GLIBC_2.2.5
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.

6 packages and 0 specfiles checked; 0 errors, 10 warnings.