accel-ppp-1.13.0-alt3.x86_64	file-in-usr-marked-as-conffile	warn	Files below <tt>/usr</tt> may not be marked as conffiles, since;  <tt>/usr</tt> might be mounted read-only and thus, the local system;  administrator would not have a chance to modify this configuration;  file.; ; 
accel-ppp-1.13.0-alt3.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/accel-ppp-1.13.0-alt3.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/accel-ppp.conf sisyphus_check: check-fhs ERROR: FHS violation; 
accel-ppp-1.13.0-alt3.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-alt2.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.qa3.x86_64; 
aspell-ru-0.99f7-alt1.x86_64	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package aspell-ru-rk-1.1-alt8.x86_64, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of aspell-ru-rk-1.1-alt8.x86_64 to remove Obsoletes: tag.; e Obsoletes: tag.; 
bacula15-15.0.3-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
bacula15-bat-15.0.3-alt1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/bat.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).; 
bacula15-bat-15.0.3-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/bat.desktop: hint: value "System;Utility;X-Red-Hat-Base;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
bacula15-client-15.0.3-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/bacula-fd: not systemd compatible: lsb init header missing and bacula-fd.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
bacula15-common-15.0.3-alt1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
bacula15-common-15.0.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/bacula15-common-15.0.3-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/bacula.conf sisyphus_check: check-fhs ERROR: FHS violation; 
bacula15-common-15.0.3-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.; 
bacula15-director-common-15.0.3-alt1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
bacula15-director-common-15.0.3-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/bacula-dir: not systemd compatible: lsb init header missing and bacula-dir.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
bacula15-director-common-15.0.3-alt1.x86_64	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/doc/bacula15-director-common-15.0.3/updatedb/update_mysql_tables_11_to_12: $ grep /tmp/ /usr/share/doc/bacula15-director-common-15.0.3/updatedb/update_mysql_tables_11_to_12 echo " " bindir=/usr/bin PATH="$bindir:$PATH" db_name=${db_name:-bacula} mysql $* ${db_name} "select VersionId from Version\G" >/tmp/$$ DBVERSION=`sed 's/^VersionId: \(.*\)$/\1/p' /tmp/$$` if [ $DBVERSION != 11 ] ; then echo " " echo "The existing database is version $DBVERSION !!" echo "This script can only update an existing version 11 database to version 12." echo "Error. Cannot upgrade this database."; 
bacula15-director-mysql-15.0.3-alt1.x86_64	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/bacula/scripts/update_mysql_tables: $ grep /tmp/ /usr/share/bacula/scripts/update_mysql_tables ARGS=$* getVersion() { mysql $ARGS ${db_name} "select VersionId from Version LIMIT 1\G" >/tmp/$$ DBVERSION=`sed 's/^VersionId: \(.*\)$/\1/p' /tmp/$$` } getVersion if [ "x$DBVERSION" = x ]; then; 
bacula15-storage-15.0.3-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/bacula-sd: not systemd compatible: lsb init header missing and bacula-sd.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
bacula15-traymonitor-15.0.3-alt1.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/bacula-tray-monitor.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).; 
bacula15-traymonitor-15.0.3-alt1.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/bacula-tray-monitor.desktop: hint: value "System;Utility;X-Red-Hat-Base;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; 
bacula15-traymonitor-15.0.3-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
libecpg6-13-debuginfo-13.23-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; ; s.; 
libecpg6-14-debuginfo-14.20-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; ; s.; 
libecpg6-15-debuginfo-15.15-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; ; s.; 
libecpg6-16-debuginfo-16.11-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; ; s.; 
libecpg6-17-1C-debuginfo-17.7-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; ; s.; ; 
libecpg6-17-debuginfo-17.7-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; ; s.; ; 
libecpg6-18-debuginfo-18.1-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.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.; s.; ; s.; 
libpq5-13-devel-13.23-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.13. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-13-devel-13.23-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
libpq5-13-devel-debuginfo-13.23-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.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.; s.; 
libpq5-13-devel-static-13.23-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; 
libpq5-14-devel-14.20-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.14. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-14-devel-14.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
libpq5-14-devel-debuginfo-14.20-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.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.; s.; 
libpq5-14-devel-static-14.20-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; 
libpq5-15-devel-15.15-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.15. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-15-devel-15.15-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
libpq5-15-devel-debuginfo-15.15-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.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.; s.; 
libpq5-15-devel-static-15.15-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; 
libpq5-16-devel-16.11-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.16. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-16-devel-16.11-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
libpq5-16-devel-debuginfo-16.11-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.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.; s.; 
libpq5-16-devel-static-16.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; 
libpq5-17-1C-devel-17.7-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.17. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-17-1C-devel-17.7-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
libpq5-17-1C-devel-debuginfo-17.7-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-16-devel-debuginfo-16.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.; 
libpq5-17-1C-devel-static-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.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.; ; 
libpq5-17-devel-17.7-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.17. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-17-devel-17.7-alt1.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
libpq5-17-devel-debuginfo-17.7-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-16-devel-debuginfo-16.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.; 
libpq5-17-devel-static-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-18.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; 
libpq5-18-devel-static-18.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-17-devel-static-17.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.; s.; 
libunbound-1.24.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
lighttpd-1.4.82-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/lighttpd: not systemd compatible: lsb init header missing and lighttpd.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
lighttpd-1.4.82-alt1.x86_64	systemd-check-socket-name	experimental	in lighttpd-1.4.82-alt1.x86_64: there is a socket lighttpd-http-ipv4.socket but no service lighttpd-http-ipv4.service. Ask ildar@ why it is not right.; in lighttpd-1.4.82-alt1.x86_64: there is a socket lighttpd-http-ipv6.socket but no service lighttpd-http-ipv6.service. Ask ildar@ why it is not right.; in lighttpd-1.4.82-alt1.x86_64: there is a socket lighttpd-https-ipv4.socket but no service lighttpd-https-ipv4.service. Ask ildar@ why it is not right.; in lighttpd-1.4.82-alt1.x86_64: there is a socket lighttpd-https-ipv6.socket but no service lighttpd-https-ipv6.service. Ask ildar@ why it is not right.; 
mongo5.0-5.0.31-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
mongo5.0-server-mongod-5.0.31-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongod: not systemd compatible: lsb init header missing and mongod.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo5.0-server-mongod-5.0.31-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo5.0-server-mongod-5.0.31-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongod.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo5.0-server-mongod-5.0.31-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.; 
mongo5.0-server-mongos-5.0.31-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongos: not systemd compatible: lsb init header missing and mongos.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo5.0-server-mongos-5.0.31-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo5.0-server-mongos-5.0.31-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongos.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo5.0-server-mongos-5.0.31-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.; 
mongo6.0-6.0.26-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
mongo6.0-server-mongod-6.0.26-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongod: not systemd compatible: lsb init header missing and mongod.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo6.0-server-mongod-6.0.26-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo6.0-server-mongod-6.0.26-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongod.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo6.0-server-mongod-6.0.26-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.; 
mongo6.0-server-mongos-6.0.26-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongos: not systemd compatible: lsb init header missing and mongos.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo6.0-server-mongos-6.0.26-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo6.0-server-mongos-6.0.26-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongos.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo6.0-server-mongos-6.0.26-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.; 
mongo7.0-7.0.26-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
mongo7.0-server-mongod-7.0.26-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongod: not systemd compatible: lsb init header missing and mongod.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo7.0-server-mongod-7.0.26-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo7.0-server-mongod-7.0.26-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongod.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo7.0-server-mongod-7.0.26-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.; 
mongo7.0-server-mongos-7.0.26-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongos: not systemd compatible: lsb init header missing and mongos.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo7.0-server-mongos-7.0.26-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo7.0-server-mongos-7.0.26-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongos.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo7.0-server-mongos-7.0.26-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.; 
mongo8.0-8.0.12-alt2.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
mongo8.0-server-mongod-8.0.12-alt2.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongod: not systemd compatible: lsb init header missing and mongod.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo8.0-server-mongod-8.0.12-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo8.0-server-mongod-8.0.12-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongod.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo8.0-server-mongod-8.0.12-alt2.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.; 
mongo8.0-server-mongos-8.0.12-alt2.x86_64	init-lsb	fail	/etc/rc.d/init.d/mongos: not systemd compatible: lsb init header missing and mongos.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
mongo8.0-server-mongos-8.0.12-alt2.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/mongo8.0-server-mongos-8.0.12-alt2.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/mongos.conf sisyphus_check: check-fhs ERROR: FHS violation; 
mongo8.0-server-mongos-8.0.12-alt2.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.1.5-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
postgresql13-contrib-13.23-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-contrib-18.1-alt1.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.; natives.; 
postgresql13-credcheck-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql18-credcheck-4.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.; s.; 
postgresql13-llvmjit-13.23-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (818 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-orafce-4.16.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-orafce-4.16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (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.; 
postgresql13-perl-13.23-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-18.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.; ; 
postgresql13-pg-auto-failover-2.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/bin/pg_autoctl (15 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.; consider using alternatives.; 
postgresql13-pg_checksums-1.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pg_checksums_ext conflicts with the package postgresql18-pg_checksums-1.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.; s.; 
postgresql13-pg_cron-1.6.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_cron-1.6.7-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_cron.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; f conflicts are avoidable, consider using alternatives.; 
postgresql13-pg_hint_plan-1.3.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_hint_plan-1.8.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_hint_plan.index.bc (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.; s.; 
postgresql13-pg_partman-4.7.4-alt1.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
postgresql13-pg_partman-4.7.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_partman-5.3.1-alt1.x86_64, for example, /usr/bin/check_unique_constraint.py (87 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-pg_repack-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pg_repack/pgut/pgut-spi.bc /usr/lib64/pgsql/bitcode/pg_repack/repack.bc /usr/lib64/pgsql/pg_repack.so conflict with the package postgresql18-pg_repack-1.5.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.; s.; 
postgresql13-pgaudit-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgaudit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgaudit.index.bc (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.; s.; ; ng alternatives.; es.; 
postgresql13-pgpool-II-4.6.4-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/pgpool: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
postgresql13-pgpool-II-4.6.4-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/pgpool: not systemd compatible: lsb init header missing and pgpool.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql13-pgpool-II-4.6.4-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql13-pgpool-II-4.6.4-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pgpool.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql13-pgvector-0.8.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgvector-0.8.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/vector.index.bc (20 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-plv8-3.2.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-plv8-3.2.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/plv8-3.2.4.index.bc (7 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-python-13.23-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-python-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_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.; 
postgresql13-rum-1.3.14-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-rum-1.3.14-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/rum.index.bc (16 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-server-13.23-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.23-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-server-18.1-alt1.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.; ; 
postgresql13-tcl-13.23-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.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.; ; 
postgresql13-timescaledb-2.15.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.; 
postgresql13-timescaledb-2.15.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/timescaledb.so /usr/share/pgsql/extension/timescaledb.control conflict with the package postgresql17-timescaledb-2.22.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-contrib-14.20-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-contrib-18.1-alt1.x86_64, for example, /usr/bin/oid2name (46 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.; natives.; 
postgresql14-credcheck-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql18-credcheck-4.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.; s.; 
postgresql14-llvmjit-14.20-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (805 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.; .; 
postgresql14-orafce-4.16.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-orafce-4.16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (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.; 
postgresql14-perl-14.20-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-18.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-pg-auto-failover-2.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/bin/pg_autoctl (15 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.; consider using alternatives.; 
postgresql14-pg_checksums-1.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pg_checksums_ext conflicts with the package postgresql18-pg_checksums-1.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.; s.; 
postgresql14-pg_cron-1.6.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_cron-1.6.7-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_cron.index.bc (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.; s.; es.; nflicts are avoidable, consider using alternatives.; 
postgresql14-pg_hint_plan-1.4.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_hint_plan-1.8.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_hint_plan.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; e, consider using alternatives.; 
postgresql14-pg_partman-5.3.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-pg_partman-5.3.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw.index.bc /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql18-pg_partman-5.3.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-pg_repack-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql18-pg_repack-1.5.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.; s.; plicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql14-pgauditlogtofile-1.7.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgauditlogtofile-1.7.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (9 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.; 
postgresql14-pgpool-II-4.6.4-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/pgpool: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
postgresql14-pgpool-II-4.6.4-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/pgpool: not systemd compatible: lsb init header missing and pgpool.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql14-pgpool-II-4.6.4-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql14-pgpool-II-4.6.4-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pgpool.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql14-pgvector-0.8.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgvector-0.8.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/vector.index.bc (20 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; tives.; 
postgresql14-plv8-3.2.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-plv8-3.2.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/plv8-3.2.4.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql14-python-14.20-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-python-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_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.; 
postgresql14-rum-1.3.14-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-rum-1.3.14-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/rum.index.bc (14 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-server-14.20-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.20-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-server-18.1-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (38 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.20-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.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-timescaledb-2.19.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-timescaledb-2.19.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/timescaledb.so conflicts with the package postgresql17-timescaledb-2.22.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.; ts are avoidable, consider using alternatives.; 
postgresql15-15.15-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.; 
postgresql15-contrib-15.15-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-contrib-18.1-alt1.x86_64, for example, /usr/bin/oid2name (41 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.; natives.; 
postgresql15-credcheck-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql18-credcheck-4.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.; s.; 
postgresql15-llvmjit-15.15-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (824 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.; .; 
postgresql15-orafce-4.16.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-orafce-4.16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (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.; 
postgresql15-perl-15.15-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-18.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.; ; 
postgresql15-pg_checksums-1.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pg_checksums_ext conflicts with the package postgresql18-pg_checksums-1.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.; s.; 
postgresql15-pg_cron-1.6.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_cron-1.6.7-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_cron.index.bc (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.; s.; es.; nflicts are avoidable, consider using alternatives.; 
postgresql15-pg_hint_plan-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_hint_plan-1.8.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_hint_plan.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; e, consider using alternatives.; 
postgresql15-pg_partman-5.3.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.; 
postgresql15-pg_partman-5.3.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw.index.bc /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflict with the package postgresql18-pg_partman-5.3.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.; 
postgresql15-pg_repack-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql18-pg_repack-1.5.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.; s.; plicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql15-pgauditlogtofile-1.7.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgauditlogtofile-1.7.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (7 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.; atives.; s.; voidable, consider using alternatives.; 
postgresql15-pgpool-II-4.6.4-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/pgpool: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
postgresql15-pgpool-II-4.6.4-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/pgpool: not systemd compatible: lsb init header missing and pgpool.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql15-pgpool-II-4.6.4-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql15-pgpool-II-4.6.4-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pgpool.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql15-pgvector-0.8.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgvector-0.8.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/vector.index.bc (19 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; tives.; 
postgresql15-plv8-3.2.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-plv8-3.2.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/plv8-3.2.4.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql15-python-15.15-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-python-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_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.; 
postgresql15-rum-1.3.14-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-rum-1.3.14-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/rum.index.bc (13 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.; 
postgresql15-server-15.15-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.; 
postgresql15-server-15.15-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-server-18.1-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (38 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.; ; 
postgresql15-tcl-15.15-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.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.; ; 
postgresql15-timescaledb-2.22.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.; 
postgresql15-timescaledb-2.22.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/timescaledb-2.22.1.so /usr/lib64/pgsql/timescaledb-invalidations-2.22.1.so /usr/lib64/pgsql/timescaledb-tsl-2.22.1.so conflict with the package postgresql17-timescaledb-2.22.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.; 
postgresql16-16.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.; 
postgresql16-contrib-16.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-contrib-18.1-alt1.x86_64, for example, /usr/bin/oid2name (33 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; natives.; 
postgresql16-credcheck-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts with the package postgresql18-credcheck-4.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.; s.; onflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql16-llvmjit-16.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (757 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.; 
postgresql16-orafce-4.16.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-orafce-4.16.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce/alert.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.;  consider using alternatives.; 
postgresql16-perl-16.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.15-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql16-pg-auto-failover-2.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/bin/pg_autoctl (11 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.; 
postgresql16-pg_checksums-1.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pg_checksums_ext conflicts with the package postgresql18-pg_checksums-1.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.; s.; 
postgresql16-pg_cron-1.6.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc conflict with the package postgresql18-pg_cron-1.6.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.; 
postgresql16-pg_hint_plan-1.6.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_hint_plan-1.8.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_hint_plan.index.bc (8 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; e, consider using alternatives.; 
postgresql16-pg_partman-5.3.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.; 
postgresql16-pg_partman-5.3.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw.index.bc /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflict with the package postgresql18-pg_partman-5.3.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.; 
postgresql16-pg_repack-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql18-pg_repack-1.5.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.; s.; plicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql16-pgaudit-16.1-alt0.rc1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql18-pgaudit-18.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; 
postgresql16-pgauditlogtofile-1.7.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgauditlogtofile-1.7.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; es.; s.; re avoidable, consider using alternatives.; 
postgresql16-pgpool-II-4.6.4-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/pgpool: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
postgresql16-pgpool-II-4.6.4-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/pgpool: not systemd compatible: lsb init header missing and pgpool.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql16-pgpool-II-4.6.4-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql16-pgpool-II-4.6.4-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pgpool.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql16-pgvector-0.8.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgvector-0.8.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/vector.index.bc (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; .; 
postgresql16-plv8-3.2.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-plv8-3.2.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/plv8-3.2.4/plv8.bc (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.; ; 
postgresql16-python-16.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-python-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_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.; 
postgresql16-repmgr-5.5.0-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql16-repmgr-5.5.0-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql18-repmgr-5.5.0-alt4.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.; g alternatives.; 
postgresql16-repmgr-5.5.0-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql16-repmgr-5.5.0-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql16-rum-1.3.14-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-rum-1.3.14-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/rum/src/rumbulk.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql16-server-16.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.; 
postgresql16-server-16.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-server-18.1-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (32 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.; ; 
postgresql16-tcl-16.11-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.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.; ; 
postgresql16-tds_fdw-2.0.5-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.bc /usr/lib64/pgsql/bitcode/tds_fdw/src/tds_fdw.bc /usr/lib64/pgsql/tds_fdw.so conflict with the package postgresql17-tds_fdw-2.0.5-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.; 
postgresql16-timescaledb-2.22.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.; 
postgresql16-timescaledb-2.22.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/timescaledb-2.22.1.so /usr/lib64/pgsql/timescaledb-tsl-2.22.1.so conflict with the package postgresql17-timescaledb-2.22.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.; onflicts are avoidable, consider using alternatives.; 
postgresql17-17.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.; 
postgresql17-1C-17.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.; 
postgresql17-1C-contrib-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/share/pgsql/extension/hstore_plpython3u--1.0.sql /usr/share/pgsql/extension/ltree_plpython3u--1.0.sql conflict with the package postgresql18-python-18.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.; 
postgresql17-1C-credcheck-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts with the package postgresql18-credcheck-4.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.; t conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-1C-llvmjit-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (677 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.; 
postgresql17-1C-pg-auto-failover-2.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover/formation_metadata.bc (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-1C-pg_checksums-1.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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.; 
postgresql17-1C-pg_cron-1.6.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc conflict with the package postgresql18-pg_cron-1.6.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.; 
postgresql17-1C-pg_hint_plan-1.7.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_hint_plan-1.8.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_hint_plan.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; ; 
postgresql17-1C-pg_repack-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql18-pg_repack-1.5.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.;  explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-1C-pgaudit-17.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflict with the package postgresql18-pgaudit-18.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; e, consider using alternatives.; 
postgresql17-1C-pgauditlogtofile-1.7.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgauditlogtofile-1.7.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; es.; es.; 
postgresql17-1C-repmgr-5.5.0-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql17-1C-repmgr-5.5.0-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql18-repmgr-5.5.0-alt4.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.; g alternatives.; 
postgresql17-1C-repmgr-5.5.0-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql17-1C-repmgr-5.5.0-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql17-1C-server-17.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.; 
postgresql17-contrib-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-contrib-18.1-alt1.x86_64, for example, /usr/bin/oid2name (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.; rnatives.; 
postgresql17-credcheck-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts with the package postgresql18-credcheck-4.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.; s.; onflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-llvmjit-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (669 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.; ives.; 
postgresql17-orafce-4.16.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/orafce/dbms_sql.bc /usr/lib64/pgsql/bitcode/orafce/magic.bc /usr/lib64/pgsql/bitcode/orafce/replace_empty_string.bc conflict with the package postgresql18-orafce-4.16.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-perl-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.15-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-pg-auto-failover-2.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-1C-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover/formation_metadata.bc (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-pg_checksums-1.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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.; 
postgresql17-pg_cron-1.6.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc conflict with the package postgresql18-pg_cron-1.6.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.; 
postgresql17-pg_hint_plan-1.7.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pg_hint_plan-1.8.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_hint_plan.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; ; 
postgresql17-pg_partman-5.3.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.; 
postgresql17-pg_partman-5.3.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw.index.bc /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflict with the package postgresql18-pg_partman-5.3.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.; 
postgresql17-pg_repack-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql18-pg_repack-1.5.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.;  explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-pgaudit-17.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflict with the package postgresql18-pgaudit-18.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; e, consider using alternatives.; 
postgresql17-pgauditlogtofile-1.7.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgauditlogtofile-1.7.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (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.; es.; es.; 
postgresql17-pgpool-II-4.6.4-alt1.x86_64	init-condrestart	fail	/etc/rc.d/init.d/pgpool: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
postgresql17-pgpool-II-4.6.4-alt1.x86_64	init-lsb	fail	/etc/rc.d/init.d/pgpool: not systemd compatible: lsb init header missing and pgpool.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql17-pgpool-II-4.6.4-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql17-pgpool-II-4.6.4-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pgpool.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql17-pgvector-0.8.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-pgvector-0.8.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/vector.index.bc (12 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.; .; 
postgresql17-plv8-3.2.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/plv8-3.2.4/plv8.bc /usr/lib64/pgsql/bitcode/plv8-3.2.4/plv8_type.bc /usr/lib64/pgsql/plv8-3.2.4.so conflict with the package postgresql18-plv8-3.2.4-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.; 
postgresql17-python-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-python-18.1-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_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.; 
postgresql17-repmgr-5.5.0-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql17-repmgr-5.5.0-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql18-repmgr-5.5.0-alt4.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.; g alternatives.; 
postgresql17-repmgr-5.5.0-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql17-repmgr-5.5.0-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql17-rum-1.3.14-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql16-rum-1.3.14-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/rum/src/rumbulk.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql17-server-17.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.; 
postgresql17-server-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-server-18.1-alt1.x86_64, for example, /usr/bin/initdb (27 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; lternatives.; 
postgresql17-tcl-17.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-18.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.; ; 
postgresql17-tds_fdw-2.0.5-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.bc /usr/lib64/pgsql/bitcode/tds_fdw/src/tds_fdw.bc /usr/lib64/pgsql/tds_fdw.so conflict with the package postgresql16-tds_fdw-2.0.5-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.; 
postgresql17-timescaledb-2.22.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.; 
postgresql17-timescaledb-2.22.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/timescaledb-2.22.1.so /usr/lib64/pgsql/timescaledb-tsl-2.22.1.so conflict with the package postgresql16-timescaledb-2.22.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.; onflicts are avoidable, consider using alternatives.; 
postgresql18-18.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.; 
postgresql18-contrib-18.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-contrib-17.7-alt1.x86_64, for example, /usr/bin/oid2name (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.; ; 
postgresql18-credcheck-4.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts with the package postgresql17-credcheck-4.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.; s.; onflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql18-llvmjit-18.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-llvmjit-17.7-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (669 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.; 
postgresql18-orafce-4.16.2-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/orafce/dbms_sql.bc /usr/lib64/pgsql/bitcode/orafce/magic.bc /usr/lib64/pgsql/bitcode/orafce/replace_empty_string.bc conflict with the package postgresql17-orafce-4.16.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql18-perl-18.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.15-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql18-pg_checksums-1.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.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.; 
postgresql18-pg_cron-1.6.7-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc conflict with the package postgresql17-pg_cron-1.6.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.; s.; 
postgresql18-pg_hint_plan-1.8.0-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-pg_hint_plan-1.7.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pg_hint_plan.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; 
postgresql18-pg_partman-5.3.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.; 
postgresql18-pg_partman-5.3.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw.index.bc /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflict with the package postgresql17-pg_partman-5.3.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.; able, consider using alternatives.; 
postgresql18-pg_repack-1.5.3-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql17-pg_repack-1.5.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.; s.; plicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
postgresql18-pgaudit-18.0-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflict with the package postgresql17-pgaudit-17.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; consider using alternatives.; 
postgresql18-pgauditlogtofile-1.7.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-pgauditlogtofile-1.7.6-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (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.; s.; 
postgresql18-pgvector-0.8.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-pgvector-0.8.1-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/vector.index.bc (12 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.; 
postgresql18-plv8-3.2.4-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/lib64/pgsql/bitcode/plv8-3.2.4/plv8.bc /usr/lib64/pgsql/bitcode/plv8-3.2.4/plv8_type.bc /usr/lib64/pgsql/plv8-3.2.4.so conflict with the package postgresql17-plv8-3.2.4-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.; 
postgresql18-python-18.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-python-17.7-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_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.; , if conflicts are avoidable, consider using alternatives.; 
postgresql18-repmgr-5.5.0-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/repmgr: not systemd compatible: lsb init header missing and repmgr.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
postgresql18-repmgr-5.5.0-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql17-repmgr-5.5.0-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; s.; lternatives.; 
postgresql18-repmgr-5.5.0-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/postgresql18-repmgr-5.5.0-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/repmgr.conf sisyphus_check: check-fhs ERROR: FHS violation; 
postgresql18-server-18.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.; 
postgresql18-server-18.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql17-server-17.7-alt1.x86_64, for example, /usr/bin/initdb (27 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; lternatives.; 
postgresql18-tcl-18.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.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.; ; 
unbound-1.24.2-alt1.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
unbound-1.24.2-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/unbound-1.24.2-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/unbound.conf sisyphus_check: check-fhs ERROR: FHS violation; 
zabbix-java-gateway-7.0.21-alt2.x86_64	init-condrestart	fail	/etc/rc.d/init.d/zabbix_java_gateway: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.; 
