Sisyphus repository
Last update: 11 december 2017 | SRPMs: 18127 | Visits: 10551187
en ru br
Maintainer: Alexei Takaseev

 Information   Packages   Bugs and FR  Repocop 

Repocop messages:

package status test message
accel-ppp-1.11.2-alt4.x86_64
info
init-but-no-native-systemd The package have SysV init script(s) but no native systemd files.
accel-ppp-1.11.2-alt4.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-alt2.x86_64
info
init-but-no-native-systemd The package have SysV init script(s) but no native systemd files.
libecpg6.8-1C-debuginfo-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.10-debuginfo-10.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. value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.5-debuginfo-9.3.20-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. value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.6-debuginfo-9.4.15-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. value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.d... [the rest of the message is skipped]
libpq5.9-1C-debuginfo-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.10-debuginfo-10.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. value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.6-debuginfo-9.3.20-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. value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.7-debuginfo-9.4.15-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. value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is differ... [the rest of the message is skipped]
lighttpd-1.4.47-alt2.x86_64
warn
init-lsb /etc/rc.d/init.d/lighttpd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
linphone-gui-3.12.0-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.
linphone-tester-3.12.0-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.
openfire-4.1.6-alt2.noarch
info
init-but-no-native-systemd The package have SysV init script(s) but no native systemd files.
postgresql9.6-1C-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package postgre-etersoft9.6-9.6.1.2-alt2.x86_64, for example, /usr/bin/createdb (10 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. Files /usr/bin/pg_isready /usr/bin/pg_xlogdump conflict with the package postgre-etersoft9.6-server-9.6.1.2-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. File /usr/bin/pg_xlogdump conflicts with the package postgresql9.3-contrib-9.3.20-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. File /usr/bin/pg_xlogdump conflicts with the package postgresql9.4-contrib-9.4.15-alt1.x86_64. Moreover, the packages have no explicit conflicts with e... [the rest of the message is skipped]
postgresql9.6-1C-contrib-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-file-file File /usr/bin/pg_standby conflicts with the package postgre-etersoft9.6-server-9.6.1.2-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. There are file conflicts with the package postgresql10-contrib-10.1-alt1.x86_64, for example, /usr/bin/pg_archivecleanup (28 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. There are file conflicts with the package postgresql9.3-contrib-9.3.20-alt1.x86_64, for example, /usr/bin/oid2name (28 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. There are file conflicts with the package postgresql9.4-contrib-9.4.15-alt1.x86_64, for example, /usr/bin/oid2name ... [the rest of the message is skipped]
postgresql9.6-1C-perl-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-file-file File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.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. File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.3-perl-9.3.20-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. File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.4-perl-9.4.15-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. File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.10-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are... [the rest of the message is skipped]
postgresql9.6-1C-python-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-file-file File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.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. File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.3-python-9.3.20-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. File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.4-python-9.4.15-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. File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.10-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, ... [the rest of the message is skipped]
postgresql9.6-1C-server-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package postgre-etersoft9.6-server-9.6.1.2-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (8 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.
postgresql9.6-1C-server-9.6.6-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.
postgresql9.6-1C-server-9.6.6-alt1.x86_64
experimental
checkbashisms checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
postgresql9.6-1C-tcl-9.6.6-alt1.x86_64
warn
rpm-filesystem-conflict-file-file File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.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. Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.3-tcl-9.3.20-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. File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.4-tcl-9.4.15-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. File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.5-tcl-9.5.10-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add ex... [the rest of the message is skipped]
zabbix-java-gateway-3.4.4-alt1.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.
zabbix-server-mysql-3.4.4-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.
zabbix-server-pgsql-3.4.4-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.
 
design & coding: Vladimir Lettiev aka crux © 2004-2005, Andrew Avramenko aka liks © 2007-2008
current maintainer: Michael Shigorin