| |
packager |
rpm id |
test |
status |
message |
 |
rider |
getstream-20120411-alt4.x86_64 |
init-but-no-native-systemd |
info |
The package have SysV init script(s) but no native systemd files. |
|
taf |
accel-ppp-1.13.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. |
 |
taf |
aspell-ispell-0.60.8-alt2.noarch |
alt-alternatives-master-slave-conflict |
fail |
slave alternative /usr/bin/spell is already registered as a master in package: ispell-3.2.06-alt14.x86_64
64 |
 |
taf |
asterisk-20.7.0-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
asterisk-20.7.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. |
|
taf |
asterisk-20.7.0-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/asterisk: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
bacula13-13.0.4-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
bacula13-bat-13.0.4-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/bat.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). |
|
taf |
bacula13-bat-13.0.4-alt1.x86_64 |
freedesktop-desktop |
info |
desktop-file-validate utility printed the following message(s): /usr/share/applications/bat.desktop: hint: value "System;Utility;X-Red-Hat-Base;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu |
|
taf |
bacula13-client-13.0.4-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/bacula-fd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
bacula13-common-13.0.4-alt1.x86_64 |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
taf |
bacula13-common-13.0.4-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. |
|
taf |
bacula13-director-common-13.0.4-alt1.x86_64 |
big-changelog |
info |
Package contains big ChangeLog. Gzip it. |
|
taf |
bacula13-director-common-13.0.4-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/bacula-dir: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
bacula13-director-common-13.0.4-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/share/doc/bacula13-director-common-13.0.4/updatedb/update_mysql_tables_11_to_12: $ grep /tmp/ /usr/share/doc/bacula13-director-common-13.0.4/updatedb/update_mysql_tables_11_to_12 echo " " bindir=/usr/bin PATH="$bindir:$PATH" db_name=${db_name:-bacula} mysql $* ${db_name} "select VersionId from Version\G" >/tmp/$$ DBVERSION=`sed 's/^VersionId: \(.*\)$/\1/p' /tmp/$$` if [ $DBVERSION != 11 ] ; then echo " " echo "The existing database is version $DBVERSION !!" echo "This script can only update an existing version 11 database to version 12." echo "Error. Cannot upgrade this database." |
|
taf |
bacula13-director-mysql-13.0.4-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/share/bacula/scripts/update_mysql_tables: $ grep /tmp/ /usr/share/bacula/scripts/update_mysql_tables ARGS=$* getVersion() { mysql $ARGS ${db_name} "select VersionId from Version LIMIT 1\G" >/tmp/$$ DBVERSION=`sed 's/^VersionId: \(.*\)$/\1/p' /tmp/$$` } getVersion if [ "x$DBVERSION" = x ]; then |
|
taf |
bacula13-storage-13.0.4-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/bacula-sd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
bacula13-traymonitor-13.0.4-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/bacula-tray-monitor.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). |
|
taf |
bacula13-traymonitor-13.0.4-alt1.x86_64 |
freedesktop-desktop |
info |
desktop-file-validate utility printed the following message(s): /usr/share/applications/bacula-tray-monitor.desktop: hint: value "System;Utility;X-Red-Hat-Base;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu |
 |
