/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
.
ives.
| rpm id | test | status | message | |
|---|---|---|---|---|
|
codetest_sl-1.6-alt1.x86_64 | rpm-filesystem-conflict-file-file | warn | Files /usr/bin/sl /usr/share/man/man1/sl.1.xz conflict with the package sl-5.02-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. |
|
criu-4.0-alt1.x86_64 | sisyphus_check | fail | sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/criu-4.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/criu.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
drbd-reactor-1.7.0-alt1.x86_64 | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
drbd-utils-9.29.0-alt1.x86_64 | sisyphus_check | fail | sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/drbd-utils-9.29.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/65-drbd.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
fence-agents-common-4.16.0-alt1.noarch | sisyphus_check | fail | sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/fence-agents-common-4.16.0-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/fence-agents.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
ifupdown2-3.2.0.11-alt2.noarch | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
ledmon-1.1.0-alt1.x86_64 | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
ledmon-1.1.0-alt1.x86_64 | uncompressed-manpages | info | Package contains uncompressed manual pages. |
|
lizardfs-client-3.13.0-alt0.rc4.1.1.x86_64 | rpm-filesystem-conflict-symlink-file | warn | symlink /usr/share/man/man7/moosefs.7.xz is a file in the package moosefs-master-4.56.6-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. |
|
pve-backup-restore-image-0.5-alt1.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. |
|
pve-backup-restore-image-0.5-alt1.x86_64 | missing-url | info | Missing Url: in a package. |
|
pve-enable-0.1-alt1.x86_64 | missing-url | info | Missing Url: in a package. |
|
python3-module-prometheus-pve-exporter-3.4.7-alt1.noarch | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
ravada-2.3.1-alt2.noarch | pseudouser-added-as-real-user | fail | package added a pseudouser in its %pre/%post script as a real user. You should use -r option of useradd command to create a system account. |
|
ravada-2.3.1-alt2.noarch | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
sbd-1.5.2-alt1.x86_64 | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
udev-rules-hotplug-cpu-1.0-alt1.noarch | missing-url | info | Missing Url: in a package. |
|
volumes-profile-alt-server-v-1.1-alt1.noarch | rpm-filesystem-conflict-file-file | warn | File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-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. . ives. |
|
volumes-profile-alt-server-v-1.1-alt1.noarch | unsafe-tmp-usage-in-scripts | fail | The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/install2/initinstall.d/10-vm-profile.sh: $ grep /tmp/ /usr/share/install2/initinstall.d/10-vm-profile.sh #!/bin/sh # see also http://www.altlinux.org/Autoinstall message() { echo "vm-profile: $*" >>/tmp/vm-profile.log; } ROOT_MIN=7 # In Gb VAR_MIN=1 # In Gb mem="$(sed '/^MemTotal/s/[^0-9]//gp' /proc/meminfo)" # in kB |