| |
rpm id |
test |
status |
message |
 |
NetworkManager-openconnect-1.2.10-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. |
|
NetworkManager-sstp-1.3.2-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. |
 |
acmed-0.25.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
agola-0.5.0-alt3.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
agola-0.5.0-alt3.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
 |
arrow-glib-doc-12.0.0-alt2.3.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. |
|
branding-alt-container-11-alt1.src |
requires-ImageMagick |
info |
Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. |
|
branding-alt-container-notes-11-alt1.noarch |
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. |
|
branding-alt-server-11.0-alt16.src |
requires-ImageMagick |
info |
Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. |
|
branding-alt-server-graphics-11.0-alt16.noarch |
rpm-filesystem-conflict-file-file |
warn |
File /usr/share/design/server/icons/system-logo.png conflicts with the package branding-uzguard-server-bootsplash-1.0-alt0.2.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. |
|
branding-alt-server-notes-11.0-alt16.noarch |
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. |
|
branding-alt-virtualization-pve-11.0-alt0.2.src |
requires-ImageMagick |
info |
Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. |
|
branding-alt-virtualization-pve-notes-11.0-alt0.2.noarch |
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. |
|
branding-alt-virtualization-pve-release-11.0-alt0.2.noarch |
rpm-filesystem-conflict-file-file |
warn |
File /etc/altlinux-release conflicts with the package altlinux-release-sisyphus-20201124-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. |
|
caddy-2.9.1-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cert-manager-1.15.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/webhook conflicts with the package webhook-2.8.2-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. |
|
cloud-init-24.4.1-alt1.noarch |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
cloud-init-24.4.1-alt1.noarch |
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. |
|
cloud-init-24.4.1-alt1.noarch |
init-condrestart |
warn |
/etc/rc.d/init.d/cloud-config: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway./etc/rc.d/init.d/cloud-final: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway./etc/rc.d/init.d/cloud-init: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway./etc/rc.d/init.d/cloud-init-local: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway. |
 |
