Repocop reports by acl

  packager rpm id test status message
andy 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.
andy 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
andy drbd-reactor-1.5.0-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
andy 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
andy fence-agents-common-4.15.0-alt1.noarch sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/fence-agents-common-4.15.0-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/fence-agents.conf sisyphus_check: check-fhs ERROR: FHS violation
andy ifupdown2-3.2.0.9-alt1.noarch bin-permissions info not executable file /usr/sbin/ip-brctl
andy ifupdown2-3.2.0.9-alt1.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
andy ledmon-1.0.0-alt2.a8b320d3.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
andy ledmon-1.0.0-alt2.a8b320d3.x86_64 uncompressed-manpages info Package contains uncompressed manual pages.
andy 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.
andy pve-backup-restore-image-0.4-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.
andy pve-backup-restore-image-0.4-alt1.x86_64 missing-url info Missing Url: in a package.
andy pve-enable-0.1-alt1.x86_64 missing-url info Missing Url: in a package.
andy python3-module-prometheus-pve-exporter-3.4.5-alt1.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
andy 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.
andy ravada-2.3.1-alt2.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
andy 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.
andy udev-rules-hotplug-cpu-1.0-alt1.noarch missing-url info Missing Url: in a package.
andy 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.
andy 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
shaba open-vm-tools-12.5.0-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
shaba open-vm-tools-12.5.0-alt1.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-12.5.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/open-vm-tools-vgauthd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-12.5.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-vmware-guest-tools.rules /usr/lib/udev/rules.d/98-open-vm-tools.rules /usr/lib/udev/rules.d/99-vmware-scsi-udev.rules sisyphus_check: check-udev ERROR: udev rules path violation
shaba open-vm-tools-12.5.0-alt1.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.
shaba open-vm-tools-desktop-12.5.0-alt1.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-desktop-12.5.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/open-vm-tools-desktop.conf sisyphus_check: check-fhs ERROR: FHS violation
shaba pve-container-5.2.0-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
shaba pve-firewall-5.0.7-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.
shaba pve-firewall-5.0.7-alt1.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/pve-firewall-5.0.7-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pve-firewall.conf sisyphus_check: check-fhs ERROR: FHS violation
shaba pve-firewall-5.0.7-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
shaba pve-ha-manager-4.0.5-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
shaba pve-qemu-server-8.2.4-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
vt coccinelle-1.2-alt1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/bin/spatch /usr/share/man/man1/spatch.1.xz conflict with the package schilytools-2024.03.21-alt2.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.

generated by repocop at Wed Nov 6 02:22:27 2024