/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
| rpm id | test | status | message | |
|---|---|---|---|---|
|
freeipa-client-epn-4.11.2-alt3.x86_64 | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
freeipa-common-4.11.2-alt3.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-server-4.11.2-alt3.x86_64 | sisyphus_check | fail | sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/freeipa-server-4.11.2-alt3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ipa.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
freeipa-server-4.11.2-alt3.x86_64 | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
freeipa-server-4.11.2-alt3.x86_64 | systemd-check-socket-name | experimental | in freeipa-server-4.11.2-alt3.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.11.2-alt3.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.11.2-alt3.x86_64 | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |