Repocop reports by acl

  packager rpm id test status message
@core bind-9.18.31-alt1.src specfile-useradd-n warn -n in useradd is compat option and can be removed any time. Use -N instead.
@core bind-9.18.31-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/bind: not systemd compatible: lsb init header missing and bind.service is not present. See http://www.altlinux.org/Services_Policy for details.
@core bind-9.18.31-alt1.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/bind-9.18.31-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/bind.conf sisyphus_check: check-fhs ERROR: FHS violation
imz tests-for-installed-python3-pkgs-0.1.25-alt1.noarch missing-url info Missing Url: in a package.
sin libsss_autofs-2.9.5-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
sin libsss_sudo-2.9.5-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
sin sssd-2.9.5-alt1.src specfile-useradd-n warn -n in useradd is compat option and can be removed any time. Use -N instead.
sin sssd-2.9.5-alt1.x86_64 systemd-check-socket-name experimental in sssd-2.9.5-alt1.x86_64: there is a socket sssd-pam-priv.socket but no service sssd-pam-priv.service. Ask ildar@ why it is not right.
sin sssd-kcm-2.9.5-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
sin sssd-pac-2.9.5-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev 389-ds-base-2.4.6-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev certmonger-0.79.20-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.
slev certmonger-0.79.20-alt2.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/certmonger-0.79.20-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/certmonger.conf sisyphus_check: check-fhs ERROR: FHS violation
slev cockpit-tests-311.1-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev cockpit-tests-311.1-alt2.x86_64 systemd-check-socket-name experimental in cockpit-tests-311.1-alt2.x86_64: there is a socket cockpit-session.socket but no service cockpit-session.service. Ask ildar@ why it is not right.
slev cockpit-ws-311.1-alt2.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/cockpit-ws-311.1-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/cockpit-tempfiles.conf sisyphus_check: check-fhs ERROR: FHS violation
slev cockpit-ws-311.1-alt2.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev cockpit-ws-311.1-alt2.x86_64 systemd-check-socket-name experimental in cockpit-ws-311.1-alt2.x86_64: there is a socket cockpit-wsinstance-https-factory.socket but no service cockpit-wsinstance-https-factory.service. Ask ildar@ why it is not right.
slev dogtag-pki-acme-11.4.3-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.
slev dogtag-pki-ca-11.4.3-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.
slev dogtag-pki-java-11.4.3-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.
slev dogtag-pki-kra-11.4.3-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.
slev dogtag-pki-server-11.4.3-alt4.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev dogtag-pki-server-theme-11.4.3-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.
slev dogtag-pki-tps-11.4.3-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.
slev fleet-commander-logger-0.15.1-alt14.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/fleet-commander-logger-0.15.1-alt14.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/81-fleet-commander-logger.rules sisyphus_check: check-udev ERROR: udev rules path violation
slev freeipa-client-epn-4.11.2-alt3.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev freeipa-common-4.11.2-alt3.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.
slev freeipa-healthcheck-0.17-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev freeipa-server-4.11.2-alt3.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/freeipa-server-4.11.2-alt3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/ipa.conf sisyphus_check: check-fhs ERROR: FHS violation
slev freeipa-server-4.11.2-alt3.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev freeipa-server-4.11.2-alt3.x86_64 systemd-check-socket-name experimental in freeipa-server-4.11.2-alt3.x86_64: there is a socket ipa-otpd.socket but no service ipa-otpd.service. Ask ildar@ why it is not right.
slev freeipa-server-common-4.11.2-alt3.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.
slev freeipa-server-dns-4.11.2-alt3.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev gssproxy-0.9.1-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.
slev gssproxy-0.9.1-alt1.1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
slev opendnssec-2.1.14-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.
slev opendnssec-2.1.14-alt1.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/opendnssec-2.1.14-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/opendnssec.conf sisyphus_check: check-fhs ERROR: FHS violation
slev python3-module-proxy-py-2.4.9-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/bin/proxy conflicts with the package libproxy-tools-0.5.9-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.
slev python3-module-pyproject-fmt-2.5.0-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/pyproject-fmt conflicts with the package python3-module-pyproject-parser-0.11.1-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.
slev python3-module-system-seed-wheels-0.0.1-alt1.x86_64 missing-url info Missing Url: in a package.
slev python3-module-system-seed-wheels-wheels-0.0.1-alt1.x86_64 missing-url info Missing Url: in a package.
slev uid_wrapper-1.3.1-alt1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libuid_wrapper.so but just /usr/lib64/libuid_wrapper.so.0.2.1. According to SharedLibs Policy Draft, symlink /usr/lib64/libuid_wrapper.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/libuid_wrapper.so to \%files of uid_wrapper-1.3.1-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.
viy tomcat-el-3.0-api-9.0.83-alt1_1jpp11.noarch altlinux-java-duplicate-jars info file /usr/share/java/tomcat/tomcat-el-api.jar confilicts with package: tomcat-lib-9.0.83-alt1_1jpp11.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar
viy tomcat-el-3.0-api-9.0.83-alt1_1jpp11.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/share/java/tomcat-el-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt2_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
viy tomcat-jsp-2.3-api-9.0.83-alt1_1jpp11.noarch altlinux-java-duplicate-jars info file /usr/share/java/tomcat/tomcat-jsp-api.jar confilicts with package: tomcat-lib-9.0.83-alt1_1jpp11.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar
viy tomcat-jsp-2.3-api-9.0.83-alt1_1jpp11.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/share/java/tomcat-jsp-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt2_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
viy tomcat-lib-9.0.83-alt1_1jpp11.noarch altlinux-java-duplicate-jars info file /usr/share/java/tomcat/tomcat-servlet-api.jar confilicts with package: tomcat-servlet-4.0-api-9.0.83-alt1_1jpp11.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar
viy tomcat-servlet-4.0-api-9.0.83-alt1_1jpp11.noarch altlinux-java-duplicate-jars info file /usr/share/java/tomcat/tomcat-servlet-api.jar confilicts with package: tomcat-lib-9.0.83-alt1_1jpp11.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar
viy tomcat-servlet-4.0-api-9.0.83-alt1_1jpp11.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt2_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.

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