| |
rpm id |
test |
status |
message |
 |
389-ds-base-3.1.4-alt3.1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
 |
certmonger-0.79.21-alt2.x86_64 |
file-in-usr-marked-as-conffile |
warn |
Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file. |
 |
certmonger-0.79.21-alt2.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/certmonger-0.79.21-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/certmonger.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
cockpit-ws-336.2-alt3.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/cockpit-ws-336.2-alt3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/cockpit-ws.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
cockpit-ws-336.2-alt3.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cockpit-ws-336.2-alt3.x86_64 |
systemd-check-socket-name |
experimental |
in cockpit-ws-336.2-alt3.x86_64: there is a socket cockpit-session.socket but no service cockpit-session.service. Ask ildar@ why it is not right.
in cockpit-ws-336.2-alt3.x86_64: there is a socket cockpit-wsinstance-https-factory.socket but no service cockpit-wsinstance-https-factory.service. Ask ildar@ why it is not right. |
 |
dogtag-pki-ca-11.8.0-alt1.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. |
|
dogtag-pki-java-11.8.0-alt1.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. |
|
dogtag-pki-kra-11.8.0-alt1.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. |
|
dogtag-pki-server-11.8.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
dogtag-pki-server-theme-11.8.0-alt1.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. |
|
dogtag-pki-tps-11.8.0-alt1.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. |
|
freeipa-client-epn-4.13.1-alt4.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
freeipa-common-4.13.1-alt4.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. |
|
freeipa-healthcheck-0.19-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
freeipa-server-4.13.1-alt4.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/freeipa-server-4.13.1-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ipa.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
freeipa-server-4.13.1-alt4.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
freeipa-server-4.13.1-alt4.x86_64 |
systemd-check-socket-name |
experimental |
in freeipa-server-4.13.1-alt4.x86_64: there is a socket ipa-otpd.socket but no service ipa-otpd.service. Ask ildar@ why it is not right. |
|
freeipa-server-common-4.13.1-alt4.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. |
|
freeipa-server-common-4.13.1-alt4.x86_64 |
file-in-usr-marked-as-conffile |
warn |
Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file. |
|
freeipa-server-dns-4.13.1-alt4.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
gssproxy-0.9.2-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
opendnssec-2.1.14-alt2.x86_64 |
file-in-usr-marked-as-conffile |
warn |
Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file. |
|
opendnssec-2.1.14-alt2.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/opendnssec-2.1.14-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/opendnssec.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
python3-module-proxy-py-2.4.10-alt1.2.noarch |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/proxy conflicts with the package libproxy-tools-0.5.12-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. |
|
python3-module-pyproject-fmt-2.21.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/pyproject-fmt conflicts with the package python3-module-pyproject-parser-0.14.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
python3-module-system-seed-wheels-0.0.2-alt1.x86_64 |
missing-url |
info |
Missing Url: in a package. |
|
python3-module-system-seed-wheels-wheels-0.0.2-alt1.x86_64 |
missing-url |
info |
Missing Url: in a package. |
|
uid_wrapper-1.3.2-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libuid_wrapper.so but just /usr/lib64/libuid_wrapper.so.0.2.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libuid_wrapper.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libuid_wrapper.so to \%files of uid_wrapper-1.3.2-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. |