Repocop reports by acl

  packager rpm id test status message
oddity pgadmin3-1.23.0b-alt3.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-contrib-10.21-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/ltree_plpython3.so conflicts with the package postgresql14-python-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
dable, consider using alternatives.
taf postgresql10-perl-10.21-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-perl-14.3-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.
taf postgresql10-python-10.21-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 postgresql14-python-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
r, if conflicts are avoidable, consider using alternatives.
taf postgresql10-server-10.21-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 postgresql10-server-10.21-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-14.3-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (635 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-server-devel-10.21-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-devel-14.3-alt1.x86_64, for example, /usr/bin/pg_server_config (518 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.

alternatives.
taf postgresql10-tcl-10.21-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-tcl-14.3-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.
taf postgresql11-contrib-11.16-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql14-python-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
dable, consider using alternatives.
taf postgresql11-llvmjit-11.16-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-llvmjit-14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (779 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 postgresql11-perl-11.16-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-perl-14.3-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 postgresql11-python-11.16-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 postgresql14-python-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
consider using alternatives.
taf postgresql11-server-11.16-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 postgresql11-server-11.16-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-14.3-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 postgresql11-server-devel-11.16-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-devel-14.3-alt1.x86_64, for example, /usr/bin/pg_server_config (573 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.

alternatives.
taf postgresql11-tcl-11.16-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-tcl-14.3-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.
taf postgresql12-contrib-12.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-contrib-14.3-alt1.x86_64, for example, /usr/bin/oid2name (63 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-llvmjit-12.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-llvmjit-14.3-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.
s.
taf postgresql12-perl-12.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-perl-14.3-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-python-12.11-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 postgresql14-python-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
consider using alternatives.
consider using alternatives.
taf postgresql12-server-12.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 postgresql12-server-12.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-14.3-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (626 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-server-devel-12.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-devel-14.3-alt1.x86_64, for example, /usr/include/pgsql/server/access/amapi.h (462 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.11-alt1.x86_64 rpm-filesystem-conflict-file-file warn 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 postgresql14-tcl-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
taf postgresql13-contrib-13.7-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-contrib-14.3-alt1.x86_64, for example, /usr/bin/pgbench (25 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-llvmjit-13.7-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-llvmjit-14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (763 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 postgresql13-perl-13.7-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-perl-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
taf postgresql13-python-13.7-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql14-python-14.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
es.
oidable, consider using alternatives.
taf postgresql13-server-13.7-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.7-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-14.3-alt1.x86_64, for example, /usr/bin/initdb (22 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.
alternatives.
taf postgresql13-server-devel-13.7-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-server-devel-14.3-alt1.x86_64, for example, /usr/include/pgsql/server/access/amapi.h (357 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.7-alt1.x86_64 rpm-filesystem-conflict-file-file warn 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 postgresql12-tcl-12.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.
taf postgresql14-1C-contrib-14.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.7-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-1C-llvmjit-14.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-llvmjit-14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_selfuncs.bc (241 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-1C-server-14.3-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-contrib-14.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql13-contrib-13.7-alt1.x86_64, for example, /usr/bin/pgbench (25 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-llvmjit-14.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql14-1C-llvmjit-14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_selfuncs.bc (241 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-perl-14.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.7-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.
onflicts are avoidable, consider using alternatives.
taf postgresql14-python-14.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.7-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.
e avoidable, consider using alternatives.
taf postgresql14-server-14.3-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.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql13-server-13.7-alt1.x86_64, for example, /usr/bin/initdb (22 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.
alternatives.
taf postgresql14-server-devel-14.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql13-server-devel-13.7-alt1.x86_64, for example, /usr/include/pgsql/server/access/amapi.h (357 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.3-alt1.x86_64 rpm-filesystem-conflict-file-file warn 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 postgresql12-tcl-12.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.

generated by repocop at Tue May 17 05:28:15 2022