cloud-init-24.4.1-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/cloud-init-24.4.1-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/cloud-init.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/noarch/RPMS/cloud-init-24.4.1-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/66-azure-ephemeral.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
cni-plugins-1.6.1-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/cni-plugins-1.6.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/cni-plugins.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
cni-plugins-1.6.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
connman-1.43-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/connmand: not systemd compatible: lsb init header missing and connmand.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
connman-1.43-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/connman-1.43-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/connman_resolvconf.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
cri-o1.22-1.22.5-alt3.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cri-o1.23-1.23.5-alt3.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cri-o1.24-1.24.6-alt3.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cri-o1.25-1.25.5-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cri-o1.26-1.26.4-alt4.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cri-o1.27-1.27.8-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
cri-o1.28-1.28.11-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
dmeventd-1.02.204-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
dmsetup-1.02.204-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/dmsetup-1.02.204-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/10-dm.rules /usr/lib/udev/rules.d/11-dm-lvm.rules /usr/lib/udev/rules.d/13-dm-disk.rules /usr/lib/udev/rules.d/95-dm-notify.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
dracut-105-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
dracut-105-alt1.x86_64 |
unsafe-tmp-usage-in-scripts |
fail |
0755 |
|
dracut-live-105-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/lib/dracut/modules.d/90livenet/parse-livenet.sh: $ grep /tmp/ /usr/lib/dracut/modules.d/90livenet/parse-livenet.sh # live updates updates=$(getarg live.updates=) if [ "$updates" ]; then # make sure network comes up even if we're doing a local live device if [ "$netroot" ]; then echo > /tmp/net.ifaces fi echo "$updates" > /tmp/liveupdates.info echo '[ /tmp/liveupdates.done ]' > "$hookdir"/initqueue/finished/liveupdates.sh fi str_starts "$root" "live:" && liveurl="$root" str_starts "$liveurl" "live:" || return liveurl="${liveurl#live:}" Found error in /usr/lib/dracut/modules.d/90livenet/livenetroot.sh: $ grep /tmp/ /usr/lib/dracut/modules.d/90livenet/livenetroot.sh PATH=/usr/sbin:/usr/bin:/sbin:/bin RETRIES=${RETRIES:-100} SLEEP=${SLEEP:-5} [ /tmp/livenet.downloaded ] && exit 0 # args get passed from 40network/netroot netroot="$2" liveurl="${netroot#livenet:}" info "fetching $liveurl" sleep "$SLEEP" fi i=$((i + 1)) done > /tmp/livenet.downloaded # TODO: couldn't dmsquash-live-root handle this? if [ "${imgfile##*.}" = "iso" ]; then root=$(losetup -f) losetup "$root" "$imgfile" Found error in /usr/lib/dracut/modules.d/90dmsquash-live-autooverlay/create-overlay.sh: $ grep -A5 -B5 /tmp/ /usr/lib/dracut/modules.d/90dmsquash-live-autooverlay/create-overlay.sh #!/bin/sh type getarg > /dev/null 2>&1 || . /lib/dracut-lib.sh if getargbool 0 rd.live.debug; then exec > /tmp/create-overlay.$$.out exec 2>> /tmp/create-overlay.$$.out set -x fi gatherData() { overlay=$(getarg rd.live.overlay) Found error in /usr/lib/dracut/modules.d/90dmsquash-live/iso-scan.sh: $ grep -A5 -B5 /tmp/ /usr/lib/dracut/modules.d/90dmsquash-live/iso-scan.sh do_iso_scan() { local _name local dev for dev in /dev/disk/by-uuid/*; do _name=$(dev_unit_name "$dev") [ -e /tmp/isoscan-"${_name}" ] && continue : > /tmp/isoscan-"${_name}" mount -t auto -o ro "$dev" "/run/initramfs/isoscan" || continue if [ -f "/run/initramfs/isoscan/$isofile" ]; then losetup -f "/run/initramfs/isoscan/$isofile" udevadm trigger --action=add > /dev/null 2>&1 ln -s "$dev" /run/initramfs/isoscandev Found error in /usr/lib/dracut/modules.d/90dmsquash-live/dmsquash-live-root.sh: $ grep -A5 -B5 /tmp/ /usr/lib/dracut/modules.d/90dmsquash-live/dmsquash-live-root.sh command -v unpack_archive > /dev/null || . /lib/img-lib.sh PATH=/usr/sbin:/usr/bin:/sbin:/bin if getargbool 0 rd.live.debug; then exec > /tmp/liveroot.$$.out exec 2>> /tmp/liveroot.$$.out set -x fi [ -z "$1" ] && exit 1 livedev="$1" |
|
dracut-network-manager-105-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/lib/dracut/modules.d/35network-manager/nm-run.sh: $ grep /tmp/ /usr/lib/dracut/modules.d/35network-manager/nm-run.sh for _i in /sys/class/net/*; do [ "$_i" ] || continue state="/run/NetworkManager/devices/$(cat "$_i"/ifindex)" grep '^connection-uuid=' "$state" 2> /dev/null || continue ifname="${_i##*/}" dhcpopts_create "$state" > /tmp/dhclient."$ifname".dhcpopts source_hook initqueue/online "$ifname" /sbin/netroot "$ifname" done : > /tmp/nm.done |
|
driverctl-0.111-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
fapolicyd-1.3.3-alt2.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/fapolicyd-1.3.3-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/fapolicyd.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
fapolicyd-1.3.3-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
fcoe-utils-1.0.34-alt3.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
fcoe-utils-1.0.34-alt3.x86_64 |
systemd-check-socket-name |
experimental |
in fcoe-utils-1.0.34-alt3.x86_64: there is a socket fcoemon.socket but no service fcoemon.service. Ask ildar@ why it is not right. |
|
fence-sanlock-3.9.5-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/fence-sanlock-3.9.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/fence_sanlockd.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
fish-4.0.1-alt1.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. |
|
fish-4.0.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/share/fish/completions/yadm.fish conflicts with the package yadm-3.2.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. |
|
flannel-0.25.7-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/flannel-0.25.7-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/flannel.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
flannel-0.25.7-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
foomuuri-0.27-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/foomuuri-0.27-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/foomuuri.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
foomuuri-0.27-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
forgejo-10.0.1-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
freeradius-3.2.7-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
freeradius-3.2.7-alt1.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. |
|
freeradius-3.2.7-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/radiusd: not systemd compatible: lsb init header missing and radiusd.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
freeradius-3.2.7-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/freeradius-3.2.7-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/radiusd.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
frr-10.2-alt1.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. |
|
frr-10.2-alt1.x86_64 |
init-condrestart |
fail |
/etc/rc.d/init.d/frr: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix. |
|
frr-10.2-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/frr-10.2-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/frr.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
fwbuilder-6.0.0-alt2.beta.106.a5e1.x86_64 |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
fwbuilder-6.0.0-alt2.beta.106.a5e1.x86_64 |
freedesktop-desktop |
info |
desktop-file-validate utility printed the following message(s): /usr/share/applications/fwbuilder.desktop: hint: value "System;Settings;Security;Qt;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu |
|
galera-garbd-26.4.19-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/galera-garbd-26.4.19-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/garbd.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
gdm-data-48.0-alt1.noarch |
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. |
|
gdm-data-48.0-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/gdm-data-48.0-alt1.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/61-gdm.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
gdm-libs-48.0-alt1.x86_64 |
library-pkgnames |
info |
package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs |
|
gerbera-2.4.1-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
gerbera-2.4.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
gitea-act-0.2.11-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
gitea-tea-0.9.2-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/tea conflicts with the package tea-63.1.0-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. |
|
gnome-boxes-48.0-alt1.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. |
|
gnome-boxes-48.0-alt1.x86_64 |
freedesktop-desktop |
info |
desktop-file-validate utility printed the following message(s): /usr/share/applications/org.gnome.Boxes.desktop: hint: value "GNOME;GTK;System;Development;Emulator;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu |
|
grafana-11.5.2-alt1.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. |
|
grafana-11.5.2-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/grafana-11.5.2-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/grafana.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
guacd-1.5.5-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
guestfs-data-0.6-alt3.x86_64 |
missing-url |
info |
Missing Url: in a package. |
|
hivex-1.3.24-alt1.x86_64 |
library-pkgnames |
info |
package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs |
|
ignition-2.19.0-alt3.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
influxdb-1.8.10-alt1.1.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. |
|
installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
ves. |
|
installer-distro-virtualization-pve-stage2-11.0.0-alt0.2.noarch |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
s. |
|
iwpmd-53.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/iwpmd-53.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-iwpmd.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
kapacitor-1.5.9-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. |
|
kea-2.6.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kea-doc-2.6.1-alt1.noarch |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
kmscon-9.0.0-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
knot-3.4.4-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
knot-resolver-6.0.10-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/knot-resolver-6.0.10-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/knot-resolver.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
knot-resolver-6.0.10-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kpartx-0.11.1-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/kpartx-0.11.1-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/66-kpartx.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
kubernetes1.22-kubelet-1.22.17-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.22-master-1.22.17-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.22-node-1.22.17-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.23-kubelet-1.23.17-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.23-master-1.23.17-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.23-node-1.23.17-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.24-kubelet-1.24.17-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.24-master-1.24.17-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.24-node-1.24.17-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.25-kubelet-1.25.16-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.25-master-1.25.16-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.25-node-1.25.16-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.26-kubelet-1.26.15-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.26-master-1.26.15-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.26-node-1.26.15-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.27-common-1.27.16-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.27-common-1.27.16-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
kubernetes1.27-kubelet-1.27.16-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.27-master-1.27.16-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.27-node-1.27.16-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.28-common-1.28.15-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/kubernetes1.28-common-1.28.15-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/kubernetes.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
kubernetes1.28-kubelet-1.28.15-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.28-master-1.28.15-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
kubernetes1.28-node-1.28.15-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libdevmapper-event-1.02.204-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libdevmapper-event-lvm2.so but just /usr/lib64/libdevmapper-event-lvm2.so.2.03. According to SharedLibs Policy Draft, symlink /usr/lib64/libdevmapper-event-lvm2.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/libdevmapper-event-lvm2.so to \%files of libdevmapper-event-1.02.204-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. |
|
liberasurecode-doc-1.6.5-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. |
|
libgadu-devel-1.12.2-alt1.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. |
|
libgmime2.6-2.6.23-alt3.x86_64 |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
libguac-client-kubernetes-1.5.5-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-kubernetes.so but just /usr/lib64/libguac-client-kubernetes.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-kubernetes.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/libguac-client-kubernetes.so to \%files of libguac-client-kubernetes-1.5.5-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. |
|
libguac-client-rdp-1.5.5-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-rdp.so but just /usr/lib64/libguac-client-rdp.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-rdp.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/libguac-client-rdp.so to \%files of libguac-client-rdp-1.5.5-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. |
|
libguac-client-ssh-1.5.5-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-ssh.so but just /usr/lib64/libguac-client-ssh.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-ssh.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/libguac-client-ssh.so to \%files of libguac-client-ssh-1.5.5-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. |
|
libguac-client-telnet-1.5.5-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-telnet.so but just /usr/lib64/libguac-client-telnet.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-telnet.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/libguac-client-telnet.so to \%files of libguac-client-telnet-1.5.5-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. |
|
libguac-client-vnc-1.5.5-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libguac-client-vnc.so but just /usr/lib64/libguac-client-vnc.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libguac-client-vnc.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/libguac-client-vnc.so to \%files of libguac-client-vnc-1.5.5-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. |
|
libguac-devel-1.5.5-alt1.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. |
|
libpcsclite-2.3.3-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpcsclite_real.so but just /usr/lib64/libpcsclite_real.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libpcsclite_real.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/libpcsclite_real.so to \%files of libpcsclite-2.3.3-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. |
|
libpcsclite-devel-2.3.3-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpcscspy.so but just /usr/lib64/libpcscspy.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libpcscspy.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/libpcscspy.so to \%files of libpcsclite-devel-2.3.3-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. |
|
libproxy-tools-0.5.9-alt1.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.
lternatives. |
|
libsmi-0.5.0-alt3.x86_64 |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
libvirt-daemon-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-11.0.0-alt1.x86_64: there is a socket libvirtd-admin.socket but no service libvirtd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-11.0.0-alt1.x86_64: there is a socket libvirtd-ro.socket but no service libvirtd-ro.service. Ask ildar@ why it is not right.
in libvirt-daemon-11.0.0-alt1.x86_64: there is a socket libvirtd-tcp.socket but no service libvirtd-tcp.service. Ask ildar@ why it is not right.
in libvirt-daemon-11.0.0-alt1.x86_64: there is a socket libvirtd-tls.socket but no service libvirtd-tls.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-common-11.0.0-alt1.x86_64 |
init-condrestart |
fail |
/etc/rc.d/init.d/libvirt-guests: missing condrestart target. Note: alt-specific script %_sbindir/post_service (used in %post_service macro) depends on condrestart. It is wise to add condrestart anyway./etc/rc.d/init.d/libvirt-guests: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix. |
|
libvirt-daemon-driver-interface-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-interface-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-interface-11.0.0-alt1.x86_64: there is a socket virtinterfaced-admin.socket but no service virtinterfaced-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-interface-11.0.0-alt1.x86_64: there is a socket virtinterfaced-ro.socket but no service virtinterfaced-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-lxc-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-lxc-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-lxc-11.0.0-alt1.x86_64: there is a socket virtlxcd-admin.socket but no service virtlxcd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-lxc-11.0.0-alt1.x86_64: there is a socket virtlxcd-ro.socket but no service virtlxcd-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-network-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-network-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-network-11.0.0-alt1.x86_64: there is a socket virtnetworkd-admin.socket but no service virtnetworkd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-network-11.0.0-alt1.x86_64: there is a socket virtnetworkd-ro.socket but no service virtnetworkd-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-nodedev-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-nodedev-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-nodedev-11.0.0-alt1.x86_64: there is a socket virtnodedevd-admin.socket but no service virtnodedevd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-nodedev-11.0.0-alt1.x86_64: there is a socket virtnodedevd-ro.socket but no service virtnodedevd-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-nwfilter-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-nwfilter-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-nwfilter-11.0.0-alt1.x86_64: there is a socket virtnwfilterd-admin.socket but no service virtnwfilterd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-nwfilter-11.0.0-alt1.x86_64: there is a socket virtnwfilterd-ro.socket but no service virtnwfilterd-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-qemu-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-qemu-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-qemu-11.0.0-alt1.x86_64: there is a socket virtqemud-admin.socket but no service virtqemud-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-qemu-11.0.0-alt1.x86_64: there is a socket virtqemud-ro.socket but no service virtqemud-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-secret-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-secret-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-secret-11.0.0-alt1.x86_64: there is a socket virtsecretd-admin.socket but no service virtsecretd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-secret-11.0.0-alt1.x86_64: there is a socket virtsecretd-ro.socket but no service virtsecretd-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-storage-core-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-storage-core-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-storage-core-11.0.0-alt1.x86_64: there is a socket virtstoraged-admin.socket but no service virtstoraged-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-storage-core-11.0.0-alt1.x86_64: there is a socket virtstoraged-ro.socket but no service virtstoraged-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-driver-vbox-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-driver-vbox-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-driver-vbox-11.0.0-alt1.x86_64: there is a socket virtvboxd-admin.socket but no service virtvboxd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-driver-vbox-11.0.0-alt1.x86_64: there is a socket virtvboxd-ro.socket but no service virtvboxd-ro.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-lock-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-lock-11.0.0-alt1.x86_64: there is a socket virtlockd-admin.socket but no service virtlockd-admin.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-log-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-log-11.0.0-alt1.x86_64: there is a socket virtlogd-admin.socket but no service virtlogd-admin.service. Ask ildar@ why it is not right. |
|
libvirt-daemon-proxy-11.0.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
libvirt-daemon-proxy-11.0.0-alt1.x86_64 |
systemd-check-socket-name |
experimental |
in libvirt-daemon-proxy-11.0.0-alt1.x86_64: there is a socket virtproxyd-admin.socket but no service virtproxyd-admin.service. Ask ildar@ why it is not right.
in libvirt-daemon-proxy-11.0.0-alt1.x86_64: there is a socket virtproxyd-ro.socket but no service virtproxyd-ro.service. Ask ildar@ why it is not right.
in libvirt-daemon-proxy-11.0.0-alt1.x86_64: there is a socket virtproxyd-tcp.socket but no service virtproxyd-tcp.service. Ask ildar@ why it is not right.
in libvirt-daemon-proxy-11.0.0-alt1.x86_64: there is a socket virtproxyd-tls.socket but no service virtproxyd-tls.service. Ask ildar@ why it is not right. |
|
libvirt-libs-11.0.0-alt1.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. |
|
linstor-common-1.30.4-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. |
|
linstor-controller-1.30.4-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. |
|
linstor-controller-1.30.4-alt4.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
linstor-satellite-1.30.4-alt4.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
lldpad-1.1-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
loki-3.3.2-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
lvm2-2.03.30-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/lvm2-2.03.30-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/lvm2.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/lvm2-2.03.30-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/69-dm-lvm.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
lvm2-cmirrord-2.03.30-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
lvm2-lockd-2.03.30-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
lxc-templates-6.0.3-alt2.noarch |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/share/lxc/templates/lxc-local /usr/share/lxc/templates/lxc-oci conflict with the package pve-lxc-6.0.0-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. |
|
mariadb-11.4.5-alt2.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
mariadb-client-11.4.5-alt2.x86_64 |
rpm-filesystem-conflict-symlink-file |
warn |
symlink /usr/share/man/man8/mysqld.8.xz is a file in the package MySQL-server-8.0.41-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. |
|
mariadb-client-debuginfo-11.4.5-alt2.x86_64 |
rpm-filesystem-conflict-symlink-file |
warn |
symlink /usr/lib/debug/usr/bin/mysqltest.debug is a file in the package MySQL-client-debuginfo-8.0.41-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.
.
ives. |
|
mariadb-server-11.4.5-alt2.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/mariadb-server-11.4.5-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mariadb.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
mariadb-server-debuginfo-11.4.5-alt2.x86_64 |
rpm-filesystem-conflict-symlink-file |
warn |
symlink /usr/lib/debug/usr/sbin/mysqld.debug is a file in the package MySQL-server-debuginfo-8.0.41-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.
ives.
ives. |
|
mariadb-server-galera-11.4.5-alt2.x86_64 |
bin-permissions |
info |
not executable file /usr/bin/wsrep_sst_common |
|
mariadb-server-galera-11.4.5-alt2.x86_64 |
systemd-check-socket-name |
experimental |
in mariadb-server-galera-11.4.5-alt2.x86_64: there is a socket mariadbcheck.socket but no service mariadbcheck.service. Ask ildar@ why it is not right. |
|
matchbox-0.11.0-alt1.x86_64 |
rpm-filesystem-conflict-dir-dir |
fail |
directory /etc/matchbox is a directory in package matchbox-window-manager-1.2-alt5.1.x86_64 with different user,group or permissions. You should add explicit conflicts. |
|
matchbox-0.11.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
mdadm-4.4-alt3.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/mdadm: not systemd compatible: lsb init header missing and mdadm.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
mdadm-4.4-alt3.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/mdadm-4.4-alt3.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/01-md-raid-creating.rules /usr/lib/udev/rules.d/63-md-raid-arrays.rules /usr/lib/udev/rules.d/64-md-raid-assembly.rules /usr/lib/udev/rules.d/69-md-clustered-confirm-device.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
mdevctl-1.4.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/mdevctl-1.4.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-mdevctl.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
memcached-1.6.32-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
minio-2025.02.07-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
minio-2025.02.07-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
moosefs-chunkserver-4.57.5-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/moosefs-chunkserver-4.57.5-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/80-moosefs-chunkserver.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
mstflint-4.31.0.1-alt1.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. |
|
multipath-tools-0.11.1-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/multipathd: not systemd compatible: lsb init header missing and multipathd.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
multipath-tools-0.11.1-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/multipath-tools-0.11.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/multipath.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/multipath-tools-0.11.1-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/11-dm-mpath.rules /usr/lib/udev/rules.d/11-dm-parts.rules /usr/lib/udev/rules.d/56-multipath.rules /usr/lib/udev/rules.d/68-del-part-nodes.rules /usr/lib/udev/rules.d/99-z-dm-mpath-late.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
net-snmp-clients-5.9.4-alt1.1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package python3-module-snmpclitools-0.7.2-alt1.noarch, for example, /usr/bin/snmpbulkwalk (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
net-snmp-common-5.9.4-alt1.1.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/doc/net-snmp-common-5.9.4/passtest: $ grep /tmp/ /usr/share/doc/net-snmp-common-5.9.4/passtest # Process SET requests by simply logging the assigned value # Note that such "assignments" are not persistent, # nor is the syntax or requested value validated # if [ "$1" = "-s" ]; then echo $* >> /tmp/passtest.log exit 0 fi # # GETNEXT requests - determine next valid instance |
|
net-snmp-snmpd-5.9.4-alt1.1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/net-snmp-snmpd-5.9.4-alt1.1.x86_64.rpm: license not found in '/usr/share/license' directory: BSD-like /ALT/Sisyphus/files/x86_64/RPMS/net-snmp-snmpd-5.9.4-alt1.1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/net-snmp.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
netavark-1.14.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
nfs-ganesha-6.5-alt1.x86_64 |
altlinux-policy-shared-lib-contains-devel-so |
info |
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libganesha_nfsd.so but just /usr/lib64/libganesha_nfsd.so.6.5. According to SharedLibs Policy Draft, symlink /usr/lib64/libganesha_nfsd.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/libganesha_nfsd.so to \%files of nfs-ganesha-6.5-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. |
|
nfs-ganesha-6.5-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
nmstate-2.1.4-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
open-iscsi-iscsiuio-2.1.10-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
open-vm-tools-12.5.0-alt1.x86_64 |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
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 |
|
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. |
|
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 |
|
opennebula-context-6.6.1-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
openuds-actor-3.6.0-alt4.noarch |
freedesktop-categories |
warn |
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/UDS_Actor_Configuration.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt). |
|
openuds-actor-3.6.0-alt4.noarch |
freedesktop-desktop |
info |
desktop-file-validate utility printed the following message(s): /usr/share/applications/UDS_Actor_Configuration.desktop: hint: value "Settings;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu |
|
openuds-client-3.6.0-alt2.noarch |
freedesktop-categories |
warn |
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/UDSClient.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt). |
|
openuds-server-3.6.0-alt11.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
openuds-server-nginx-3.6.0-alt11.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/openuds-server-nginx-3.6.0-alt11.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/openuds.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
openuds-server-nginx-3.6.0-alt11.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
openuds-tunnel-3.6.0-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
ovirt-imageio-daemon-2.4.7-alt1.1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
ovirt-vmconsole-host-1.0.9-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
ovirt-vmconsole-proxy-1.0.9-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
ovn-24.03.4-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/ovn-24.03.4-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ovn.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
ovn-central-24.03.4-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
ovn-host-24.03.4-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
ovn-vtep-24.03.4-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pdns-4.9.1-alt1.1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pdns-ixfrdist-4.9.1-alt1.1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pgbouncer-1.23.0-alt1.1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/pgbouncer: not systemd compatible: lsb init header missing and pgbouncer.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
pgbouncer-1.23.0-alt1.1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/pgbouncer-1.23.0-alt1.1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pgbouncer.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
podman-5.4.1-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/podman-5.4.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/podman.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
podman-5.4.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
podman-docker-5.4.1-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/podman-docker-5.4.1-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/podman-docker.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
postgresql13-repmgr-5.5.0-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
postgresql13-repmgr-5.5.0-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
postgresql13-repmgr-5.5.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/postgresql13-repmgr-5.5.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
postgresql14-repmgr-5.5.0-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
postgresql14-repmgr-5.5.0-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql17-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
e, consider using alternatives. |
|
postgresql14-repmgr-5.5.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/postgresql14-repmgr-5.5.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
postgresql15-repmgr-5.5.0-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
postgresql15-repmgr-5.5.0-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql17-repmgr-5.5.0-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.
ider using alternatives. |
|
postgresql15-repmgr-5.5.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/postgresql15-repmgr-5.5.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
pptpd-1.5.0-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/pptpd: not systemd compatible: lsb init header missing and pptpd.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
prometheus-common-3.1.0-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/prometheus-common-3.1.0-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/prometheus.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
promtail-3.3.2-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
proxmox-backup-server-3.3.3.1-alt5.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/proxmox-backup-server-3.3.3.1-alt5.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-proxmox-backup-server.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
proxmox-backup-server-3.3.3.1-alt5.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-acme-1.5.1-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. |
|
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-backup-restore-image-0.5-alt1.x86_64 |
rpm-package-is-obsoleted |
warn |
The package is obsoleted by the package proxmox-backup-restore-image-3.3.3.1-alt1.x86_64, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of proxmox-backup-restore-image-3.3.3.1-alt1.x86_64 to remove Obsoletes: tag. |
|
pve-cluster-8.0.10-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-container-5.2.2-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-firewall-5.1.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/pve-firewall-5.1.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pve-firewall.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
pve-firewall-5.1.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-ha-manager-4.0.6-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-lxc-6.0.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/share/lxc/templates/lxc-local /usr/share/lxc/templates/lxc-oci conflict with the package lxc-templates-6.0.3-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
pve-lxc-6.0.0-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-manager-8.3.3-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. |
|
pve-manager-8.3.3-alt4.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/pve-manager-8.3.3-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pve-manager.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
pve-manager-8.3.3-alt4.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-qemu-common-9.1.2-alt3.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-qemu-common-9.1.2-alt3.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/share/qemu/trace-events-all conflicts with the package qemu-tools-9.2.3-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.
cts are avoidable, consider using alternatives. |
|
pve-qemu-server-8.3.3-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
pve-qemu-system-9.1.2-alt3.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/qemu-vmsr-helper conflicts with the package qemu-vmsr-helper-9.2.3-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.
ives.
ves.
idable, consider using alternatives. |
|
pve-storage-8.3.3-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/pve-storage-8.3.3-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/50-rbd-pve.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
python3-module-pyldb-2.9.2-alt1.x86_64 |
library-pkgnames |
info |
package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs |
|
qemu-common-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/libexec/qemu-bridge-helper /usr/share/man/man1/qemu.1.xz conflict with the package pve-qemu-system-9.1.2-alt3.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. |
|
qemu-device-display-vhost-user-gpu-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/libexec/vhost-user-gpu conflicts with the package pve-qemu-system-9.1.2-alt3.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. |
|
qemu-guest-agent-9.2.3-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/qemu-guest-agent-9.2.3-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-qemu-guest-agent.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
qemu-img-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/bin/qemu-storage-daemon /usr/share/man/man7/qemu-storage-daemon-qmp-ref.7.xz conflict with the package pve-qemu-system-9.1.2-alt3.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. |
|
qemu-pr-helper-9.2.3-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
qemu-system-aarch64-core-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/qemu-system-aarch64 conflicts with the package pve-qemu-system-9.1.2-alt3.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. |
|
qemu-system-hppa-core-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/share/qemu/hppa-firmware.img /usr/share/qemu/hppa-firmware64.img conflict with the package pve-qemu-common-9.1.2-alt3.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. |
|
qemu-system-ppc-core-9.2.3-alt1.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. |
|
qemu-system-x86-core-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/qemu-system-x86_64 conflicts with the package pve-qemu-system-9.1.2-alt3.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. |
|
qemu-tools-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/share/qemu/trace-events-all conflicts with the package pve-qemu-common-9.1.2-alt3.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. |
|
qemu-vmsr-helper-9.2.3-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/qemu-vmsr-helper conflicts with the package pve-qemu-system-9.1.2-alt3.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. |
|
qemu-vmsr-helper-9.2.3-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
rdma-core-53.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/rdma-core-53.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-rdma-ndd.rules /usr/lib/udev/rules.d/60-rdma-persistent-naming.rules /usr/lib/udev/rules.d/75-rdma-description.rules /usr/lib/udev/rules.d/90-rdma-hw-modules.rules /usr/lib/udev/rules.d/90-rdma-ulp-modules.rules /usr/lib/udev/rules.d/90-rdma-umad.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
remmina-1.4.39-alt1.x86_64 |
freedesktop-categories |
warn |
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/org.remmina.Remmina.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt). |
|
resource-agents-4.16.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/resource-agents-4.16.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/resource-agents.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
resource-agents-4.16.0-alt1.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 /usr/lib/ocf/resource.d/heartbeat/rabbitmq-server-ha: $ grep /tmp/ /usr/lib/ocf/resource.d/heartbeat/rabbitmq-server-ha The debug flag for agent (${OCF_RESKEY_binary}) instance. In the /tmp/ directory will be created rmq-* files for log some operations and ENV values inside OCF-script. AMQP server (${OCF_RESKEY_binary}) debug flag local rc=$OCF_ERR_GENERIC local LH="${LL} monitor:" ocf_log debug "${LH} action start." if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-monitor.log env >> /tmp/rmq-monitor.log echo "$d [monitor] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi get_monitor rc=$? ocf_log debug "${LH} role: ${OCF_RESKEY_CRM_meta_role}" ocf_log debug "${LH} result: $rc" -- local LH="${LL} start:" local nowtime if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-start.log env >> /tmp/rmq-start.log echo "$d [start] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." get_status -- local rc=$OCF_ERR_GENERIC local LH="${LL} stop:" if ocf_is_true "${OCF_RESKEY_debug}"; then d=$(date '+%Y%m%d %H:%M:%S') echo $d >> /tmp/rmq-stop.log env >> /tmp/rmq-stop.log echo "$d [stop] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." ocf_log info "${LH} Deleting master attribute" -- local LH="${LL} notify:" local nodelist if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-notify.log env >> /tmp/rmq-notify.log echo "$d [notify] ${OCF_RESKEY_CRM_meta_notify_type}-${OCF_RESKEY_CRM_meta_notify_operation} promote='${OCF_RESKEY_CRM_meta_notify_promote_uname}' demote='${OCF_RESKEY_CRM_meta_notify_demote_uname}' master='${OCF_RESKEY_CRM_meta_notify_master_uname}' slave='${OCF_RESKEY_CRM_meta_notify_slave_uname}' start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi if [ "${OCF_RESKEY_CRM_meta_notify_type}" = 'post' ] ; then # POST- anything notify section case "$OCF_RESKEY_CRM_meta_notify_operation" in -- local rc=$OCF_ERR_GENERIC local LH="${LL} promote:" if ocf_is_true "${OCF_RESKEY_debug}"; then d=$(date '+%Y%m%d %H:%M:%S') echo $d >> /tmp/rmq-promote.log env >> /tmp/rmq-promote.log echo "$d [promote] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." get_monitor |
|
rsyslog-8.2502.0-alt1.x86_64 |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
rygel-0.44.2-alt1.x86_64 |
freedesktop-categories |
warn |
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/rygel-preferences.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt). |
|
sanlock-3.9.5-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/sanlock-3.9.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/sanlock.conf /usr/lib/tmpfiles.d/wdmd.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
shorewall6-5.2.8-alt2.noarch |
uncompressed-manpages |
info |
Package contains uncompressed manual pages. |
|
snapd-2.66.1-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/snapd-2.66.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/snapd.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
snapd-2.66.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
spice-vdagent-0.22.1-alt2.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/spice-vdagent-0.22.1-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/spice-vdagentd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/spice-vdagent-0.22.1-alt2.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/70-spice-vdagentd.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
squid-7.0.1-alt1.x86_64 |
init-lsb |
fail |
/etc/rc.d/init.d/squid: not systemd compatible: lsb init header missing and squid.service is not present. See http://www.altlinux.org/Services_Policy for details. |
|
squid-7.0.1-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/squid-7.0.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/squid.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
squid-7.0.1-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. |
|
squid-doc-7.0.1-alt1.noarch |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
srp_daemon-53.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/srp_daemon-53.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/60-srp_daemon.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
systemd-255.18-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/systemd-255.18-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/README /usr/lib/tmpfiles.d/credstore.conf /usr/lib/tmpfiles.d/journal-nocow.conf /usr/lib/tmpfiles.d/provision.conf /usr/lib/tmpfiles.d/systemd-nologin.conf /usr/lib/tmpfiles.d/systemd-pstore.conf /usr/lib/tmpfiles.d/systemd-tmp.conf /usr/lib/tmpfiles.d/systemd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/systemd-255.18-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/70-uaccess.rules /usr/lib/udev/rules.d/71-seat.rules /usr/lib/udev/rules.d/73-seat-late.rules /usr/lib/udev/rules.d/90-vconsole.rules /usr/lib/udev/rules.d/99-systemd.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
systemd-container-255.18-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/systemd-container-255.18-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/systemd-nspawn.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
systemd-networkd-255.18-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/systemd-networkd-255.18-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/systemd-network.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
systemd-portable-255.18-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/systemd-portable-255.18-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/portables.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
systemd-stateless-255.18-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/systemd-stateless-255.18-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/etc.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
systemd-tmpfiles-common-255.18-alt1.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/systemd-tmpfiles-common-255.18-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/home.conf /usr/lib/tmpfiles.d/legacy.conf /usr/lib/tmpfiles.d/tmp.conf /usr/lib/tmpfiles.d/var.conf /usr/lib/tmpfiles.d/x11.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
targetcli-2.1.54-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
telegraf-1.33.2-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/telegraf-1.33.2-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/telegraf.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
telegraf-1.33.2-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. |
|
traefik-3.3.3-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
trivy-0.60.0-alt1.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. |
|
trivy-server-0.60.0-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
udev-255.18-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/udev-255.18-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/static-nodes-permissions.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/udev-255.18-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/50-udev-default.rules /usr/lib/udev/rules.d/60-autosuspend.rules /usr/lib/udev/rules.d/60-block.rules /usr/lib/udev/rules.d/60-cdrom_id.rules /usr/lib/udev/rules.d/60-dmi-id.rules /usr/lib/udev/rules.d/60-drm.rules /usr/lib/udev/rules.d/60-evdev.rules /usr/lib/udev/rules.d/60-fido-id.rules /usr/lib/udev/rules.d/60-infiniband.rules /usr/lib/udev/rules.d/60-input-id.rules /usr/lib/udev/rules.d/60-persistent-alsa.rules /usr/lib/udev/rules.d/60-persistent-input.rules /usr/lib/udev/rules.d/60-persistent-storage-mtd.rules /usr/lib/udev/rules.d/60-persistent-storage-tape.rules /usr/lib/udev/rules.d/60-persistent-storage.rules /usr/lib/udev/rules.d/60-persistent-v4l.rules /usr/lib/udev/rules.d/60-sensor.rules /usr/lib/udev/rules.d/60-serial.rules /usr/lib/udev/rules.d/64-btrfs.rules /usr/lib/udev/rules.d/70-camera.rules /usr/lib/udev/rules.d/70-joystick.rules /usr/lib/udev/rules.d/70-memory.rules /usr/lib/udev/rules.d/70-mouse.rules /usr/lib/udev/rules.d/70-power-switch.rules /usr/lib/udev/rules.d/70-touchpad.rules /usr/lib/udev/rules.d/75-net-description.rules /usr/lib/udev/rules.d/75-probe_mtd.rules /usr/lib/udev/rules.d/78-sound-card.rules /usr/lib/udev/rules.d/80-drivers.rules /usr/lib/udev/rules.d/80-net-setup-link.rules /usr/lib/udev/rules.d/81-net-dhcp.rules /usr/lib/udev/rules.d/90-iocost.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
udev-255.18-alt1.x86_64 |
sisyphus_check-check-dirlist |
warn |
sisyphus_check --check-dirlist failed: package contains a directory /etc/udev/rules.d that exclusively belongs to package udev-rules |
|
udev-rules-sgutils-1.48-alt2.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/udev-rules-sgutils-1.48-alt2.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/00-scsi-sg3_config.rules /usr/lib/udev/rules.d/40-usb-blacklist.rules /usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules /usr/lib/udev/rules.d/55-scsi-sg3_id.rules /usr/lib/udev/rules.d/58-scsi-sg3_symlink.rules /usr/lib/udev/rules.d/59-fc-wwpn-id.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
uki-direct-24.11-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
urbackup-client-2.5.25-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
urbackup-server-2.5.33-alt1.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. |
|
urbackup-server-2.5.33-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
valkey-8.0.2-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
vdsm-4.50.6-alt3.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/vdsm-4.50.6-alt3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/vdsm.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/noarch/RPMS/vdsm-4.50.6-alt3.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/12-vdsm-lvm.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
vdsm-4.50.6-alt3.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
vdsm-hook-checkips-4.50.6-alt3.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
vdsm-hook-localdisk-4.50.6-alt3.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/vdsm-hook-localdisk-4.50.6-alt3.noarch.rpm: invalid udev rules path: /usr/lib/udev/rules.d/12-vdsm-localdisk.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
vhostmd-1.1-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victorialogs-1.15.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-1.110.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-cluster-vminsert-1.110.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-cluster-vmselect-1.110.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-cluster-vmstorage-1.110.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-utils-1.110.1-alt1.x86_64 |
rpm-obsolete-live-package |
info |
The package obsoletes the package victoriametrics-vmctl-0.4.0-alt1.x86_64, but the package victoriametrics-vmctl-0.4.0-alt1.x86_64 is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary. |
|
victoriametrics-vmagent-1.110.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-vmalert-1.110.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-vmauth-1.110.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
victoriametrics-vmctl-0.4.0-alt1.x86_64 |
rpm-package-is-obsoleted |
warn |
The package is obsoleted by the package victoriametrics-utils-1.110.1-alt1.x86_64, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of victoriametrics-utils-1.110.1-alt1.x86_64 to remove Obsoletes: tag. |
|
virt-manager-4.1.0-alt3.noarch |
freedesktop-categories |
warn |
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/virt-manager.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt). |
|
vitastor-mon-2.1.0-alt1.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
vitastor-osd-2.1.0-alt1.x86_64 |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/vitastor-osd-2.1.0-alt1.x86_64.rpm: license not found in '/usr/share/license' directory: VNPL-1.1 /ALT/Sisyphus/files/x86_64/RPMS/vitastor-osd-2.1.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-vitastor.rules sisyphus_check: check-udev ERROR: udev rules path violation |
|
vitastor-osd-2.1.0-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
vmango-0.12.1-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
vpnc-0.5.3-alt7.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. |
|
vsftpd-3.0.5-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |