| |
rpm id |
test |
status |
message |
 |
alterator-openvpn-sh-functions-1.0-alt1.noarch |
checkbashisms |
experimental |
checkbashisms utility found possible bashisms in: /usr/bin/alterator-openvpn-sh-functions |
 |
itk-examples-5.0.0-alt3.x86_64 |
arch-dep-package-has-big-usr-share |
info |
The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
 |
python3-module-libarchive-c-2.9-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package python3-module-libarchive-4.0.1-alt1.x86_64, for example, /usr/lib64/python3/site-packages/libarchive/__init__.py (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
tcb-hash-prefix-control-1.1-alt1.noarch |
missing-url |
info |
Missing Url: in a package. |
|
vtk8.2-data-8.2.0-alt6.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |
|
vtk8.2-doc-8.2.0-alt6.x86_64 |
arch-dep-package-consists-of-usr-share |
info |
The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. |