Repocop reports for by-leader taf

  rpm id test status message
accel-ppp-1.12.0-alt4.1.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
accel-ppp-1.12.0-alt4.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
accel-ppp-1.12.0-alt4.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.
aspell-ispell-0.60.8-alt1.noarch alt-alternatives-master-slave-conflict fail slave alternative /usr/bin/spell is already registered as a master in package: enchant-1.6.0-alt3.qa1.x86_64
astra-4.4-alt8.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
bcunit-3.0.2-alt1.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/doc/BCUnit/BCUnit_doc.css
/usr/doc/BCUnit/error_handling.html
/usr/doc/BCUnit/fdl.html
/usr/doc/BCUnit/index.html
/usr/doc/BCUnit/introduction.html
/usr/doc/BCUnit/managing_tests.html
/usr/doc/BCUnit/running_tests.html
/usr/doc/BCUnit/test_registry.html
/usr/doc/BCUnit/writing_tests.html
bcunit-3.0.2-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/doc/BCUnit/BCUnit_doc.css
/usr/doc/BCUnit/error_handling.html
/usr/doc/BCUnit/fdl.html
/usr/doc/BCUnit/index.html
/usr/doc/BCUnit/introduction.html
/usr/doc/BCUnit/managing_tests.html
/usr/doc/BCUnit/running_tests.html
/usr/doc/BCUnit/test_registry.html
/usr/doc/BCUnit/writing_tests.html
bcunit-3.0.2-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
bitcoin-23.0-alt1.src specfile-url-is-dead warn Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
libmediastreamer-2.16.1-alt5.src specfile-url-is-dead warn Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
libmemcached-1.0.18-alt3.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
libnftnl-1.2.1-alt1.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
libortp-1.0.2-alt3.src specfile-url-is-dead warn Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is dead or discontinued and should be replaced by alive link (or link to archive.org as a last resort). See https://repology.org/repository/altsisyphus/problems
libortp-1.0.2-alt3.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
libpoco-devel-1.11.2-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/arc conflicts with the package arc-5.21p-alt1_16.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.
lighttpd-1.4.64-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.
lynx-2.8.9-alt1.pre.1.1.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/etc/X11/wmconfig/lynx
lynx-2.8.9-alt1.pre.1.1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/etc/X11/wmconfig/lynx
mongo-4.4.10-alt1.src specfile-useradd-n warn -n in useradd is compat option and can be removed any time. Use -N instead.
mongo-server-mongod-4.4.10-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.
mongo-server-mongod-4.4.10-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.
mongo-server-mongos-4.4.10-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.
mongo-server-mongos-4.4.10-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.
nftables-1.0.2-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.
poco-1.11.2-alt1.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
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.
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.
postgresql10-pg_partman-4.6.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.
postgresql10-pg_partman-4.6.2-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/share/pgsql/extension/pg_partman--4.6.2.sql conflicts with the package postgresql14-pg_partman-4.6.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
able, consider using alternatives.
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.
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.
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.
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.
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.
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.
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.
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.
postgresql11-pg_partman-4.6.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.
postgresql11-pg_partman-4.6.2-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 postgresql14-pg_partman-4.6.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
able, consider using alternatives.
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.
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.
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.
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.
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.
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.
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.
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.
postgresql12-pg_partman-4.6.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.
postgresql12-pg_partman-4.6.2-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 postgresql14-pg_partman-4.6.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
postgresql12-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.
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.
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.
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.
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.
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.
.
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.
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.
postgresql13-pg_partman-4.6.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.
postgresql13-pg_partman-4.6.2-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 postgresql14-pg_partman-4.6.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.
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.
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.
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.
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.
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.
postgresql13-timescaledb-2.6.1-alt1.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
postgresql13-timescaledb-2.6.1-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.
postgresql13-timescaledb-2.6.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/pgsql/timescaledb-2.6.1.so /usr/lib64/pgsql/timescaledb-tsl-2.6.1.so /usr/lib64/pgsql/timescaledb.so conflict with the package postgresql14-timescaledb-2.6.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.
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.
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.
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.
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.
.
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.
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.
postgresql14-pg_partman-4.6.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.
postgresql14-pg_partman-4.6.2-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 postgresql13-pg_partman-4.6.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
postgresql14-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.
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.
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.
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.
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.
postgresql14-timescaledb-2.6.1-alt1.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
postgresql14-timescaledb-2.6.1-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.
postgresql14-timescaledb-2.6.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/pgsql/timescaledb-2.6.1.so /usr/lib64/pgsql/timescaledb-tsl-2.6.1.so /usr/lib64/pgsql/timescaledb.so conflict with the package postgresql13-timescaledb-2.6.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.
zabbix-java-gateway-6.0.4-alt1.noarch 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.
zabbix34-agent-3.4.15-alt2.src beehive-log-unpackaged-files-found-i586 info warning: Installed (but unpackaged) file(s) found:
/usr/bin/zabbix_get
/usr/share/man/man1/zabbix_get.1.xz
zabbix34-agent-3.4.15-alt2.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/bin/zabbix_get
/usr/share/man/man1/zabbix_get.1.xz
zabbix34-agent-3.4.15-alt2.src specfile-url-permanent-https-redirect experimental Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems
Homepage link in URL is a permanent redirect to its HTTPS counterpart. Please, change URL protocol from http:// to https://. See https://repology.org/repository/altsisyphus/problems

generated by repocop at Wed May 18 05:32:19 2022