Repocop reports by srpm

  rpm id test status message
arpack-96-alt11.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/lib/libarpack_LINUX.a
/usr/lib/libarpack_LINUX_Carley.a
/usr/lib/libparpack_BLACS-LINUX.a
/usr/lib/libparpack_BLACS-LINUX_Carley.a
/usr/lib/libparpack_MPI-LINUX.a
/usr/lib/libparpack_MPI-LINUX_Carley.a
/usr/lib/parpack_BLACS-LINUX.a
/usr/lib/parpack_BLACS-LINUX_Carley.a
/usr/lib/parpack_MPI-LINUX.a
/usr/lib/parpack_MPI-LINUX_Carley.a
arpack-96-alt11.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/lib64/libarpack_LINUX.a
/usr/lib64/libarpack_LINUX_Carley.a
/usr/lib64/libparpack_BLACS-LINUX.a
/usr/lib64/libparpack_BLACS-LINUX_Carley.a
/usr/lib64/libparpack_MPI-LINUX.a
/usr/lib64/libparpack_MPI-LINUX_Carley.a
/usr/lib64/parpack_BLACS-LINUX.a
/usr/lib64/parpack_BLACS-LINUX_Carley.a
/usr/lib64/parpack_MPI-LINUX.a
/usr/lib64/parpack_MPI-LINUX_Carley.a
libarpack-devel-96-alt11.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libarpack.so is different from the same symlink in the package libarpack-ng-devel-3.6.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.

generated by repocop at Thu Nov 15 04:19:13 2018