Repocop reports by acl

  packager rpm id test status message
@cpan perl-DBD-XBase-1.08-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/bin/dbfdump conflicts with the package libshape-1.4.1-alt3.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.
@cpan perl-HTML-Template-JIT-0.05-alt2.2.noarch missing-url info Missing Url: in a package.
@cpan perl-XML-SAX-1.02-alt1.noarch 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.
aris gnumeric-data-1.12.50-alt1.noarch 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.
ender perl-MIDI-0.83-alt1.noarch missing-url info Missing Url: in a package.
mithraen nginx-1.20.1-alt1.src specfile-useradd-n warn -n in useradd is compat option and can be removed any time. Use -N instead.
mithraen nginx-1.20.1-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/nginx: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
mithraen nginx-1.20.1-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.
naf ices-0.4-alt6.2.x86_64 sisyphus_check fail sisyphus_check failed: /ALT/Sisyphus/files/x86_64/RPMS/ices-0.4-alt6.2.x86_64.rpm: forbidden requires: python-base sisyphus_check: check-deps ERROR: package dependencies violation /ALT/Sisyphus/files/x86_64/RPMS/ices-0.4-alt6.2.x86_64.rpm: The use of such a license name is ambiguous: GPL
naf perl-Palm-ZText-0.1-alt1.1.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/share/man/man1/perlztxt.1.xz
naf perl-Palm-ZText-0.1-alt1.1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/man/man1/perlztxt.1.xz
naf perl-Text-Markdown-1.0.31-alt1.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/share/man/man1/Markdown.pl.1.xz
naf perl-Text-Markdown-1.0.31-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/man/man1/Markdown.pl.1.xz
rider ImageMagick-tools-6.9.12.19-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/compare conflicts with the package zennode-1.2.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.
rider collectd-5.12.0-alt2.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
rider freeswitch-daemon-1.10.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.
rider freeswitch-daemon-1.10.6-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
rider freeswitch-daemon-1.10.6-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/freeswitch: not systemd compatible: lsb init header missing and freeswitch.service is not present. See http://www.altlinux.org/Services_Policy for details.
rider freeswitch-daemon-1.10.6-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.
rider freeswitch-webui-1.10.6-alt1.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.
sem claws-mail-3.18.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.
shaba hivex-1.3.21-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 postgresql10-contrib-10.18-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql11-contrib-11.13-alt2.x86_64, for example, /usr/bin/pg_standby (26 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 postgresql12-contrib-12.8-alt2.x86_64, for example, /usr/bin/oid2name (36 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 postgresql13-contrib-13.4-alt2.x86_64, for example, /usr/bin/oid2name (72 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.
File /usr/lib64/pgsql/ltree_plpython3.so conflicts with the package postgresql13-python-13.4-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 postgresql9.6-contrib-9.6.23-alt2.x86_64, for example, /usr/bin/pg_archivecleanup (35 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 postgresql10-perl-10.18-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.13-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 postgresql12-perl-12.8-alt2.x86_64, for example, /usr/lib64/pgsql/plperl.so (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.
There are file conflicts with the package postgresql13-perl-13.4-alt2.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.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.23-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 postgresql10-python-10.18-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql11-python-11.13-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.
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql12-python-12.8-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.
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql13-python-13.4-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/lib64/pgsql/plpython3.so conflicts with the package postgresql9.6-python-9.6.23-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 postgresql10-server-10.18-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.
taf postgresql10-server-10.18-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
taf postgresql10-server-10.18-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql11-server-11.13-alt2.x86_64, for example, /usr/bin/initdb (26 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 postgresql12-server-12.8-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (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.
There are file conflicts with the package postgresql13-server-13.4-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (632 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.6-server-9.6.23-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (36 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 postgresql10-tcl-10.18-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.13-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 postgresql12-tcl-12.8-alt2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.
There are file conflicts with the package postgresql13-tcl-13.4-alt2.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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.23-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 postgresql11-contrib-11.13-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-contrib-10.18-alt2.x86_64, for example, /usr/bin/pg_standby (26 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 postgresql12-contrib-12.8-alt2.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 postgresql13-contrib-13.4-alt2.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.
File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.4-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 postgresql9.6-contrib-9.6.23-alt2.x86_64, for example, /usr/bin/pg_archivecleanup (48 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 postgresql11-perl-11.13-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.18-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 postgresql12-perl-12.8-alt2.x86_64, for example, /usr/share/pgsql/extension/plperl--1.0.sql (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.
Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql13-perl-13.4-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/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.23-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 postgresql11-python-11.13-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql10-python-10.18-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.
Files /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql12-python-12.8-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.
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql13-python-13.4-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/lib64/pgsql/plpython3.so conflicts with the package postgresql9.6-python-9.6.23-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 postgresql11-server-11.13-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.
taf postgresql11-server-11.13-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
taf postgresql11-server-11.13-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-server-10.18-alt2.x86_64, for example, /usr/bin/initdb (26 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 postgresql12-server-12.8-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (37 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 postgresql13-server-13.4-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (630 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.6-server-9.6.23-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (43 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 postgresql11-tcl-11.13-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.18-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 postgresql12-tcl-12.8-alt2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.
There are file conflicts with the package postgresql13-tcl-13.4-alt2.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.
File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql9.6-tcl-9.6.23-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-contrib-12.8-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-contrib-10.18-alt2.x86_64, for example, /usr/bin/oid2name (36 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 postgresql11-contrib-11.13-alt2.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 postgresql13-contrib-13.4-alt2.x86_64, for example, /usr/bin/pgbench (60 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.
File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.4-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 postgresql9.6-contrib-9.6.23-alt2.x86_64, for example, /usr/bin/oid2name (48 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-perl-12.8-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-perl-10.18-alt2.x86_64, for example, /usr/lib64/pgsql/plperl.so (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.
There are file conflicts with the package postgresql11-perl-11.13-alt2.x86_64, for example, /usr/share/pgsql/extension/plperl--1.0.sql (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.
Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql13-perl-13.4-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 postgresql9.6-perl-9.6.23-alt2.x86_64, for example, /usr/lib64/pgsql/plperl.so (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 postgresql12-python-12.8-alt2.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql10-python-10.18-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.
Files /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql11-python-11.13-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.
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql13-python-13.4-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.
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql9.6-python-9.6.23-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-server-12.8-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.
taf postgresql12-server-12.8-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
taf postgresql12-server-12.8-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-server-10.18-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (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.
There are file conflicts with the package postgresql11-server-11.13-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (37 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 postgresql13-server-13.4-alt2.x86_64, for example, /usr/bin/pg_rewind (616 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.6-server-9.6.23-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (47 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.8-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-tcl-10.18-alt2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.
There are file conflicts with the package postgresql11-tcl-11.13-alt2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.
Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql13-tcl-13.4-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 postgresql9.6-tcl-9.6.23-alt2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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 postgresql9.6-contrib-9.6.23-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-contrib-10.18-alt2.x86_64, for example, /usr/bin/pg_archivecleanup (35 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 postgresql11-contrib-11.13-alt2.x86_64, for example, /usr/bin/pg_archivecleanup (48 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 postgresql12-contrib-12.8-alt2.x86_64, for example, /usr/bin/oid2name (48 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 postgresql13-contrib-13.4-alt2.x86_64, for example, /usr/bin/oid2name (75 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 postgresql13-python-13.4-alt2.x86_64, for example, /usr/lib64/pgsql/hstore_plpython3.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.
taf postgresql9.6-perl-9.6.23-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.18-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/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.13-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 postgresql12-perl-12.8-alt2.x86_64, for example, /usr/lib64/pgsql/plperl.so (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.
There are file conflicts with the package postgresql13-perl-13.4-alt2.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.
taf postgresql9.6-python-9.6.23-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql10-python-10.18-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/lib64/pgsql/plpython3.so conflicts with the package postgresql11-python-11.13-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.
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql12-python-12.8-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.
Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql13-python-13.4-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 postgresql9.6-server-9.6.23-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.
taf postgresql9.6-server-9.6.23-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/postgresql-check-db-dir /etc/rc.d/init.d/postgresql
taf postgresql9.6-server-9.6.23-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-server-10.18-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (36 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 postgresql11-server-11.13-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (43 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 postgresql12-server-12.8-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (47 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 postgresql13-server-13.4-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (640 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 postgresql9.6-tcl-9.6.23-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.18-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/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.13-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 postgresql12-tcl-12.8-alt2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (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.
There are file conflicts with the package postgresql13-tcl-13.4-alt2.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.
viy libmapsdb-devel-0.17-alt2.x86_64 missing-url info Missing Url: in a package.
viy perl-Data-Array2ArrayMap-Hash-XSTree-0.15-alt1.x86_64 missing-url info Missing Url: in a package.
viy perl-Data-Array2ArrayMap-Hash-XSTree-debuginfo-0.15-alt1.x86_64 missing-url info Missing Url: in a package.
viy perl-Data-Array2ArrayMap-SDB-0.17-alt2.x86_64 missing-url info Missing Url: in a package.
viy perl-Data-Array2ArrayMap-SDB-debuginfo-0.17-alt2.x86_64 missing-url info Missing Url: in a package.
viy perl-Sys-CPUtime-0.10-alt4.2.x86_64 missing-url info Missing Url: in a package.
viy perl-Sys-CPUtime-debuginfo-0.10-alt4.2.x86_64 missing-url info Missing Url: in a package.

generated by repocop at Sat Sep 18 04:56:23 2021