using alternatives.
/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 | |
|---|---|---|---|---|
|
3proxy-0.6.1-alt3.x86_64 | init-but-no-native-systemd | info | The package have SysV init script(s) but no native systemd files. |
|
3proxy-0.6.1-alt3.x86_64 | init-lsb | fail | /etc/rc.d/init.d/3proxy: not systemd compatible: lsb init header missing and 3proxy.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
3proxy-0.6.1-alt3.x86_64 | rpm-filesystem-conflict-file-file | warn | File /usr/bin/proxy conflicts with the package python3-module-proxy-py-2.4.10-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. using alternatives. |
|
3proxy-0.6.1-alt3.x86_64 | subdir-in-var-run | info | Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them. |
|
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.8.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.30.0-alt1.x86_64 | sisyphus_check | fail | sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/drbd-utils-9.30.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 |
|
event-driven-servers-1.0-alt2.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. |
|
event-driven-servers-1.0-alt2.x86_64 | 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 /etc/mavis/sample/tac_plus-ng.cfg: $ grep /tmp/ /etc/mavis/sample/tac_plus-ng.cfg id = tac_plus-ng { #debug = PACKET AUTHEN AUTHOR log mysyslog log accesslog { destination = /tmp/access.log } log authorlog { destination = /tmp/author.log } log authorlog2 { destination = ">/tmp/author2.log" } access log = mysyslog access log = accesslog authorization log = authorlog accounting log = mysyslog } } } # mavis module = tacinfo_cache { # directory = /tmp/tacinfo0 # } mavis module = groups { resolve gids = yes resolve gids attribute = TACMEMBER |
|
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. |
|
pi-hole-5.18.4-alt5.noarch | rpm-filesystem-conflict-file-file | warn | File /etc/dnsmasq.conf conflicts with the package dnsmasq-2.90-alt4.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. |
|
pi-hole-5.18.4-alt5.noarch | sisyphus_check | fail | sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/pi-hole-5.18.4-alt5.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/pi-hole.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
pi-hole-5.18.4-alt5.noarch | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
pi-hole-ftl-5.25.2-alt1.x86_64 | sisyphus_check | fail | sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/pi-hole-ftl-5.25.2-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pi-hole-ftl.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
pi-hole-ftl-5.25.2-alt1.x86_64 | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
pidgin-2.14.12-alt2.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. |
|
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.5.2-alt1.noarch | systemd-but-no-native-init | experimental | The package have native systemd file(s) but no SysV init scripts. |
|
ravada-2.3.2-alt1.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.2-alt1.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. |
|
tac_plus-ng-1.0-alt2.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 |