Майнтейнер: Alexei Takaseev
Информация Пакеты Bugs and FR Repocop
Сообщения от repocop:| пакет | статус | тест | сообщение |
|---|---|---|---|
| accel-ppp-1.12.0-alt6.x86_64 |
 info | subdir-in-var-run | 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. |
| bcunit-3.0.2-alt1.x86_64 |
info | library-pkgnames | package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs |
| getstream-20120411-alt4.x86_64 |
info | init-but-no-native-systemd | The package have SysV init script(s) but no native systemd files. |
| libqt3-3.3.8d-alt16.1.x86_64 |
 warn | freedesktop-categories | Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/qt3-qtconfig.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). |
| libunbound-1.17.1-alt1.x86_64 |
 experimental | systemd-but-no-native-init | The package have native systemd file(s) but no SysV init scripts. |
| lighttpd-1.4.67-alt1.x86_64 |
warn | init-lsb | /etc/rc.d/init.d/lighttpd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
| nftables-1.0.7-alt1.x86_64 |
experimental | systemd-but-no-native-init | The package have native systemd file(s) but no SysV init scripts. |
| nsd-4.6.1-alt1.src |
warn | specfile-useradd-n | -n in useradd is compat option and can be removed any time. Use -N instead. |
| openqa-4.6-alt9.1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| openqa-4.6-alt9.1.x86_64 |
experimental | systemd-but-no-native-init | The package have native systemd file(s) but no SysV init scripts. |
| openqa-doc-4.6-alt9.1.x86_64 |
info | arch-dep-package-consists-of-usr-share | 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. |
| openqa-local-db-4.6-alt9.1.x86_64 |
experimental | systemd-but-no-native-init | The package have native systemd file(s) but no SysV init scripts. |
| openqa-worker-4.6-alt9.1.x86_64 |
experimental | systemd-but-no-native-init | The package have native systemd file(s) but no SysV init scripts. |
| postgresql11-pg_partman-4.7.2-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql15-pg_partman-4.7.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. |
| postgresql11-pg_partman-4.7.2-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| postgresql11-repmgr-5.3.3-alt2.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql15-repmgr-5.3.3-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. |
| postgresql11-repmgr-5.3.3-alt2.x86_64 |
warn | init-lsb | /etc/rc.d/init.d/repmgr: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
| postgresql12-pg_partman-4.7.2-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql15-pg_partman-4.7.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. |
| postgresql12-pg_partman-4.7.2-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| postgresql12-repmgr-5.3.3-alt2.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql15-repmgr-5.3.3-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. |
| postgresql12-repmgr-5.3.3-alt2.x86_64 |
warn | init-lsb | /etc/rc.d/init.d/repmgr: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
| postgresql13-pg_partman-4.7.2-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql15-pg_partman-4.7.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. able, consider using alternatives. |
| postgresql13-pg_partman-4.7.2-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| postgresql13-repmgr-5.3.3-alt2.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc /usr/lib64/pgsql/repmgr.so conflict with the package postgresql15-repmgr-5.3.3-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. |
| postgresql13-repmgr-5.3.3-alt2.x86_64 |
warn | init-lsb | /etc/rc.d/init.d/repmgr: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
| postgresql13-timescaledb-2.9.3-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/timescaledb-2.9.3.so /usr/lib64/pgsql/timescaledb-tsl-2.9.3.so /usr/lib64/pgsql/timescaledb.so conflict with the package postgresql15-timescaledb-2.9.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. |
| postgresql13-timescaledb-2.9.3-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| postgresql14-pg_partman-4.7.2-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql15-pg_partman-4.7.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. |
| postgresql14-pg_partman-4.7.2-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| postgresql14-repmgr-5.3.3-alt2.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql15-repmgr-5.3.3-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. |
| postgresql14-repmgr-5.3.3-alt2.x86_64 |
warn | init-lsb | /etc/rc.d/init.d/repmgr: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
| postgresql14-timescaledb-2.9.3-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/timescaledb-2.9.3.so /usr/lib64/pgsql/timescaledb-tsl-2.9.3.so /usr/lib64/pgsql/timescaledb.so conflict with the package postgresql13-timescaledb-2.9.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. |
| postgresql14-timescaledb-2.9.3-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| postgresql15-pg_partman-4.7.2-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql14-pg_partman-4.7.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. |
| postgresql15-pg_partman-4.7.2-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| postgresql15-repmgr-5.3.3-alt2.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql14-repmgr-5.3.3-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. nsider using alternatives. |
| postgresql15-repmgr-5.3.3-alt2.x86_64 |
warn | init-lsb | /etc/rc.d/init.d/repmgr: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
| postgresql15-timescaledb-2.9.3-alt1.x86_64 |
warn | rpm-filesystem-conflict-file-file | Files /usr/lib64/pgsql/timescaledb-2.9.3.so /usr/lib64/pgsql/timescaledb-tsl-2.9.3.so /usr/lib64/pgsql/timescaledb.so conflict with the package postgresql13-timescaledb-2.9.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. |
| postgresql15-timescaledb-2.9.3-alt1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| qt3-doc-html-3.3.8d-alt16.1.x86_64 |
info | arch-dep-package-has-big-usr-share | 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. |
| unbound-1.17.1-alt1.src |
warn | specfile-useradd-n | -n in useradd is compat option and can be removed any time. Use -N instead. |
| zabbix-java-gateway-6.0.14-alt2.noarch |
 fail | init-condrestart | /etc/rc.d/init.d/zabbix_java_gateway: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix. |