taf |
bacula13-traymonitor-13.0.4-alt1.x86_64 |
iconsdir |
experimental |
Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. |
|
taf |
bcunit-5.2.62-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 |
|
taf |
libunbound-1.19.3-alt1.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
taf |
lighttpd-1.4.73-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/lighttpd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo4.2-4.2.25-alt2.1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
mongo4.2-server-mongod-4.2.25-alt2.1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongod: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo4.2-server-mongod-4.2.25-alt2.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. |
|
taf |
mongo4.2-server-mongos-4.2.25-alt2.1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongos: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo4.2-server-mongos-4.2.25-alt2.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. |
|
taf |
mongo4.4-4.4.29-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
mongo4.4-server-mongod-4.4.29-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongod: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo4.4-server-mongod-4.4.29-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. |
|
taf |
mongo4.4-server-mongos-4.4.29-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongos: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo4.4-server-mongos-4.4.29-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. |
|
taf |
mongo5.0-5.0.25-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
mongo5.0-server-mongod-5.0.25-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongod: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo5.0-server-mongod-5.0.25-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. |
|
taf |
mongo5.0-server-mongos-5.0.25-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongos: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo5.0-server-mongos-5.0.25-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. |
|
taf |
mongo6.0-6.0.14-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
mongo6.0-server-mongod-6.0.14-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongod: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo6.0-server-mongod-6.0.14-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. |
|
taf |
mongo6.0-server-mongos-6.0.14-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongos: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo6.0-server-mongos-6.0.14-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. |
|
taf |
mongo7.0-7.0.8-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
mongo7.0-server-mongod-7.0.8-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongod: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo7.0-server-mongod-7.0.8-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. |
|
taf |
mongo7.0-server-mongos-7.0.8-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/mongos: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
mongo7.0-server-mongos-7.0.8-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. |
|
taf |
nftables-1.0.9-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
taf |
postgresql12-contrib-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.x86_64, for example, /usr/bin/oid2name (70 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. |
|
taf |
postgresql12-iplike-2.3.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql16-iplike-2.3.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. |
|
taf |
postgresql12-llvmjit-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (799 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.
s. |
|
taf |
postgresql12-perl-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-perl-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/plperl.so (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.
licts are avoidable, consider using alternatives. |
|
taf |
postgresql12-pg_checksums-1.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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. |
|
taf |
postgresql12-pg_partman-4.7.4-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. |
|
taf |
postgresql12-pg_partman-4.7.4-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-pg_partman-5.1.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/src/pg_partman_bgw.index.bc (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. |
|
taf |
postgresql12-pg_repack-1.5.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/lib64/pgsql/bitcode/pg_repack/pgut/pgut-spi.bc /usr/lib64/pgsql/bitcode/pg_repack/repack.bc /usr/lib64/pgsql/pg_repack.so conflict with the package postgresql16-pg_repack-1.5.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.
s. |
|
taf |
postgresql12-python-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql16-python-16.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. |
|
taf |
postgresql12-server-12.18-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. |
|
taf |
postgresql12-server-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (633 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. |
|
taf |
postgresql12-tcl-12.18-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-tcl-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.
icts are avoidable, consider using alternatives. |
|
taf |
postgresql13-contrib-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.x86_64, for example, /usr/bin/pgbench (39 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.
|
|
taf |
postgresql13-iplike-2.3.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql16-iplike-2.3.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. |
|
taf |
postgresql13-llvmjit-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (804 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.
es.
s. |
|
taf |
postgresql13-perl-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.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.
ther. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql13-pg_checksums-1.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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. |
|
taf |
postgresql13-pg_partman-4.7.4-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. |
|
taf |
postgresql13-pg_partman-4.7.4-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-pg_partman-5.1.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/src/pg_partman_bgw.index.bc (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. |
|
taf |
postgresql13-pg_repack-1.5.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/lib64/pgsql/bitcode/pg_repack/pgut/pgut-spi.bc /usr/lib64/pgsql/bitcode/pg_repack/repack.bc /usr/lib64/pgsql/pg_repack.so conflict with the package postgresql16-pg_repack-1.5.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.
s. |
|
taf |
postgresql13-python-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql16-python-16.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.
ernatives. |
|
taf |
postgresql13-server-13.14-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. |
|
taf |
postgresql13-server-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (34 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. |
|
taf |
postgresql13-tcl-13.14-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql16-tcl-16.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.
her. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql13-timescaledb-2.14.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. |
|
taf |
postgresql13-timescaledb-2.14.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
Files /usr/lib64/pgsql/timescaledb-2.14.2.so /usr/lib64/pgsql/timescaledb-tsl-2.14.2.so conflict with the package postgresql16-timescaledb-2.14.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. |
|
taf |
postgresql14-contrib-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.x86_64, for example, /usr/bin/pgbench (33 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.
|
|
taf |
postgresql14-iplike-2.3.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql16-iplike-2.3.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. |
|
taf |
postgresql14-llvmjit-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (783 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.
es.
s. |
|
taf |
postgresql14-perl-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql14-pg_checksums-1.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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. |
|
taf |
postgresql14-pg_partman-5.1.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. |
|
taf |
postgresql14-pg_partman-5.1.0-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
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 postgresql16-pg_partman-5.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.
es. |
|
taf |
postgresql14-pg_repack-1.5.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql16-pg_repack-1.5.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.
s.
plicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql14-python-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.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.
idable, consider using alternatives.
ernatives. |
|
taf |
postgresql14-server-14.11-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. |
|
taf |
postgresql14-server-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (33 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. |
|
taf |
postgresql14-tcl-14.11-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql16-tcl-16.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.
her. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql14-timescaledb-2.14.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. |
|
taf |
postgresql14-timescaledb-2.14.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/timescaledb-2.14.2.so conflicts with the package postgresql16-timescaledb-2.14.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.
re avoidable, consider using alternatives. |
|
taf |
postgresql15-15.6-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. |
|
taf |
postgresql15-1C-15.5-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. |
|
taf |
postgresql15-1C-contrib-15.5-alt4.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.14-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. |
|
taf |
postgresql15-1C-llvmjit-15.5-alt4.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (784 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.
es. |
|
taf |
postgresql15-1C-pg_checksums-1.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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. |
|
taf |
postgresql15-1C-pg_repack-1.5.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql16-pg_repack-1.5.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.
explicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql15-1C-server-15.5-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. |
|
taf |
postgresql15-contrib-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-contrib-16.2-alt1.x86_64, for example, /usr/bin/pgbench (29 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.
|
|
taf |
postgresql15-iplike-2.3.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql16-iplike-2.3.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. |
|
taf |
postgresql15-llvmjit-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-llvmjit-16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 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.
tives. |
|
taf |
postgresql15-perl-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql15-pg_checksums-1.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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. |
|
taf |
postgresql15-pg_partman-5.1.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. |
|
taf |
postgresql15-pg_partman-5.1.0-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql16-pg_partman-5.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.
able, consider using alternatives.
es. |
|
taf |
postgresql15-pg_repack-1.5.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql16-pg_repack-1.5.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.
s.
plicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql15-python-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.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.
idable, consider using alternatives.
ernatives. |
|
taf |
postgresql15-server-15.6-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. |
|
taf |
postgresql15-server-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql16-server-16.2-alt1.x86_64, for example, /usr/bin/initdb (27 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.
lternatives. |
|
taf |
postgresql15-tcl-15.6-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.11-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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql15-timescaledb-2.14.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. |
|
taf |
postgresql15-timescaledb-2.14.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/timescaledb-2.14.2.so conflicts with the package postgresql16-timescaledb-2.14.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.
re avoidable, consider using alternatives. |
|
taf |
postgresql16-16.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. |
|
taf |
postgresql16-contrib-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-contrib-15.6-alt1.x86_64, for example, /usr/bin/pgbench (29 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.
|
|
taf |
postgresql16-iplike-2.3.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql15-iplike-2.3.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. |
|
taf |
postgresql16-llvmjit-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-llvmjit-15.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 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.
s. |
|
taf |
postgresql16-perl-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.6-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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql16-pg_checksums-1.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/bin/pg_checksums_ext conflicts with the package postgresql15-pg_checksums-1.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.
s. |
|
taf |
postgresql16-pg_partman-5.1.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. |
|
taf |
postgresql16-pg_partman-5.1.0-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql15-pg_partman-5.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.
able, consider using alternatives.
es. |
|
taf |
postgresql16-pg_repack-1.5.0-alt2.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql15-pg_repack-1.5.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.
s.
plicit conflicts, or, if conflicts are avoidable, consider using alternatives. |
|
taf |
postgresql16-python-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.6-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.
dable, consider using alternatives.
ernatives. |
|
taf |
postgresql16-repmgr-5.4.1-alt1.x86_64 |
init-lsb |
warn |
/etc/rc.d/init.d/repmgr: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. |
|
taf |
postgresql16-repmgr-5.4.1-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-repmgr-5.4.1-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. |
|
taf |
postgresql16-server-16.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. |
|
taf |
postgresql16-server-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-server-15.6-alt1.x86_64, for example, /usr/bin/initdb (27 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.
lternatives. |
|
taf |
postgresql16-tcl-16.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.11-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.
nflicts are avoidable, consider using alternatives. |
|
taf |
postgresql16-tds_fdw-2.0.3-alt3.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package postgresql15-tds_fdw-2.0.3-alt3.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (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. |
|
taf |
postgresql16-timescaledb-2.14.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. |
|
taf |
postgresql16-timescaledb-2.14.2-alt1.x86_64 |
rpm-filesystem-conflict-file-file |
warn |
File /usr/lib64/pgsql/timescaledb-2.14.2.so conflicts with the package postgresql15-timescaledb-2.14.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.
re avoidable, consider using alternatives. |
|
taf |
unbound-1.19.3-alt1.src |
specfile-useradd-n |
warn |
-n in useradd is compat option and can be removed any time. Use -N instead. |
|
taf |
zabbix-java-gateway-6.0.28-alt2.x86_64 |
init-condrestart |
fail |
/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. |