warn	3proxy-0.6.1-alt2.x86_64	Files /usr/bin/proxy /usr/share/man/man8/proxy.8.xz conflict with the package libproxy-tools-0.5.6-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	Little-Wire-examples-1.3-alt1.x86_64	File /usr/bin/adc conflicts with the package autodafe-0.1-alt3_6.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.; 
warn	MySQL-server-8.0.41-alt1.x86_64	File /usr/share/man/man8/mysqld.8.xz conflicts with the package mariadb-client-10.11.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.; 
warn	RTags-2.41-alt3.x86_64	File /usr/bin/rp conflicts with the package rosenpass-0.2.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	akonadi-devel-24.12.3-alt1.x86_64	There are file conflicts with the package kde5-akonadi-devel-23.08.5-alt101.x86_64, for example, /usr/bin/asapcat (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.; 
warn	alterator-control++-0.0.5-alt1.x86_64	Files /usr/lib/alterator/backend3/controlpp /usr/share/alterator/ui/controlpp/lists/ajax.scm conflict with the package alterator-controlpp-0.0.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.; 
warn	alterator-controlpp-0.0.3-alt1.x86_64	Files /usr/lib/alterator/backend3/controlpp /usr/share/alterator/ui/controlpp/lists/ajax.scm conflict with the package alterator-control++-0.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.; 
warn	alterator-livecd-0.9.0-alt1.noarch	Files /usr/lib/alterator/backend3/livecd-start /usr/share/alterator/steps/livecd-finish.desktop /usr/share/alterator/ui/livecd/start/index.scm conflict with the package installer-alterator-livecd-stage2-0.1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib/alterator/backend3/livecd-finish /usr/share/alterator/ui/livecd/finish/index.scm conflict with the package installer-alterator-livecd-stage3-0.1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	alterator-setup-0.4.4-alt1.noarch	File /usr/share/alterator/steps/notes-license.desktop conflicts with the package livecd-install-0.9.21-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	altlinux-release-p11-20240523-alt1.noarch	File /etc/altlinux-release conflicts with the package branding-alt-education-release-11.0-alt0.7.beta.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-server-release-11.0-alt23.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-alt-virtualization-pve-release-11.0-alt0.5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-qazos-release-1.0-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-simply-linux-release-10.910-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-11.0.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	aqute-bnd-6.2.0-alt1_2jpp11.noarch	File /etc/ant.d/aqute-bnd conflicts with the package aqute-bnd4-4.3.1-alt4_4jpp11.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	aqute-bnd4-4.3.1-alt4_4jpp11.noarch	File /etc/ant.d/aqute-bnd conflicts with the package aqute-bnd-6.2.0-alt1_2jpp11.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-alaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.alaw conflicts with the package asterisk-extra-sounds-fr-alaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-g722-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g722 conflicts with the package asterisk-extra-sounds-fr-g722-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-g729-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g729 conflicts with the package asterisk-extra-sounds-fr-g729-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-gsm-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.gsm conflicts with the package asterisk-extra-sounds-fr-gsm-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-siren14-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren14 conflicts with the package asterisk-extra-sounds-fr-siren14-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-siren7-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren7 conflicts with the package asterisk-extra-sounds-fr-siren7-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-sln16-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.sln16 conflicts with the package asterisk-extra-sounds-fr-sln16-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-ulaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.ulaw conflicts with the package asterisk-extra-sounds-fr-ulaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-core-sounds-fr-wav-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.wav conflicts with the package asterisk-extra-sounds-fr-wav-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-alaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.alaw conflicts with the package asterisk-core-sounds-fr-alaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-g722-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g722 conflicts with the package asterisk-core-sounds-fr-g722-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-g729-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.g729 conflicts with the package asterisk-core-sounds-fr-g729-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-gsm-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.gsm conflicts with the package asterisk-core-sounds-fr-gsm-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-siren14-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren14 conflicts with the package asterisk-core-sounds-fr-siren14-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-siren7-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.siren7 conflicts with the package asterisk-core-sounds-fr-siren7-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-sln16-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.sln16 conflicts with the package asterisk-core-sounds-fr-sln16-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-ulaw-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.ulaw conflicts with the package asterisk-core-sounds-fr-ulaw-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	asterisk-extra-sounds-fr-wav-alt1.1-alt1.1.noarch	File /usr/share/asterisk/sounds/fr/astcc-followed-by-the-pound-key.wav conflicts with the package asterisk-core-sounds-fr-wav-alt1.1-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	atril-gtk-dvi-1.27.0-alt2.x86_64	File /usr/lib64/atril/3/backends/libdvidocument.so conflicts with the package mate-document-viewer-dvi-1.28.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.; 
warn	autodafe-0.1-alt3_6.x86_64	File /usr/bin/adc conflicts with the package Little-Wire-examples-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.; 
warn	baikal-openuds-0.0.3-alt2.1.noarch	File /usr/bin/xfreerdp conflicts with the package xfreerdp3-3.14.1-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	batik-slideshow-1.14-alt1_3jpp11.noarch	File /usr/bin/slideshow conflicts with the package racket-main-8.8-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.; 
warn	bitmap-1.0.6-alt1.x86_64	File /usr/bin/bitmap conflicts with the package mesa-demos-9.0.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-education-kde-settings-11.0-alt0.7.beta.noarch	File /etc/skel/.config/kdeglobals conflicts with the package branding-xalt-kworkstation-graphics-11.0.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-education-release-11.0-alt0.7.beta.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p11-20240523-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-education-system-settings-11.0-alt0.7.beta.noarch	File /etc/skel/.vimrc conflicts with the package branding-simply-linux-xfce-settings-10.910-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.; File /etc/skel/.config/gtk-3.0/gtk.css conflicts with the package phosh-background-settings-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-education-xfce-settings-11.0-alt0.7.beta.x86_64	File /etc/skel/.gtkrc-2.0 conflicts with the package branding-xalt-kworkstation-graphics-11.0.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-server-release-11.0-alt23.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p11-20240523-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-alt-virtualization-pve-release-11.0-alt0.5.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p11-20240523-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-qazos-kde-settings-1.0-alt0.1.noarch	File /etc/skel/.config/kdeglobals conflicts with the package branding-xalt-kworkstation-graphics-11.0.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-qazos-release-1.0-alt0.1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p11-20240523-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-qazos-system-settings-1.0-alt0.1.noarch	File /etc/skel/.vimrc conflicts with the package branding-simply-linux-xfce-settings-10.910-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.; File /etc/skel/.config/gtk-3.0/gtk.css conflicts with the package phosh-background-settings-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-qazos-xfce-settings-1.0-alt0.1.x86_64	File /etc/skel/.gtkrc-2.0 conflicts with the package branding-xalt-kworkstation-graphics-11.0.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-simply-linux-release-10.910-alt1.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p11-20240523-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-simply-linux-xfce-settings-10.910-alt1.x86_64	File /etc/skel/.vimrc conflicts with the package branding-alt-education-system-settings-11.0-alt0.7.beta.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.vimrc conflicts with the package branding-qazos-system-settings-1.0-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gtkrc-2.0 conflicts with the package branding-xalt-kworkstation-graphics-11.0.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	branding-xalt-kworkstation-graphics-11.0.0-alt4.noarch	File /etc/skel/.config/kdeglobals conflicts with the package branding-alt-education-kde-settings-11.0-alt0.7.beta.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gtkrc-2.0 conflicts with the package branding-alt-education-xfce-settings-11.0-alt0.7.beta.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/kdeglobals conflicts with the package branding-qazos-kde-settings-1.0-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gtkrc-2.0 conflicts with the package branding-qazos-xfce-settings-1.0-alt0.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-10.910-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.; 
warn	branding-xalt-kworkstation-release-11.0.0-alt4.noarch	File /etc/altlinux-release conflicts with the package altlinux-release-p11-20240523-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	bsd-games-2.17-alt3_71.x86_64	File /usr/bin/sail conflicts with the package libsail-0.9.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.; 
warn	cert-manager-1.14.5-alt1.x86_64	File /usr/bin/webhook conflicts with the package webhook-2.8.1-alt2.1.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.; 
warn	clean-3.1-alt3.x86_64	File /usr/bin/clm conflicts with the package mcl-1.008.09.149-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	codetest_sl-1.6-alt1.x86_64	Files /usr/bin/sl /usr/share/man/man1/sl.1.xz conflict with the package sl-5.02-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.; 
warn	cssed-common-0.4.1-alt2.noarch	File /usr/share/applications/mimeinfo.cache conflicts with the package handbrake-gtk-1.9.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.; 
warn	curlftpfs-ng-0.9.3.1-alt0.1.x86_64	Files /usr/bin/curlftpfs /usr/share/man/man1/curlftpfs.1.xz conflict with the package fuse-curlftpfs-0.9.2-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	db4.7-utils-4.7.25-alt13.x86_64	There are file conflicts with the package pks-db-0.9.6-alt4.x86_64, for example, /usr/bin/db_archive (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.; 
warn	db4.8-utils-4.8.30-alt7.x86_64	There are file conflicts with the package pks-db-0.9.6-alt4.x86_64, for example, /usr/bin/db_archive (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.; 
warn	db6.1-utils-6.1.19-alt9.x86_64	There are file conflicts with the package pks-db-0.9.6-alt4.x86_64, for example, /usr/bin/db_archive (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.; 
warn	dca-apps-0.0.5-alt4.qa1.x86_64	File /usr/bin/dcadec conflicts with the package dcadec-0.2.0-alt1.1.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.; 
warn	dcadec-0.2.0-alt1.1.x86_64	File /usr/bin/dcadec conflicts with the package dca-apps-0.0.5-alt4.qa1.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.; 
warn	deepin-screen-recorder-6.0.5-alt1.x86_64	File /usr/share/dbus-1/services/com.deepin.Screenshot.service conflicts with the package deepin-screenshot-5.0.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.; 
warn	deepin-screenshot-5.0.0-alt1.x86_64	File /usr/share/dbus-1/services/com.deepin.Screenshot.service conflicts with the package deepin-screen-recorder-6.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.; 
warn	deepin-session-ui-6.0.18-alt1.x86_64	File /usr/share/dbus-1/services/org.freedesktop.Notifications.service conflicts with the package notify-osd-0.9.34-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.; 
warn	ecm-1.03-alt2.x86_64	File /usr/bin/ecm conflicts with the package gmp-ecm-7.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.; 
warn	fish-4.0.1-alt1.x86_64	File /usr/share/fish/completions/yadm.fish conflicts with the package yadm-3.2.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	fontpackages-devel-1.44-alt8_24.noarch	There are file conflicts with the package rpm-build-fedora-compat-fonts-2.0.5-alt2_11.noarch, for example, /usr/share/fontconfig/templates/basic-font-template.conf (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.; 
warn	fonts-ttf-chinese-opendesktop-1.6.100-alt1_12.noarch	Files /usr/share/ghostscript/conf.d/CIDFnmap.zh_CN /usr/share/ghostscript/conf.d/FAPIcidfmap.zh_CN /usr/share/ghostscript/conf.d/cidfmap.zh_CN conflict with the package ghostscript-chinese-zh_CN-0.4.0-alt1_9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/ghostscript/conf.d/CIDFnmap.zh_TW /usr/share/ghostscript/conf.d/FAPIcidfmap.zh_TW /usr/share/ghostscript/conf.d/cidfmap.zh_TW conflict with the package ghostscript-chinese-zh_TW-0.4.0-alt1_9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	fpc-utils-3.2.3-alt1.x86_64	File /usr/bin/relpath conflicts with the package tsugaru-tests-20230113-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	fuse-curlftpfs-0.9.2-alt3.x86_64	Files /usr/bin/curlftpfs /usr/share/man/man1/curlftpfs.1.xz conflict with the package curlftpfs-ng-0.9.3.1-alt0.1.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.; 
warn	fuse-obexfs-0.11-alt0.rc3.qa2.x86_64	Files /usr/bin/obexautofs /usr/bin/obexfs conflict with the package obexftp-0.24.2.1-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	garden-1.0.9-alt1_18.x86_64	File /usr/bin/garden conflicts with the package python3-module-kivy-garden-0.1.4-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gcc10-gdc-doc-10.5.0-alt1.x86_64	File /usr/share/info/gdc.info.xz conflicts with the package gcc11-gdc-doc-11.4.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc12-gdc-doc-12.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc13-gdc-doc-13.2.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gcc11-gdc-doc-11.4.1-alt1.x86_64	File /usr/share/info/gdc.info.xz conflicts with the package gcc10-gdc-doc-10.5.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc12-gdc-doc-12.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc13-gdc-doc-13.2.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gcc12-gdc-doc-12.3.1-alt1.x86_64	File /usr/share/info/gdc.info.xz conflicts with the package gcc10-gdc-doc-10.5.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc11-gdc-doc-11.4.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc13-gdc-doc-13.2.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gcc13-gdc-doc-13.2.1-alt3.x86_64	File /usr/share/info/gdc.info.xz conflicts with the package gcc10-gdc-doc-10.5.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc11-gdc-doc-11.4.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.; File /usr/share/info/gdc.info.xz conflicts with the package gcc12-gdc-doc-12.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.; 
warn	gem-bluecloth-devel-2.2.0-alt1.noarch	There are file conflicts with the package gem-rdiscount-devel-2.2.0.2-alt1.1.noarch, for example, /usr/include/config.h (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/include/mkdio.h conflicts with the package libdiscount-devel-2.2.7d-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.; File /usr/include/config.h conflicts with the package libpicosat-devel-965-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/include/cstring.h conflicts with the package libsexpr-devel-1.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.; 
warn	gem-cool-io-devel-1.7.1-alt1.noarch	Files /usr/include/libev/ev.h /usr/include/libev/ev_vars.h /usr/include/libev/ev_wrap.h conflict with the package gem-nio4r-devel-2.5.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gem-msgpack-devel-1.7.2-alt1.noarch	File /usr/include/msgpack/sysdep.h conflicts with the package libmsgpack-c-devel-6.0.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.; 
warn	gem-nio4r-devel-2.5.8-alt1.noarch	Files /usr/include/libev/ev.h /usr/include/libev/ev_vars.h /usr/include/libev/ev_wrap.h conflict with the package gem-cool-io-devel-1.7.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gem-rdiscount-devel-2.2.0.2-alt1.1.noarch	There are file conflicts with the package gem-bluecloth-devel-2.2.0-alt1.noarch, for example, /usr/include/config.h (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.; 
warn	gem-unicode-devel-0.4.4.4-alt1.1.noarch	File /usr/include/unicode/ustring.h conflicts with the package libicu-devel-7.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.; 
warn	gerris-20131206-alt1.x86_64	File /usr/bin/shapes conflicts with the package gnustep-opal-r37181-alt6.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.; 
warn	ghostscript-chinese-zh_CN-0.4.0-alt1_9.noarch	Files /usr/share/ghostscript/conf.d/CIDFnmap.zh_CN /usr/share/ghostscript/conf.d/FAPIcidfmap.zh_CN /usr/share/ghostscript/conf.d/cidfmap.zh_CN conflict with the package fonts-ttf-chinese-opendesktop-1.6.100-alt1_12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	ghostscript-chinese-zh_TW-0.4.0-alt1_9.noarch	Files /usr/share/ghostscript/conf.d/CIDFnmap.zh_TW /usr/share/ghostscript/conf.d/FAPIcidfmap.zh_TW /usr/share/ghostscript/conf.d/cidfmap.zh_TW conflict with the package fonts-ttf-chinese-opendesktop-1.6.100-alt1_12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gitea-tea-0.9.2-alt2.x86_64	File /usr/bin/tea conflicts with the package tea-62.0.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.; 
warn	glusterfs10-georeplication-10.5-alt1.x86_64	There are file conflicts with the package glusterfs11-georeplication-11.1-alt2.x86_64, for example, /usr/lib/glusterfs/python/syncdaemon/__pycache__/resource.cpython-312.opt-1.pyc (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.; 
warn	glusterfs11-georeplication-11.1-alt2.x86_64	There are file conflicts with the package glusterfs10-georeplication-10.5-alt1.x86_64, for example, /usr/lib/glusterfs/python/syncdaemon/__pycache__/resource.cpython-312.opt-1.pyc (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.; 
warn	gmp-ecm-7.0.5-alt1.x86_64	File /usr/bin/ecm conflicts with the package ecm-1.03-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	gnustep-opal-r37181-alt6.x86_64	File /usr/bin/shapes conflicts with the package gerris-20131206-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.; 
warn	go-task-3.19.1-alt1.x86_64	File /usr/bin/task conflicts with the package task-core-2.5.1-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.; 
warn	handbrake-gtk-1.9.0-alt1.x86_64	File /usr/share/applications/mimeinfo.cache conflicts with the package cssed-common-0.4.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	identity-0.7.0-alt1.x86_64	File /usr/bin/identity conflicts with the package mesa-demos-9.0.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	incus-tools-6.5.0-alt1.x86_64	File /usr/bin/fuidshift conflicts with the package lxd-5.21.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.; 
warn	inn-2.7.2-alt1.x86_64	File /usr/share/man/man1/sm.1.xz conflicts with the package screen-message-0.6-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-alterator-livecd-stage2-0.1.2-alt1.noarch	Files /usr/lib/alterator/backend3/livecd-start /usr/share/alterator/steps/livecd-finish.desktop /usr/share/alterator/ui/livecd/start/index.scm conflict with the package alterator-livecd-0.9.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-alterator-livecd-stage3-0.1.2-alt1.noarch	Files /usr/lib/alterator/backend3/livecd-finish /usr/share/alterator/ui/livecd/finish/index.scm conflict with the package alterator-livecd-0.9.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-alt-education-stage2-11.0-alt4.noarch	There are file conflicts with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-skip-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-centaurus-stage2-11.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.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-skip-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.2-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; 
warn	installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch	There are file conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-11.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-cliff-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.2-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch	There are file conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-11.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.2-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch	There are file conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-11.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.2-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-education-stage2-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-kworkstation-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-education-stage2-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-kworkstation-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-centaurus-stage2-11.0-alt1.x86_64	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-skip-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-education-stage2-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-kworkstation-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; 
warn	installer-distro-cliff-common-10.2-alt1.x86_64	File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-kworkstation-stage2-10.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.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-cliff-stage2-10.2-alt1.x86_64	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-skip-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-education-stage2-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-kworkstation-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-jeos-stage2-0.1-alt2.noarch	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-education-stage2-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-kworkstation-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-kworkstation-stage2-10.2-alt1.x86_64	There are file conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; 
warn	installer-distro-regular-stage2-0.3-alt3.noarch	Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-education-stage2-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-kworkstation-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-simply-linux-stage2-11.3.0-alt1.noarch	There are file conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh conflict with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-centaurus-stage2-11.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-kworkstation-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-token-desktop-stage2-0.1.1-alt5.noarch	There are file conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; There are file conflicts with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-11.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.2-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-distro-virtualization-pve-stage2-11.0.0-alt0.3.noarch	There are file conflicts with the package installer-distro-alt-education-stage2-11.0-alt4.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-alt-server-v-stage2-10.1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-11.0.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-centaurus-stage2-11.0-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/postinstall.d/20-alterator-menu.sh /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-cliff-common-10.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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.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.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-0.1-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.2-alt1.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-stage2-0.3-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-11.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-alt5.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-alphabet-profiles-1.0-alt2.noarch	File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-centaurus-profiles-2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-centaurus-profiles-2.0-alt1.noarch	File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-alphabet-profiles-1.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-vm-fs-stage2-0.3-alt2.noarch	File /usr/share/install2/initinstall.d/05-vm-profile-ofs conflicts with the package installer-feature-vm-ofs-stage2-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-vm-fs-stage3-0.3-alt2.noarch	File /usr/share/install2/preinstall.d/01-move-fs-ofs conflicts with the package installer-feature-vm-ofs-stage3-0.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-vm-ofs-stage2-0.3-alt1.noarch	File /usr/share/install2/initinstall.d/05-vm-profile-ofs conflicts with the package installer-feature-vm-fs-stage2-0.3-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	installer-feature-vm-ofs-stage3-0.3-alt1.noarch	File /usr/share/install2/preinstall.d/01-move-fs-ofs conflicts with the package installer-feature-vm-fs-stage3-0.3-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	java-wakeonlan-1.0.0-alt1_17jpp11.noarch	File /usr/bin/wakeonlan conflicts with the package wakeonlan-0.42-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	kde5-akonadi-devel-23.08.5-alt101.x86_64	There are file conflicts with the package akonadi-devel-24.12.3-alt1.x86_64, for example, /usr/bin/asapcat (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.; 
warn	kernel-source-rtl8723de-4.11up-5.1.1.8-alt6.noarch	File /usr/src/kernel/sources/kernel-source-rtl8723de-5.1.1.8.tar.bz2 conflicts with the package kernel-source-rtl8723de-4.15up-5.1.1.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	kernel-source-rtl8723de-4.15up-5.1.1.8-alt1.noarch	File /usr/src/kernel/sources/kernel-source-rtl8723de-5.1.1.8.tar.bz2 conflicts with the package kernel-source-rtl8723de-4.11up-5.1.1.8-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	lexmark7000linux-990516-alt1.x86_64	File /usr/bin/pbm2l7k conflicts with the package pbm2l7k-990321-alt1.qa2.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.; 
warn	libLLVMSPIRVLib-devel-19.1.0-alt1.x86_64	Files /usr/include/LLVMSPIRVLib/LLVMSPIRVExtensions.inc /usr/include/LLVMSPIRVLib/LLVMSPIRVLib.h /usr/include/LLVMSPIRVLib/LLVMSPIRVOpts.h conflict with the package libspirv-llvm14.0-translator-devel-14.0.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.; 
warn	libann-devel-static-1.1.2-alt5.x86_64	File /usr/lib64/libANN.a conflicts with the package micmac-libann-devel-static-1.1.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libdiscount-devel-2.2.7d-alt1.x86_64	File /usr/include/mkdio.h conflicts with the package gem-bluecloth-devel-2.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libecpg6-13-devel-static-13.20-alt4.x86_64	There are file conflicts with the package libecpg6-14-devel-static-14.17-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-15-devel-static-15.12-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-16-devel-static-16.8-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-1C-devel-static-17.2-alt8.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-devel-static-17.4-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; 
warn	libecpg6-14-devel-static-14.17-alt4.x86_64	There are file conflicts with the package libecpg6-13-devel-static-13.20-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-15-devel-static-15.12-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-16-devel-static-16.8-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-1C-devel-static-17.2-alt8.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-devel-static-17.4-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; 
warn	libecpg6-15-devel-static-15.12-alt4.x86_64	There are file conflicts with the package libecpg6-13-devel-static-13.20-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-14-devel-static-14.17-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-16-devel-static-16.8-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-1C-devel-static-17.2-alt8.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-devel-static-17.4-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; 
warn	libecpg6-16-devel-static-16.8-alt4.x86_64	There are file conflicts with the package libecpg6-13-devel-static-13.20-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-14-devel-static-14.17-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-15-devel-static-15.12-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-1C-devel-static-17.2-alt8.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-devel-static-17.4-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; 
warn	libecpg6-17-1C-devel-static-17.2-alt8.x86_64	There are file conflicts with the package libecpg6-13-devel-static-13.20-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-14-devel-static-14.17-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-15-devel-static-15.12-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-16-devel-static-16.8-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-devel-static-17.4-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; 
warn	libecpg6-17-devel-static-17.4-alt4.x86_64	There are file conflicts with the package libecpg6-13-devel-static-13.20-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-14-devel-static-14.17-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-15-devel-static-15.12-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-16-devel-static-16.8-alt4.x86_64, for example, /usr/lib64/libecpg.a (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.; There are file conflicts with the package libecpg6-17-1C-devel-static-17.2-alt8.x86_64, for example, /usr/lib64/libecpg.a (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.; 
warn	libgcrypt-devel-1.10.2-alt2.x86_64	There are file conflicts with the package libgcrypt-gost-devel-1.8.5-alt6.x86_64, for example, /usr/bin/libgcrypt-config (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.; 
warn	libgcrypt-gost-devel-1.8.5-alt6.x86_64	There are file conflicts with the package libgcrypt-devel-1.10.2-alt2.x86_64, for example, /usr/bin/libgcrypt-config (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.; 
warn	libicu-devel-7.4.2-alt1.x86_64	File /usr/include/unicode/ustring.h conflicts with the package gem-unicode-devel-0.4.4.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	liblcf0-0.7.0-alt1_3.x86_64	There are file conflicts with the package shared-mime-info-2.4-alt1.x86_64, for example, /usr/share/mime/globs (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.; 
warn	liblensfun-devel-0.3.95-alt1.x86_64	There are file conflicts with the package liblensfun1-devel-0.3.4-alt1.x86_64, for example, /usr/include/lensfun/lensfun.h (79 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.; 
warn	liblensfun1-devel-0.3.4-alt1.x86_64	There are file conflicts with the package liblensfun-devel-0.3.95-alt1.x86_64, for example, /usr/include/lensfun/lensfun.h (79 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.; 
warn	liblog4cplus-devel-docs-2.0.7-alt1.2.x86_64	File /usr/share/man/man3/config.h.3.xz conflicts with the package libpgf-devel-7.21.7-alt1_2.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.; 
warn	libmilter-devel-static-8.14.3_1-alt1_12.x86_64	Files /usr/include/libmilter/mfapi.h /usr/include/libmilter/mfdef.h /usr/include/libmilter/milter.h conflict with the package sendmail-devel-8.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.; 
warn	libmozjs115-devel-static-115.2.0-alt2.x86_64	File /usr/lib64/libjs_static.a conflicts with the package libmozjs128-devel-static-128.1.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libmozjs128-devel-static-128.1.0-alt1.x86_64	File /usr/lib64/libjs_static.a conflicts with the package libmozjs115-devel-static-115.2.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libmsgpack-c-devel-6.0.1-alt1.x86_64	File /usr/include/msgpack/sysdep.h conflicts with the package gem-msgpack-devel-1.7.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libpgf-devel-7.21.7-alt1_2.x86_64	File /usr/share/man/man3/config.h.3.xz conflicts with the package liblog4cplus-devel-docs-2.0.7-alt1.2.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.; 
warn	libpicosat-devel-965-alt3.x86_64	File /usr/include/config.h conflicts with the package gem-bluecloth-devel-2.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libpq5-13-devel-static-13.20-alt4.x86_64	File /usr/lib64/libpq.a conflicts with the package libpq5-14-devel-static-14.17-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-15-devel-static-15.12-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-16-devel-static-16.8-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-1C-devel-static-17.2-alt8.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-devel-static-17.4-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.; 
warn	libpq5-14-devel-static-14.17-alt4.x86_64	File /usr/lib64/libpq.a conflicts with the package libpq5-13-devel-static-13.20-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-15-devel-static-15.12-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-16-devel-static-16.8-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-1C-devel-static-17.2-alt8.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-devel-static-17.4-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.; 
warn	libpq5-15-devel-static-15.12-alt4.x86_64	File /usr/lib64/libpq.a conflicts with the package libpq5-13-devel-static-13.20-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-14-devel-static-14.17-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-16-devel-static-16.8-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-1C-devel-static-17.2-alt8.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-devel-static-17.4-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.; 
warn	libpq5-16-devel-static-16.8-alt4.x86_64	File /usr/lib64/libpq.a conflicts with the package libpq5-13-devel-static-13.20-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-14-devel-static-14.17-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-15-devel-static-15.12-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-1C-devel-static-17.2-alt8.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-devel-static-17.4-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.; 
warn	libpq5-17-1C-devel-static-17.2-alt8.x86_64	File /usr/lib64/libpq.a conflicts with the package libpq5-13-devel-static-13.20-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-14-devel-static-14.17-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-15-devel-static-15.12-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-16-devel-static-16.8-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-devel-static-17.4-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.; 
warn	libpq5-17-devel-static-17.4-alt4.x86_64	File /usr/lib64/libpq.a conflicts with the package libpq5-13-devel-static-13.20-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-14-devel-static-14.17-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-15-devel-static-15.12-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-16-devel-static-16.8-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.; File /usr/lib64/libpq.a conflicts with the package libpq5-17-1C-devel-static-17.2-alt8.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.; 
warn	libproxy-tools-0.5.6-alt1.x86_64	Files /usr/bin/proxy /usr/share/man/man8/proxy.8.xz conflict with the package 3proxy-0.6.1-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libreadline-devel-8.2.10-alt1.x86_64	There are file conflicts with the package libreadline5-devel-5.2.14-alt7.x86_64, for example, /usr/include/readline/chardefs.h (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.; 
warn	libreadline5-devel-5.2.14-alt7.x86_64	There are file conflicts with the package libreadline-devel-8.2.10-alt1.x86_64, for example, /usr/include/readline/chardefs.h (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.; 
warn	libsail-0.9.1-alt1.x86_64	File /usr/bin/sail conflicts with the package bsd-games-2.17-alt3_71.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.; 
warn	libsexpr-devel-1.3.1-alt1.x86_64	File /usr/include/cstring.h conflicts with the package gem-bluecloth-devel-2.2.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libshape-1.5.0-alt1.x86_64	File /usr/bin/dbfdump conflicts with the package perl-DBD-XBase-1.08-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libspirv-llvm14.0-translator-devel-14.0.7-alt1.x86_64	Files /usr/include/LLVMSPIRVLib/LLVMSPIRVExtensions.inc /usr/include/LLVMSPIRVLib/LLVMSPIRVLib.h /usr/include/LLVMSPIRVLib/LLVMSPIRVOpts.h conflict with the package libLLVMSPIRVLib-devel-19.1.0-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	livecd-0ad-0.2-alt1.noarch	File /etc/sysconfig/livecd-runapp conflicts with the package livecd-attract-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/sysconfig/livecd-runapp conflicts with the package livecd-fgfs-0.2-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	livecd-attract-0.1-alt1.noarch	File /etc/sysconfig/livecd-runapp conflicts with the package livecd-0ad-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/sysconfig/livecd-runapp conflicts with the package livecd-fgfs-0.2-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	livecd-fgfs-0.2-alt2.noarch	File /etc/sysconfig/livecd-runapp conflicts with the package livecd-0ad-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/sysconfig/livecd-runapp conflicts with the package livecd-attract-0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	livecd-gnome-nowarn-space-0.3-alt1.noarch	File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-alt-education-xfce-settings-11.0-alt0.7.beta.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-qazos-xfce-settings-1.0-alt0.1.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.; 
warn	livecd-install-0.9.21-alt1.noarch	File /usr/share/alterator/steps/notes-license.desktop conflicts with the package alterator-setup-0.4.4-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/X11/profile.d/zdg-user-dirs-install.sh conflicts with the package tionix-vdi-client-2.6.0-alt5.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	lxc-templates-6.0.3-alt2.noarch	Files /usr/share/lxc/templates/lxc-local /usr/share/lxc/templates/lxc-oci conflict with the package pve-lxc-6.0.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	lxd-5.21.1-alt1.x86_64	File /usr/bin/fuidshift conflicts with the package incus-tools-6.5.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.; 
warn	ly-0.6.0-alt0.g2ca870c.x86_64	File /usr/bin/ly conflicts with the package python3-module-ly-0.9.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mariadb-client-10.11.11-alt1.x86_64	File /usr/share/man/man8/mysqld.8.xz conflicts with the package MySQL-server-8.0.41-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.; 
warn	mate-document-viewer-dvi-1.28.0-alt1.x86_64	File /usr/lib64/atril/3/backends/libdvidocument.so conflicts with the package atril-gtk-dvi-1.27.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mcl-1.008.09.149-alt2.x86_64	File /usr/bin/clm conflicts with the package clean-3.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	mesa-demos-9.0.0-alt2.x86_64	File /usr/bin/bitmap conflicts with the package bitmap-1.0.6-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/identity conflicts with the package identity-0.7.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.; 
warn	micmac-libann-devel-static-1.1.1-alt1.x86_64	File /usr/lib64/libANN.a conflicts with the package libann-devel-static-1.1.2-alt5.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.; 
warn	mplayer-1.5-alt2.g567631e.x86_64	There are file conflicts with the package mplayer-skins-2.0-alt5.noarch, for example, /usr/share/mplayer/skins/Blue/VERSION (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.; 
warn	mplayer-skins-2.0-alt5.noarch	There are file conflicts with the package mplayer-1.5-alt2.g567631e.x86_64, for example, /usr/share/mplayer/skins/Blue/VERSION (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.; 
warn	munge-0.5.15-alt1.x86_64	File /usr/bin/munge conflicts with the package python3-module-munge-1.3.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	nfft-3.2.3-alt2.x86_64	File /usr/bin/radon conflicts with the package python3-module-radon-6.0.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	notify-osd-0.9.34-alt1.x86_64	File /usr/share/dbus-1/services/org.freedesktop.Notifications.service conflicts with the package deepin-session-ui-6.0.18-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.; 
warn	nxdialog-3.5.99.26.1-alt3.2.x86_64	File /usr/bin/nxdialog conflicts with the package rx-etersoft-1.5.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	obexftp-0.24.2.1-alt2.x86_64	Files /usr/bin/obexautofs /usr/bin/obexfs conflict with the package fuse-obexfs-0.11-alt0.rc3.qa2.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.; 
warn	oregano-0.84.43-alt2.x86_64	File /usr/share/glib-2.0/schemas/gschemas.compiled conflicts with the package soundconverter-4.0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	pbm2l7k-990321-alt1.qa2.x86_64	File /usr/bin/pbm2l7k conflicts with the package lexmark7000linux-990516-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.; 
warn	perl-DBD-XBase-1.08-alt2.noarch	File /usr/bin/dbfdump conflicts with the package libshape-1.5.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.; 
warn	perl-Math-Primality-scripts-0.08-alt2.noarch	File /usr/bin/primes.pl conflicts with the package perl-Math-Prime-Util-scripts-0.73-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	perl-Math-Prime-Util-scripts-0.73-alt3.noarch	File /usr/bin/primes.pl conflicts with the package perl-Math-Primality-scripts-0.08-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	pgpdump-0.36-alt1.x86_64	File /usr/bin/pgpdump conflicts with the package pks-utils-0.9.6-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.; 
warn	phosh-background-settings-0.1-alt1.noarch	File /etc/skel/.config/gtk-3.0/gtk.css conflicts with the package branding-alt-education-system-settings-11.0-alt0.7.beta.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /etc/skel/.config/gtk-3.0/gtk.css conflicts with the package branding-qazos-system-settings-1.0-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	php8.1-pdo-devel-8.1.32-alt1.x86_64	Files /usr/include/php/ext/pdo/php_pdo.h /usr/include/php/ext/pdo/php_pdo_driver.h conflict with the package php8.2-pdo-devel-8.2.28-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.; Files /usr/include/php/ext/pdo/php_pdo.h /usr/include/php/ext/pdo/php_pdo_driver.h conflict with the package php8.3-pdo-devel-8.3.19-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.; 
warn	php8.2-pdo-devel-8.2.28-alt1.x86_64	Files /usr/include/php/ext/pdo/php_pdo.h /usr/include/php/ext/pdo/php_pdo_driver.h conflict with the package php8.1-pdo-devel-8.1.32-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.; 
warn	php8.3-pdo-devel-8.3.19-alt1.x86_64	Files /usr/include/php/ext/pdo/php_pdo.h /usr/include/php/ext/pdo/php_pdo_driver.h conflict with the package php8.1-pdo-devel-8.1.32-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.; 
warn	pks-db-0.9.6-alt4.x86_64	There are file conflicts with the package db4.7-utils-4.7.25-alt13.x86_64, for example, /usr/bin/db_archive (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.; There are file conflicts with the package db4.8-utils-4.8.30-alt7.x86_64, for example, /usr/bin/db_archive (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.; There are file conflicts with the package db6.1-utils-6.1.19-alt9.x86_64, for example, /usr/bin/db_archive (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.; 
warn	pks-utils-0.9.6-alt4.x86_64	File /usr/bin/pgpdump conflicts with the package pgpdump-0.36-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.; 
warn	postgresql13-contrib-13.20-alt4.x86_64	There are file conflicts with the package postgresql14-contrib-14.17-alt4.x86_64, for example, /usr/bin/pgbench (23 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-contrib-15.12-alt4.x86_64, for example, /usr/bin/pgbench (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-contrib-16.8-alt4.x86_64, for example, /usr/bin/pgbench (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.; There are file conflicts with the package postgresql17-contrib-17.4-alt4.x86_64, for example, /usr/bin/oid2name (43 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-credcheck-3.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql14-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql15-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql16-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql17-1C-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql17-credcheck-3.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.; 
warn	postgresql13-iplike-2.3.0-alt2.x86_64	File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql16-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql17-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-llvmjit-13.20-alt4.x86_64	There are file conflicts with the package postgresql14-llvmjit-14.17-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (716 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-llvmjit-15.12-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (756 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-llvmjit-16.8-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (780 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-1C-llvmjit-17.2-alt8.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (786 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-llvmjit-17.4-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (785 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.; 
warn	postgresql13-multicorn2-2.5-alt2.x86_64	Files /usr/lib64/pgsql/bitcode/multicorn/src/multicorn.bc /usr/lib64/pgsql/bitcode/multicorn/src/python.bc /usr/lib64/pgsql/bitcode/multicorn/src/query.bc conflict with the package postgresql14-multicorn2-2.5-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/multicorn/src/multicorn.bc /usr/lib64/pgsql/bitcode/multicorn/src/python.bc /usr/lib64/pgsql/bitcode/multicorn/src/query.bc conflict with the package postgresql15-multicorn2-2.5-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-orafce-4.14.3-alt1.x86_64	There are file conflicts with the package postgresql14-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (26 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (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.; There are file conflicts with the package postgresql16-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-perl-13.20-alt4.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-perl-14.17-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.12-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.8-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.4-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.; 
warn	postgresql13-pg-auto-failover-2.2-alt1.x86_64	There are file conflicts with the package postgresql14-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover/formation_metadata.bc (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.; There are file conflicts with the package postgresql15-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/bin/pg_autoctl (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.; There are file conflicts with the package postgresql16-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.; There are file conflicts with the package postgresql17-1C-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.; 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.; 
warn	postgresql13-pg_checksums-1.2-alt2.x86_64	File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-1C-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-pg_cron-1.6.5-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql14-pg_cron-1.6.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.; Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql15-pg_cron-1.6.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.; There are file conflicts with the package postgresql16-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql17-1C-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql17-pg_cron-1.6.5-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.; 
warn	postgresql13-pg_partman-4.7.4-alt1.x86_64	There are file conflicts with the package postgresql14-pg_partman-5.2.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-pg_partman-5.2.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-pg_partman-5.2.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pg_partman-5.2.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 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.; 
warn	postgresql13-pg_repack-1.5.2-alt1.x86_64	There are file conflicts with the package postgresql14-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (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.; There are file conflicts with the package postgresql15-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (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.; There are file conflicts with the package postgresql16-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (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.; There are file conflicts with the package postgresql17-1C-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (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.; There are file conflicts with the package postgresql17-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (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.; 
warn	postgresql13-pgaudit-1.5.3-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql14-pgaudit-1.6.3-alt0.rc1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql15-pgaudit-1.7.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.; There are file conflicts with the package postgresql16-pgaudit-16.1-alt0.rc1.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.; There are file conflicts with the package postgresql17-1C-pgaudit-17.1-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.; There are file conflicts with the package postgresql17-pgaudit-17.1-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.; 
warn	postgresql13-postgis-3.5.2-alt1.x86_64	There are file conflicts with the package postgresql14-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (88 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (95 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (106 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (106 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.; 
warn	postgresql13-python-13.20-alt4.x86_64	Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql14-python-14.17-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.; Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql15-python-15.12-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.; Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql16-python-16.8-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.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql17-1C-contrib-17.2-alt8.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql17-python-17.4-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.; 
warn	postgresql13-repmgr-5.5.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc /usr/lib64/pgsql/repmgr.so conflict with the package postgresql14-repmgr-5.5.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.; Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc /usr/lib64/pgsql/repmgr.so conflict with the package postgresql15-repmgr-5.5.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.; There are file conflicts with the package postgresql16-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-server-13.20-alt4.x86_64	There are file conflicts with the package postgresql14-server-14.17-alt4.x86_64, for example, /usr/bin/initdb (21 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-server-15.12-alt4.x86_64, for example, /usr/bin/initdb (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-server-16.8-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-server-17.4-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-tcl-13.20-alt4.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql15-tcl-15.12-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.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql16-tcl-16.8-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.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.4-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.; 
warn	postgresql13-tds_fdw-2.0.4-alt1.x86_64	There are file conflicts with the package postgresql14-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.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.; There are file conflicts with the package postgresql15-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.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.; There are file conflicts with the package postgresql16-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.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.; There are file conflicts with the package postgresql17-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql13-timescaledb-2.15.3-alt1.x86_64	File /usr/share/pgsql/extension/timescaledb.control conflicts with the package postgresql14-timescaledb-2.17.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.; File /usr/share/pgsql/extension/timescaledb.control conflicts with the package postgresql15-timescaledb-2.17.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.; File /usr/share/pgsql/extension/timescaledb.control conflicts with the package postgresql16-timescaledb-2.17.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.; 
warn	postgresql14-contrib-14.17-alt4.x86_64	There are file conflicts with the package postgresql13-contrib-13.20-alt4.x86_64, for example, /usr/bin/pgbench (23 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-contrib-15.12-alt4.x86_64, for example, /usr/bin/pgbench (21 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-contrib-16.8-alt4.x86_64, for example, /usr/bin/pgbench (34 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-contrib-17.4-alt4.x86_64, for example, /usr/bin/oid2name (40 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.; 
warn	postgresql14-credcheck-3.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql13-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql15-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql16-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql17-1C-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql17-credcheck-3.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.; 
warn	postgresql14-iplike-2.3.0-alt2.x86_64	File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql16-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql17-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql14-llvmjit-14.17-alt4.x86_64	There are file conflicts with the package postgresql13-llvmjit-13.20-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (716 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-llvmjit-15.12-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (509 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-llvmjit-16.8-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (722 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-1C-llvmjit-17.2-alt8.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (750 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-llvmjit-17.4-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (748 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.; 
warn	postgresql14-multicorn2-2.5-alt2.x86_64	Files /usr/lib64/pgsql/bitcode/multicorn/src/multicorn.bc /usr/lib64/pgsql/bitcode/multicorn/src/python.bc /usr/lib64/pgsql/bitcode/multicorn/src/query.bc conflict with the package postgresql13-multicorn2-2.5-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/multicorn/src/multicorn.bc /usr/lib64/pgsql/bitcode/multicorn/src/python.bc /usr/lib64/pgsql/bitcode/multicorn/src/query.bc conflict with the package postgresql15-multicorn2-2.5-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql14-orafce-4.14.3-alt1.x86_64	There are file conflicts with the package postgresql13-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (26 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.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.; There are file conflicts with the package postgresql16-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (23 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (23 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.; 
warn	postgresql14-perl-14.17-alt4.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.8-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.4-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.; 
warn	postgresql14-pg-auto-failover-2.2-alt1.x86_64	There are file conflicts with the package postgresql13-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover/formation_metadata.bc (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.; There are file conflicts with the package postgresql15-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.; There are file conflicts with the package postgresql16-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.; There are file conflicts with the package postgresql17-1C-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.; 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.; 
warn	postgresql14-pg_checksums-1.2-alt2.x86_64	File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-1C-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql14-pg_cron-1.6.5-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql13-pg_cron-1.6.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.; 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 postgresql15-pg_cron-1.6.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.; There are file conflicts with the package postgresql16-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql17-1C-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql17-pg_cron-1.6.5-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.; 
warn	postgresql14-pg_partman-5.2.4-alt1.x86_64	There are file conflicts with the package postgresql13-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql15-pg_partman-5.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.; Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql16-pg_partman-5.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.; Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql17-pg_partman-5.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.; 
warn	postgresql14-pg_repack-1.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql15-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql16-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql17-1C-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql17-pg_repack-1.5.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.; 
warn	postgresql14-pgaudit-1.6.3-alt0.rc1.x86_64	Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql13-pgaudit-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.; File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql15-pgaudit-1.7.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.; There are file conflicts with the package postgresql16-pgaudit-16.1-alt0.rc1.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.; There are file conflicts with the package postgresql17-1C-pgaudit-17.1-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.; There are file conflicts with the package postgresql17-pgaudit-17.1-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.; 
warn	postgresql14-pgauditlogtofile-1.6.4-alt1.x86_64	There are file conflicts with the package postgresql15-pgauditlogtofile-1.6.4-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.; There are file conflicts with the package postgresql16-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.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.; There are file conflicts with the package postgresql17-1C-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.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.; There are file conflicts with the package postgresql17-pgauditlogtofile-1.6.4-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.; 
warn	postgresql14-postgis-3.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (88 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (88 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (105 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (105 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.; 
warn	postgresql14-python-14.17-alt4.x86_64	Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql13-python-13.20-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.8-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql17-python-17.4-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.; 
warn	postgresql14-repmgr-5.5.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc /usr/lib64/pgsql/repmgr.so conflict with the package postgresql13-repmgr-5.5.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.; Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql15-repmgr-5.5.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.; There are file conflicts with the package postgresql16-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (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.; There are file conflicts with the package postgresql17-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (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.; 
warn	postgresql14-server-14.17-alt4.x86_64	There are file conflicts with the package postgresql13-server-13.20-alt4.x86_64, for example, /usr/bin/initdb (21 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-server-15.12-alt4.x86_64, for example, /usr/bin/initdb (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.; There are file conflicts with the package postgresql16-server-16.8-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-server-17.4-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql14-tcl-14.17-alt4.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql15-tcl-15.12-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.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql16-tcl-16.8-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.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.4-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.; 
warn	postgresql14-tds_fdw-2.0.4-alt1.x86_64	There are file conflicts with the package postgresql13-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.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.; 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 postgresql15-tds_fdw-2.0.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.; 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.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.; There are file conflicts with the package postgresql17-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql14-timescaledb-2.17.2-alt1.x86_64	File /usr/share/pgsql/extension/timescaledb.control conflicts with the package postgresql13-timescaledb-2.15.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.; Files /usr/lib64/pgsql/timescaledb-2.17.2.so /usr/lib64/pgsql/timescaledb-tsl-2.17.2.so conflict with the package postgresql15-timescaledb-2.17.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.; Files /usr/lib64/pgsql/timescaledb-2.17.2.so /usr/lib64/pgsql/timescaledb-tsl-2.17.2.so conflict with the package postgresql16-timescaledb-2.17.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.; 
warn	postgresql15-contrib-15.12-alt4.x86_64	There are file conflicts with the package postgresql13-contrib-13.20-alt4.x86_64, for example, /usr/bin/pgbench (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-contrib-14.17-alt4.x86_64, for example, /usr/bin/pgbench (21 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-contrib-16.8-alt4.x86_64, for example, /usr/bin/pgbench (30 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-contrib-17.4-alt4.x86_64, for example, /usr/bin/oid2name (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql15-credcheck-3.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql13-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql14-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql16-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql17-1C-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql17-credcheck-3.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.; 
warn	postgresql15-iplike-2.3.0-alt2.x86_64	File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql16-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql17-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql15-llvmjit-15.12-alt4.x86_64	There are file conflicts with the package postgresql13-llvmjit-13.20-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (756 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-llvmjit-14.17-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (509 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-llvmjit-16.8-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (676 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-1C-llvmjit-17.2-alt8.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (737 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-llvmjit-17.4-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (734 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.; 
warn	postgresql15-multicorn2-2.5-alt2.x86_64	Files /usr/lib64/pgsql/bitcode/multicorn/src/multicorn.bc /usr/lib64/pgsql/bitcode/multicorn/src/python.bc /usr/lib64/pgsql/bitcode/multicorn/src/query.bc conflict with the package postgresql13-multicorn2-2.5-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/multicorn/src/multicorn.bc /usr/lib64/pgsql/bitcode/multicorn/src/python.bc /usr/lib64/pgsql/bitcode/multicorn/src/query.bc conflict with the package postgresql14-multicorn2-2.5-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql15-orafce-4.14.3-alt1.x86_64	There are file conflicts with the package postgresql13-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (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.; There are file conflicts with the package postgresql14-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.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.; There are file conflicts with the package postgresql16-orafce-4.14.3-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.; There are file conflicts with the package postgresql17-orafce-4.14.3-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.; 
warn	postgresql15-perl-15.12-alt4.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.8-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.4-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.; 
warn	postgresql15-pg-auto-failover-2.2-alt1.x86_64	There are file conflicts with the package postgresql13-pg-auto-failover-2.2-alt1.x86_64, for example, /usr/bin/pg_autoctl (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.; There are file conflicts with the package postgresql14-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.; There are file conflicts with the package postgresql16-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.; There are file conflicts with the package postgresql17-1C-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.; 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.; 
warn	postgresql15-pg_checksums-1.2-alt2.x86_64	File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-1C-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql15-pg_cron-1.6.5-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql13-pg_cron-1.6.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.; 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 postgresql14-pg_cron-1.6.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.; There are file conflicts with the package postgresql16-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql17-1C-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql17-pg_cron-1.6.5-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.; 
warn	postgresql15-pg_partman-5.2.4-alt1.x86_64	There are file conflicts with the package postgresql13-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql14-pg_partman-5.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.; File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql16-pg_partman-5.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.; File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql17-pg_partman-5.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.; 
warn	postgresql15-pg_repack-1.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql14-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql16-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql17-1C-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql17-pg_repack-1.5.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.; 
warn	postgresql15-pgaudit-1.7.1-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql13-pgaudit-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.; File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql14-pgaudit-1.6.3-alt0.rc1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-pgaudit-16.1-alt0.rc1.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.; There are file conflicts with the package postgresql17-1C-pgaudit-17.1-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.; There are file conflicts with the package postgresql17-pgaudit-17.1-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.; 
warn	postgresql15-pgauditlogtofile-1.6.4-alt1.x86_64	There are file conflicts with the package postgresql14-pgauditlogtofile-1.6.4-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.; There are file conflicts with the package postgresql16-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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.; There are file conflicts with the package postgresql17-1C-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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.; There are file conflicts with the package postgresql17-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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.; 
warn	postgresql15-postgis-3.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (95 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (88 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (100 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (100 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.; 
warn	postgresql15-python-15.12-alt4.x86_64	Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql13-python-13.20-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.8-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql17-python-17.4-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.; 
warn	postgresql15-repmgr-5.5.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc /usr/lib64/pgsql/repmgr.so conflict with the package postgresql13-repmgr-5.5.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.; Files /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql14-repmgr-5.5.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.; Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql16-repmgr-5.5.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.; Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql17-repmgr-5.5.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.; 
warn	postgresql15-server-15.12-alt4.x86_64	There are file conflicts with the package postgresql13-server-13.20-alt4.x86_64, for example, /usr/bin/initdb (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-server-14.17-alt4.x86_64, for example, /usr/bin/initdb (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.; There are file conflicts with the package postgresql16-server-16.8-alt4.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.; There are file conflicts with the package postgresql17-server-17.4-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql15-tcl-15.12-alt4.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql13-tcl-13.20-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.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.17-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.; 
warn	postgresql15-tds_fdw-2.0.4-alt1.x86_64	There are file conflicts with the package postgresql13-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.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.; 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 postgresql14-tds_fdw-2.0.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.; 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.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.; There are file conflicts with the package postgresql17-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql15-timescaledb-2.17.2-alt1.x86_64	File /usr/share/pgsql/extension/timescaledb.control conflicts with the package postgresql13-timescaledb-2.15.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.; Files /usr/lib64/pgsql/timescaledb-2.17.2.so /usr/lib64/pgsql/timescaledb-tsl-2.17.2.so conflict with the package postgresql14-timescaledb-2.17.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.; 
warn	postgresql16-contrib-16.8-alt4.x86_64	There are file conflicts with the package postgresql13-contrib-13.20-alt4.x86_64, for example, /usr/bin/pgbench (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.; There are file conflicts with the package postgresql14-contrib-14.17-alt4.x86_64, for example, /usr/bin/pgbench (34 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-contrib-15.12-alt4.x86_64, for example, /usr/bin/pgbench (30 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-contrib-17.4-alt4.x86_64, for example, /usr/bin/oid2name (23 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.; 
warn	postgresql16-credcheck-3.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql13-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql14-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql15-credcheck-3.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.; 
warn	postgresql16-iplike-2.3.0-alt2.x86_64	File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql13-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql14-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql15-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql16-llvmjit-16.8-alt4.x86_64	There are file conflicts with the package postgresql13-llvmjit-13.20-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (780 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-llvmjit-14.17-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (722 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-llvmjit-15.12-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (676 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-1C-llvmjit-17.2-alt8.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (575 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-llvmjit-17.4-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (566 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.; 
warn	postgresql16-orafce-4.14.3-alt1.x86_64	There are file conflicts with the package postgresql13-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (23 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-orafce-4.14.3-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.; There are file conflicts with the package postgresql17-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce/alert.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.; 
warn	postgresql16-perl-16.8-alt4.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-perl-14.17-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.12-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.; 
warn	postgresql16-pg-auto-failover-2.2-alt1.x86_64	There are file conflicts with the package postgresql13-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.; There are file conflicts with the package postgresql14-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.; There are file conflicts with the package postgresql15-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.; There are file conflicts with the package postgresql17-1C-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.; 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.; 
warn	postgresql16-pg_checksums-1.2-alt2.x86_64	File /usr/bin/pg_checksums_ext conflicts with the package postgresql13-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql14-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql15-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-1C-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql17-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql16-pg_cron-1.6.5-alt1.x86_64	There are file conflicts with the package postgresql13-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql14-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql15-pg_cron-1.6.5-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.; Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql17-1C-pg_cron-1.6.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.; File /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc conflicts with the package postgresql17-pg_cron-1.6.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.; 
warn	postgresql16-pg_partman-5.2.4-alt1.x86_64	There are file conflicts with the package postgresql13-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql14-pg_partman-5.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.; File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql15-pg_partman-5.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.; File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql17-pg_partman-5.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.; 
warn	postgresql16-pg_repack-1.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql14-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql15-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql17-1C-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql17-pg_repack-1.5.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.; 
warn	postgresql16-pgaudit-16.1-alt0.rc1.x86_64	There are file conflicts with the package postgresql13-pgaudit-1.5.3-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.; There are file conflicts with the package postgresql14-pgaudit-1.6.3-alt0.rc1.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.; There are file conflicts with the package postgresql15-pgaudit-1.7.1-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.; Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql17-1C-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.; Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so 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.; 
warn	postgresql16-pgauditlogtofile-1.6.4-alt1.x86_64	There are file conflicts with the package postgresql14-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.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.; There are file conflicts with the package postgresql15-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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.; Files /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_log.bc conflict with the package postgresql17-1C-pgauditlogtofile-1.6.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.; Files /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_log.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_shmem.bc conflict with the package postgresql17-pgauditlogtofile-1.6.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.; 
warn	postgresql16-postgis-3.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (106 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (105 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (100 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (84 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.; 
warn	postgresql16-python-16.8-alt4.x86_64	Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql13-python-13.20-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql14-python-14.17-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.12-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.; 
warn	postgresql16-repmgr-5.5.0-alt1.x86_64	There are file conflicts with the package postgresql13-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql15-repmgr-5.5.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.; Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql17-repmgr-5.5.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.; 
warn	postgresql16-server-16.8-alt4.x86_64	There are file conflicts with the package postgresql13-server-13.20-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-server-14.17-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-server-15.12-alt4.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.; There are file conflicts with the package postgresql17-server-17.4-alt4.x86_64, for example, /usr/bin/initdb (24 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.; 
warn	postgresql16-tcl-16.8-alt4.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql13-tcl-13.20-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.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.17-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.; 
warn	postgresql16-tds_fdw-2.0.4-alt1.x86_64	There are file conflicts with the package postgresql13-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.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.; 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 postgresql14-tds_fdw-2.0.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.; 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 postgresql15-tds_fdw-2.0.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.; There are file conflicts with the package postgresql17-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql16-timescaledb-2.17.2-alt1.x86_64	File /usr/share/pgsql/extension/timescaledb.control conflicts with the package postgresql13-timescaledb-2.15.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.; Files /usr/lib64/pgsql/timescaledb-2.17.2.so /usr/lib64/pgsql/timescaledb-tsl-2.17.2.so conflict with the package postgresql14-timescaledb-2.17.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.; 
warn	postgresql17-1C-contrib-17.2-alt8.x86_64	File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.20-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.; 
warn	postgresql17-1C-credcheck-3.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql13-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql14-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql15-credcheck-3.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.; 
warn	postgresql17-1C-llvmjit-17.2-alt8.x86_64	There are file conflicts with the package postgresql13-llvmjit-13.20-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (786 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-llvmjit-14.17-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (750 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-llvmjit-15.12-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (737 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-llvmjit-16.8-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (575 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-llvmjit-17.4-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_selfuncs.bc (222 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.; 
warn	postgresql17-1C-pg-auto-failover-2.2-alt1.x86_64	There are file conflicts with the package postgresql13-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.; There are file conflicts with the package postgresql14-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.; There are file conflicts with the package postgresql15-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.; There are file conflicts with the package postgresql16-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.; 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 (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.; 
warn	postgresql17-1C-pg_checksums-1.2-alt2.x86_64	File /usr/bin/pg_checksums_ext conflicts with the package postgresql13-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql14-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql15-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql17-1C-pg_cron-1.6.5-alt1.x86_64	There are file conflicts with the package postgresql13-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql14-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql15-pg_cron-1.6.5-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.; Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql16-pg_cron-1.6.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.; Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql17-pg_cron-1.6.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.; 
warn	postgresql17-1C-pg_repack-1.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql14-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql15-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql16-pg_repack-1.5.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.; 
warn	postgresql17-1C-pgaudit-17.1-alt1.x86_64	There are file conflicts with the package postgresql13-pgaudit-1.5.3-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.; There are file conflicts with the package postgresql14-pgaudit-1.6.3-alt0.rc1.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.; There are file conflicts with the package postgresql15-pgaudit-1.7.1-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.; Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql16-pgaudit-16.1-alt0.rc1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts 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.; 
warn	postgresql17-1C-pgauditlogtofile-1.6.4-alt1.x86_64	There are file conflicts with the package postgresql14-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.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.; There are file conflicts with the package postgresql15-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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.; Files /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_log.bc conflict with the package postgresql16-pgauditlogtofile-1.6.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.; Files /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_log.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_shmem.bc conflict with the package postgresql17-pgauditlogtofile-1.6.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.; 
warn	postgresql17-contrib-17.4-alt4.x86_64	There are file conflicts with the package postgresql13-contrib-13.20-alt4.x86_64, for example, /usr/bin/oid2name (43 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-contrib-14.17-alt4.x86_64, for example, /usr/bin/oid2name (40 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-contrib-15.12-alt4.x86_64, for example, /usr/bin/oid2name (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-contrib-16.8-alt4.x86_64, for example, /usr/bin/oid2name (23 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.; 
warn	postgresql17-credcheck-3.0-alt1.x86_64	Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql13-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql14-credcheck-3.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.; Files /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql15-credcheck-3.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.; 
warn	postgresql17-iplike-2.3.0-alt2.x86_64	File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql13-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql14-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/iplike.so conflicts with the package postgresql15-iplike-2.3.0-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql17-llvmjit-17.4-alt4.x86_64	There are file conflicts with the package postgresql13-llvmjit-13.20-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (785 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-llvmjit-14.17-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (748 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-llvmjit-15.12-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (734 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-llvmjit-16.8-alt4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (566 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-1C-llvmjit-17.2-alt8.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_selfuncs.bc (222 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.; 
warn	postgresql17-orafce-4.14.3-alt1.x86_64	There are file conflicts with the package postgresql13-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce.index.bc (23 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-orafce-4.14.3-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.; There are file conflicts with the package postgresql16-orafce-4.14.3-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/orafce/alert.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.; 
warn	postgresql17-perl-17.4-alt4.x86_64	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-perl-14.17-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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.12-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.; 
warn	postgresql17-pg-auto-failover-2.2-alt1.x86_64	There are file conflicts with the package postgresql13-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.; There are file conflicts with the package postgresql14-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.; There are file conflicts with the package postgresql15-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.; There are file conflicts with the package postgresql16-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.; 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 (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.; 
warn	postgresql17-pg_checksums-1.2-alt2.x86_64	File /usr/bin/pg_checksums_ext conflicts with the package postgresql13-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql14-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql15-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/bin/pg_checksums_ext conflicts with the package postgresql16-pg_checksums-1.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	postgresql17-pg_cron-1.6.5-alt1.x86_64	There are file conflicts with the package postgresql13-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql14-pg_cron-1.6.5-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.; There are file conflicts with the package postgresql15-pg_cron-1.6.5-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.; File /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc conflicts with the package postgresql16-pg_cron-1.6.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.; Files /usr/lib64/pgsql/bitcode/pg_cron/src/job_metadata.bc /usr/lib64/pgsql/bitcode/pg_cron/src/pg_cron.bc /usr/lib64/pgsql/bitcode/pg_cron/src/task_states.bc conflict with the package postgresql17-1C-pg_cron-1.6.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.; 
warn	postgresql17-pg_partman-5.2.4-alt1.x86_64	There are file conflicts with the package postgresql13-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (85 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc /usr/lib64/pgsql/pg_partman_bgw.so conflict with the package postgresql14-pg_partman-5.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.; File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql15-pg_partman-5.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.; File /usr/lib64/pgsql/bitcode/src/pg_partman_bgw/src/pg_partman_bgw.bc conflicts with the package postgresql16-pg_partman-5.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.; 
warn	postgresql17-pg_repack-1.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-pg_repack-1.5.2-alt1.x86_64, for example, /usr/bin/pg_repack (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql14-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql15-pg_repack-1.5.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.; File /usr/lib64/pgsql/bitcode/pg_repack/repack.bc conflicts with the package postgresql16-pg_repack-1.5.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.; 
warn	postgresql17-pgaudit-17.1-alt1.x86_64	There are file conflicts with the package postgresql13-pgaudit-1.5.3-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.; There are file conflicts with the package postgresql14-pgaudit-1.6.3-alt0.rc1.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.; There are file conflicts with the package postgresql15-pgaudit-1.7.1-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.; Files /usr/lib64/pgsql/bitcode/pgaudit.index.bc /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc /usr/lib64/pgsql/pgaudit.so conflict with the package postgresql16-pgaudit-16.1-alt0.rc1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql17-1C-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.; 
warn	postgresql17-pgauditlogtofile-1.6.4-alt1.x86_64	There are file conflicts with the package postgresql14-pgauditlogtofile-1.6.4-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.; There are file conflicts with the package postgresql15-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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.; Files /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_log.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_shmem.bc conflict with the package postgresql16-pgauditlogtofile-1.6.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.; Files /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_log.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_shmem.bc conflict with the package postgresql17-1C-pgauditlogtofile-1.6.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.; 
warn	postgresql17-postgis-3.5.2-alt1.x86_64	There are file conflicts with the package postgresql13-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (106 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (105 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (100 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (84 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.; 
warn	postgresql17-python-17.4-alt4.x86_64	Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql13-python-13.20-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql14-python-14.17-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.; File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.12-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.; 
warn	postgresql17-repmgr-5.5.0-alt1.x86_64	There are file conflicts with the package postgresql13-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-repmgr-5.5.0-alt1.x86_64, for example, /usr/bin/repmgr (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql15-repmgr-5.5.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.; Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql16-repmgr-5.5.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.; 
warn	postgresql17-server-17.4-alt4.x86_64	There are file conflicts with the package postgresql13-server-13.20-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-server-14.17-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-server-15.12-alt4.x86_64, for example, /etc/rc.d/init.d/postgresql (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-server-16.8-alt4.x86_64, for example, /usr/bin/initdb (24 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.; 
warn	postgresql17-tcl-17.4-alt4.x86_64	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql13-tcl-13.20-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.; File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql14-tcl-14.17-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.; 
warn	postgresql17-tds_fdw-2.0.4-alt1.x86_64	There are file conflicts with the package postgresql13-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-tds_fdw-2.0.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/tds_fdw.index.bc (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	pve-lxc-6.0.0-alt2.x86_64	Files /usr/share/lxc/templates/lxc-local /usr/share/lxc/templates/lxc-oci conflict with the package lxc-templates-6.0.3-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	pve-qemu-common-9.2.0-alt5.x86_64	Files /usr/share/qemu/hppa-firmware.img /usr/share/qemu/hppa-firmware64.img conflict with the package qemu-system-hppa-core-9.1.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.; File /usr/share/qemu/trace-events-all conflicts with the package qemu-tools-9.1.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.; 
warn	pve-qemu-system-9.2.0-alt5.x86_64	Files /usr/libexec/qemu-bridge-helper /usr/share/man/man1/qemu.1.xz conflict with the package qemu-common-9.1.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.; File /usr/libexec/vhost-user-gpu conflicts with the package qemu-device-display-vhost-user-gpu-9.1.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.; Files /usr/bin/qemu-storage-daemon /usr/share/man/man1/qemu-storage-daemon.1.xz /usr/share/man/man7/qemu-storage-daemon-qmp-ref.7.xz conflict with the package qemu-img-9.1.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.; File /usr/bin/qemu-system-aarch64 conflicts with the package qemu-system-aarch64-core-9.1.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.; File /usr/bin/qemu-system-x86_64 conflicts with the package qemu-system-x86-core-9.1.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.; File /usr/bin/qemu-vmsr-helper conflicts with the package qemu-vmsr-helper-9.1.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.; 
warn	python3-module-facebook-sdk-1.0.0-alt2.noarch	There are file conflicts with the package python3-module-tornado-facebook-sdk-0.1.0-alt2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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.; 
warn	python3-module-geventhttpclient-facebook-0.4.4-alt2.noarch	There are file conflicts with the package python3-module-requests-facebook-0.4.0-alt2.noarch, for example, /usr/lib/python3/site-packages/__pycache__/facebook.cpython-37.opt-1.pyc (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.; 
warn	python3-module-kivy-garden-0.1.4-alt2.noarch	File /usr/bin/garden conflicts with the package garden-1.0.9-alt1_18.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.; 
warn	python3-module-ly-0.9.8-alt1.noarch	File /usr/bin/ly conflicts with the package ly-0.6.0-alt0.g2ca870c.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.; 
warn	python3-module-munge-1.3.0-alt1.noarch	File /usr/bin/munge conflicts with the package munge-0.5.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.; 
warn	python3-module-pyproject-fmt-1.8.0-alt1.noarch	File /usr/bin/pyproject-fmt conflicts with the package python3-module-pyproject-parser-0.11.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-pyproject-parser-0.11.1-alt1.noarch	File /usr/bin/pyproject-fmt conflicts with the package python3-module-pyproject-fmt-1.8.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-radon-6.0.1-alt1.noarch	File /usr/bin/radon conflicts with the package nfft-3.2.3-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-requests-facebook-0.4.0-alt2.noarch	There are file conflicts with the package python3-module-geventhttpclient-facebook-0.4.4-alt2.noarch, for example, /usr/lib/python3/site-packages/__pycache__/facebook.cpython-37.opt-1.pyc (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.; 
warn	python3-module-servicemanager-2.0.7-alt1.noarch	File /usr/bin/sm conflicts with the package screen-message-0.6-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	python3-module-tornado-facebook-sdk-0.1.0-alt2.noarch	There are file conflicts with the package python3-module-facebook-sdk-1.0.0-alt2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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.; 
warn	qemu-common-9.1.2-alt1.x86_64	Files /usr/libexec/qemu-bridge-helper /usr/share/man/man1/qemu.1.xz conflict with the package pve-qemu-system-9.2.0-alt5.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.; 
warn	qemu-device-display-vhost-user-gpu-9.1.2-alt1.x86_64	File /usr/libexec/vhost-user-gpu conflicts with the package pve-qemu-system-9.2.0-alt5.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.; 
warn	qemu-img-9.1.2-alt1.x86_64	Files /usr/bin/qemu-storage-daemon /usr/share/man/man1/qemu-storage-daemon.1.xz /usr/share/man/man7/qemu-storage-daemon-qmp-ref.7.xz conflict with the package pve-qemu-system-9.2.0-alt5.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.; 
warn	qemu-system-aarch64-core-9.1.2-alt1.x86_64	File /usr/bin/qemu-system-aarch64 conflicts with the package pve-qemu-system-9.2.0-alt5.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.; 
warn	qemu-system-hppa-core-9.1.2-alt1.x86_64	Files /usr/share/qemu/hppa-firmware.img /usr/share/qemu/hppa-firmware64.img conflict with the package pve-qemu-common-9.2.0-alt5.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.; 
warn	qemu-system-x86-core-9.1.2-alt1.x86_64	File /usr/bin/qemu-system-x86_64 conflicts with the package pve-qemu-system-9.2.0-alt5.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.; 
warn	qemu-tools-9.1.2-alt1.x86_64	File /usr/share/qemu/trace-events-all conflicts with the package pve-qemu-common-9.2.0-alt5.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.; 
warn	qemu-vmsr-helper-9.1.2-alt1.x86_64	File /usr/bin/qemu-vmsr-helper conflicts with the package pve-qemu-system-9.2.0-alt5.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.; 
warn	racket-main-8.8-alt1.x86_64	File /usr/bin/slideshow conflicts with the package batik-slideshow-1.14-alt1_3jpp11.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	rosenpass-0.2.1-alt1.x86_64	File /usr/bin/rp conflicts with the package RTags-2.41-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	rpm-build-fedora-compat-fonts-2.0.5-alt2_11.noarch	There are file conflicts with the package fontpackages-devel-1.44-alt8_24.noarch, for example, /usr/share/fontconfig/templates/basic-font-template.conf (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.; 
warn	rx-etersoft-1.5.2-alt2.x86_64	File /usr/bin/nxdialog conflicts with the package nxdialog-3.5.99.26.1-alt3.2.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.; 
warn	screen-message-0.6-alt3.x86_64	File /usr/share/man/man1/sm.1.xz conflicts with the package inn-2.7.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.; File /usr/bin/sm conflicts with the package python3-module-servicemanager-2.0.7-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	sendmail-devel-8.18.1-alt1.x86_64	Files /usr/include/libmilter/mfapi.h /usr/include/libmilter/mfdef.h /usr/include/libmilter/milter.h conflict with the package libmilter-devel-static-8.14.3_1-alt1_12.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.; 
warn	shared-color-profiles-0.1.5-alt1.noarch	File /usr/share/color/icc/bluish.icc conflicts with the package xcalib-0.8-alt3.qa1.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.; 
warn	shared-mime-info-2.4-alt1.x86_64	There are file conflicts with the package liblcf0-0.7.0-alt1_3.x86_64, for example, /usr/share/mime/globs (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.; 
warn	sl-5.02-alt1.x86_64	Files /usr/bin/sl /usr/share/man/man1/sl.1.xz conflict with the package codetest_sl-1.6-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	snapd-glib-2-devel-1.66-alt1.x86_64	There are file conflicts with the package snapd-glib-devel-1.65-alt2.x86_64, for example, /usr/share/gtk-doc/html/snapd-glib/SnapdTask.html (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.; 
warn	snapd-glib-devel-1.65-alt2.x86_64	There are file conflicts with the package snapd-glib-2-devel-1.66-alt1.x86_64, for example, /usr/share/gtk-doc/html/snapd-glib/SnapdTask.html (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.; 
warn	soundconverter-4.0.5-alt1.noarch	File /usr/share/glib-2.0/schemas/gschemas.compiled conflicts with the package oregano-0.84.43-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	syslinux-4.04-alt19.x86_64	Files /usr/bin/lss16toppm /usr/bin/ppmtolss16 /usr/bin/syslinux conflict with the package syslinux1-1.62-alt4.1.qa1.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.; 
warn	syslinux1-1.62-alt4.1.qa1.x86_64	Files /usr/bin/lss16toppm /usr/bin/ppmtolss16 /usr/bin/syslinux conflict with the package syslinux-4.04-alt19.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.; 
warn	task-core-2.5.1-alt4.x86_64	File /usr/bin/task conflicts with the package go-task-3.19.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.; 
warn	tea-62.0.2-alt1.x86_64	File /usr/bin/tea conflicts with the package gitea-tea-0.9.2-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tionix-vdi-client-2.6.0-alt5.1.noarch	File /etc/X11/profile.d/zdg-user-dirs-install.sh conflicts with the package livecd-install-0.9.21-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tsugaru-tests-20230113-alt2.x86_64	File /usr/bin/relpath conflicts with the package fpc-utils-3.2.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.; File /usr/bin/wildcard conflicts with the package wildcard-0.3.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.; 
warn	volumes-profile-alt-education-11.0-alt4.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-alt-server-1.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-alt-server-v-1.1-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-alt-workstation-1.1-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-centaurus-0.14-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-cliff-server-0.18-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-cliff-workstation-0.5-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-jeos-0.2.1-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-kdesktop-0.13.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-lite-0.4.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-master-0.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	volumes-profile-regular-0.5.2-alt1.noarch	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-education-11.0-alt4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-1.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-server-v-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-alt-workstation-1.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.14-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.18-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-workstation-0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.2.1-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	wakeonlan-0.42-alt1.noarch	File /usr/bin/wakeonlan conflicts with the package java-wakeonlan-1.0.0-alt1_17jpp11.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	webhook-2.8.1-alt2.1.x86_64	File /usr/bin/webhook conflicts with the package cert-manager-1.14.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.; 
warn	wildcard-0.3.3-alt1.x86_64	File /usr/bin/wildcard conflicts with the package tsugaru-tests-20230113-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	xcalib-0.8-alt3.qa1.x86_64	File /usr/share/color/icc/bluish.icc conflicts with the package shared-color-profiles-0.1.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	xfreerdp3-3.14.1-alt2.x86_64	File /usr/bin/xfreerdp conflicts with the package baikal-openuds-0.0.3-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	yadm-3.2.2-alt1.noarch	File /usr/share/fish/completions/yadm.fish conflicts with the package fish-4.0.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.;