Repocop reports by acl

	packager	rpm id	test	status	message
	maks1ms	go-size-analyzer-1.10.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/gsa conflicts with the package libgwenhywfar-5.14.1-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.
	maks1ms	kernel-modules-drbd9-talos-9.3.0-alt1.396347.1.src	unmet-dependency-build-no-suitable-version	fail	build dependency kernel-headers-modules-talos has no suitable version.
	maks1ms	moonlight-qt-6.1.0-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/com.moonlight_stream.Moonlight.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).
	maks1ms	nvidia-fabricmanager-570-570.158.01-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib/libnvfm.so but just /usr/lib/libnvfm.so.1. According to SharedLibs Policy Draft, symlink /usr/lib/libnvfm.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/lib/libnvfm.so to \%files of nvidia-fabricmanager-570-570.158.01-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.
	maks1ms	nvidia-fabricmanager-570-570.158.01-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.
	maks1ms	nvidia-fabricmanager-570-570.158.01-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.
	maks1ms	nvidia-fabricmanager-570-570.158.01-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	maks1ms	opentofu-1.11.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/tofu conflicts with the package tofu-3.2-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.
	maks1ms	stplr-0.0.30-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/stplr-0.0.30-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/stplr.conf sisyphus_check: check-fhs ERROR: FHS violation
	obirvalger	go-task-3.48.0-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/share/zsh/site-functions/_task conflicts with the package zsh-completion-task-3.4.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.
	obirvalger	netplan-1.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-base-19.2.3-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libosd_tp.so but just /usr/lib64/libosd_tp.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libosd_tp.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/libosd_tp.so to \%files of ceph-base-19.2.3-alt2.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. pocop test.
	shaba	ceph-base-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-common-19.2.3-alt2.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
	shaba	ceph-common-19.2.3-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/ceph-common-19.2.3-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ceph-common.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/ceph-common-19.2.3-alt2.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/50-rbd.rules sisyphus_check: check-udev ERROR: udev rules path violation
	shaba	ceph-common-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-exporter-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-fuse-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-immutable-object-cache-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-mds-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-mgr-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-mgr-cephadm-19.2.3-alt2.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.
	shaba	ceph-mgr-dashboard-19.2.3-alt2.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.
	shaba	ceph-mgr-diskprediction-local-19.2.3-alt2.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.
	shaba	ceph-mgr-modules-core-19.2.3-alt2.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.
	shaba	ceph-mgr-rook-19.2.3-alt2.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.
	shaba	ceph-mon-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-osd-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-radosgw-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	ceph-volume-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	cephfs-mirror-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	forgejo-11.0.10-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	rbd-mirror-19.2.3-alt2.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no SysV init scripts.
	shaba	talos-devel-1.12.4-alt1.noarch	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/gocode/src/github.com/siderolabs/talos/hack/test/e2e-qemu.sh: $ grep /tmp/ /usr/share/gocode/src/github.com/siderolabs/talos/hack/test/e2e-qemu.sh QEMU_FLAGS+=("--image-cache-path=${TMP}/image-cache") QEMU_FLAGS+=("--image-cache-tls-cert-file=${TMP}/image-cache-tls.crt") QEMU_FLAGS+=("--image-cache-tls-key-file=${TMP}/image-cache-tls.key") ;; http-proxy) "${TALOSCTL}" debug air-gapped 172.20.1.1 > /tmp/airgapped.log 2>&1 & sleep 5 # wait for the air-gapped server to start cat air-gapped-patch.yaml mv air-gapped-patch.yaml "${TMP}/air-gapped-patch.yaml" QEMU_FLAGS+=("--config-patch=@${TMP}/air-gapped-patch.yaml") ;; secure-http-proxy) "${TALOSCTL}" debug air-gapped 172.20.1.1 > /tmp/airgapped-secure.log 2>&1 & sleep 5 # wait for the air-gapped server to start cat air-gapped-patch.yaml mv air-gapped-patch.yaml "${TMP}/air-gapped-patch.yaml" QEMU_FLAGS+=("--config-patch=@${TMP}/air-gapped-patch.yaml") ;; https-reverse-proxy) "${TALOSCTL}" debug air-gapped 172.20.1.1 > /tmp/airgapped-reverse-proxy.log 2>&1 & sleep 5 # wait for the air-gapped server to start cat air-gapped-patch.yaml mv air-gapped-patch.yaml "${TMP}/air-gapped-patch.yaml" QEMU_FLAGS+=("--config-patch=@${TMP}/air-gapped-patch.yaml") jobs -p | xargs -r kill "${TALOSCTL}" cluster destroy \ --name "${CLUSTER_NAME}" \ --provisioner "${PROVISIONER}" \ --save-cluster-logs-archive-path="/tmp/logs-${LOG_ARCHIVE_SUFFIX}.tar.gz" \ --save-support-archive-path="/tmp/support-${LOG_ARCHIVE_SUFFIX}.zip" } trap destroy_cluster SIGINT EXIT create_cluster