warn 3proxy-0.6.1-alt2.x86_64 File /usr/bin/proxy conflicts with the package libproxy-tools-0.4.17-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 LibreOffice-integrated-7.4.2.3-alt4.x86_64 File /usr/share/man/man1/unopkg.1.xz conflicts with the package LibreOffice-still-common-24.8.5.2-alt1.p10.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 LibreOffice-still-common-24.8.5.2-alt1.p10.1.x86_64 File /usr/share/man/man1/unopkg.1.xz conflicts with the package LibreOffice-integrated-7.4.2.3-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 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.; File /usr/bin/blink conflicts with the package blink-qt-5.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 MySQL-server-8.0.40-alt1.x86_64 File /usr/share/man/man8/mysqld.8.xz conflicts with the package mariadb-client-10.6.21-alt1.x86_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 SNNS-4.3-alt1.1.1.1.x86_64 File /usr/bin/analyze conflicts with the package hunspell-utils-1.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.; 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-setup-0.4.1-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-p10-20210721-alt2.noarch File /etc/altlinux-release conflicts with the package branding-alt-education-release-10.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/altlinux-release conflicts with the package branding-alt-platform-builder-release-10.1-alt0.p10.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-alt-server-release-10.4-alt3.p10.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-v-release-10.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.; File /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-10-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.; File /etc/altlinux-release conflicts with the package branding-alt-workstation-release-10.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/altlinux-release conflicts with the package branding-myoffice-plus-release-1.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 /etc/altlinux-release conflicts with the package branding-simply-linux-release-10.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/altlinux-release conflicts with the package branding-uzguard-server-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-uzguard-workstation-release-1.0-alt0.2.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-10.4.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 altlinux-release-p8-20160414-alt1.noarch File /etc/altlinux-release conflicts with the package branding-alt-container-release-10-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-alt-education-release-10.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/altlinux-release conflicts with the package branding-alt-platform-builder-release-10.1-alt0.p10.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-alt-server-release-10.4-alt3.p10.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-v-release-10.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.; File /etc/altlinux-release conflicts with the package branding-alt-starterkit-release-10-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.; File /etc/altlinux-release conflicts with the package branding-alt-workstation-release-10.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/altlinux-release conflicts with the package branding-myoffice-plus-release-1.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 /etc/altlinux-release conflicts with the package branding-simply-linux-release-10.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/altlinux-release conflicts with the package branding-uzguard-server-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-uzguard-workstation-release-1.0-alt0.2.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-10.4.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 altlinux-release-sisyphus-20201124-alt1.noarch File /etc/altlinux-release conflicts with the package branding-alt-container-release-10-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-alt-platform-builder-release-10.1-alt0.p10.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-myoffice-plus-release-1.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 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.26.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 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-alt1.noarch File /usr/bin/xfreerdp conflicts with the package xfreerdp3-3.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 batik-slideshow-1.14-alt1_1jpp8.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-8.4.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 blink-qt-5.9.1-alt1.x86_64 File /usr/bin/blink 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 branding-alt-container-release-10-alt1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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 altlinux-release-sisyphus-20201124-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-release-10.4-alt1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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-10.4-alt1.x86_64 Files /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-workstation-mate-settings-10.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.; Files /etc/skel/.config/plasma-org.kde.plasma.desktop-appletsrc /etc/skel/.config/plasmashellrc conflict with the package branding-uzguard-workstation-kde-settings-1.0-alt0.2.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 /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-xalt-kworkstation-graphics-10.4.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 /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-platform-builder-release-10.1-alt0.p10.1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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 altlinux-release-sisyphus-20201124-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-10.4-alt3.p10.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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-v-release-10.4-alt2.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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-starterkit-release-10-alt6.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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-workstation-mate-settings-10.4-alt1.noarch Files /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-education-xfce-settings-10.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 /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-myoffice-plus-xfce-settings-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.; File /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-10.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 /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-uzguard-server-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.; Files /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-uzguard-workstation-xfce-settings-1.0-alt0.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 branding-alt-workstation-release-10.4-alt1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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-myoffice-plus-release-1.3-alt1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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 altlinux-release-sisyphus-20201124-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-myoffice-plus-xfce-settings-1.3-alt1.x86_64 Files /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-workstation-mate-settings-10.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.; Files /etc/skel/.config/plasma-org.kde.plasma.desktop-appletsrc /etc/skel/.config/plasmashellrc conflict with the package branding-uzguard-workstation-kde-settings-1.0-alt0.2.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 /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-xalt-kworkstation-graphics-10.4.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 /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.4-alt1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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.4-alt1.x86_64 File /etc/skel/.gtkrc-2.0 conflicts with the package branding-alt-workstation-mate-settings-10.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/skel/.gtkrc-2.0 conflicts with the package branding-xalt-kworkstation-graphics-10.4.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 branding-uzguard-server-release-1.0-alt0.1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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-uzguard-server-xfce-settings-1.0-alt0.1.x86_64 Files /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-workstation-mate-settings-10.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.; Files /etc/skel/.config/plasma-org.kde.plasma.desktop-appletsrc /etc/skel/.config/plasmashellrc conflict with the package branding-uzguard-workstation-kde-settings-1.0-alt0.2.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 /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-xalt-kworkstation-graphics-10.4.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 /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-uzguard-workstation-kde-settings-1.0-alt0.2.noarch Files /etc/skel/.config/plasma-org.kde.plasma.desktop-appletsrc /etc/skel/.config/plasmashellrc conflict with the package branding-alt-education-xfce-settings-10.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 /etc/skel/.config/plasma-org.kde.plasma.desktop-appletsrc /etc/skel/.config/plasmashellrc conflict with the package branding-myoffice-plus-xfce-settings-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.; Files /etc/skel/.config/plasma-org.kde.plasma.desktop-appletsrc /etc/skel/.config/plasmashellrc conflict with the package branding-uzguard-server-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 branding-uzguard-workstation-release-1.0-alt0.2.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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-uzguard-workstation-xfce-settings-1.0-alt0.2.x86_64 Files /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-workstation-mate-settings-10.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.; Files /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-xalt-kworkstation-graphics-10.4.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 /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-xalt-kworkstation-graphics-10.4.0-alt1.noarch Files /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-alt-education-xfce-settings-10.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 /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-myoffice-plus-xfce-settings-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.; File /etc/skel/.gtkrc-2.0 conflicts with the package branding-simply-linux-xfce-settings-10.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 /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-uzguard-server-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.; Files /etc/skel/.config/autostart/tracker-store.desktop /etc/skel/.config/gtk-3.0/settings.ini /etc/skel/.gtkrc-2.0 conflict with the package branding-uzguard-workstation-xfce-settings-1.0-alt0.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 branding-xalt-kworkstation-release-10.4.0-alt1.noarch File /etc/altlinux-release conflicts with the package altlinux-release-p10-20210721-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 /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-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 bumper-0.1.13-alt1.noarch File /usr/bin/bump conflicts with the package mesa-demos-8.4.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 camotics-1.2.1-alt2.20191008.x86_64 File /usr/bin/planner conflicts with the package planner-0.14.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 can-uilts-v2019.00.0-alt1.x86_64 File /usr/bin/jcat conflicts with the package sleuthkit-4.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.; warn clean-3.0-alt1.7.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 cmark-0.29.0-alt1.1.x86_64 File /usr/bin/cmark conflicts with the package python-module-commonmark-0.8.1-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 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 custom-libgccjit13-devel-13.2.1-alt2.p10.1.x86_64 Files /usr/include/libgccjit++.h /usr/include/libgccjit.h conflict with the package libgccjit10-devel-10.3.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 db4.7-utils-4.7.25-alt11.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-alt4.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-alt6.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 devscripts-2.19.7-alt2.x86_64 File /usr/bin/dget conflicts with the package dmd-2.097.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 dmd-2.097.0-alt1.x86_64 File /usr/bin/dget conflicts with the package devscripts-2.19.7-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 extlinux-6.04.pre3-alt3.x86_64 File /usr/share/man/man1/extlinux.1.xz conflicts with the package syslinux-4.04-alt18.x86_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 fbterm-1.7-alt3.x86_64 File /usr/share/terminfo/f/fbterm conflicts with the package terminfo-extra-6.3.20220618-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 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 fuse-obexfs-0.11-alt0.rc3.qa2.x86_64 Files /usr/bin/obexautofs /usr/bin/obexfs conflict with the package obexftp-0.24.2-alt2.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 garden-1.0.9-alt1_11.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-fortran-doc-10.3.1-alt2.x86_64 File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.3-doc-4.3.2-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 /usr/share/info/gfortran.info.xz conflicts with the package gcc4.4-doc-4.4.7-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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.5-doc-4.5.4-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.6-doc-4.6.3-alt14.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/info/gfortran.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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/info/gfortran.info.xz conflicts with the package gcc4.8-doc-4.8.2-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.9-doc-4.9.2-alt9.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/info/gfortran.info.xz conflicts with the package gcc5-doc-5.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt7.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-go-doc-10.3.1-alt2.x86_64 File /usr/share/info/gccgo.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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 gcc4.3-doc-4.3.2-alt23.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc4.4-doc-4.4.7-alt6.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc4.5-doc-4.5.4-alt7.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc4.6-doc-4.6.3-alt14.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc4.7-doc-4.7.2-alt13.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gccgo.info.xz conflicts with the package gcc10-go-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gccgo.info.xz conflicts with the package gcc7-go-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gccgo.info.xz conflicts with the package gcc8-go-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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.; File /usr/share/info/gccgo.info.xz conflicts with the package gcc9-go-doc-9.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 gcc4.8-doc-4.8.2-alt7.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc4.9-doc-4.9.2-alt9.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc5-doc-5.3.1-alt9.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc6-doc-6.3.1-alt7.noarch File /usr/share/info/gfortran.info.xz conflicts with the package gcc10-fortran-doc-10.3.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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc7-fortran-doc-7.3.1-alt10.x86_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/gfortran.info.xz conflicts with the package gcc8-fortran-doc-8.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/gfortran.info.xz conflicts with the package gcc9-fortran-doc-9.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 gcc7-fortran-doc-7.3.1-alt10.x86_64 File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.3-doc-4.3.2-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 /usr/share/info/gfortran.info.xz conflicts with the package gcc4.4-doc-4.4.7-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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.5-doc-4.5.4-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.6-doc-4.6.3-alt14.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/info/gfortran.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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/info/gfortran.info.xz conflicts with the package gcc4.8-doc-4.8.2-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.9-doc-4.9.2-alt9.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/info/gfortran.info.xz conflicts with the package gcc5-doc-5.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt7.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 gcc7-go-doc-7.3.1-alt10.x86_64 File /usr/share/info/gccgo.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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 gcc8-fortran-doc-8.4.1-alt1.x86_64 File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.3-doc-4.3.2-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 /usr/share/info/gfortran.info.xz conflicts with the package gcc4.4-doc-4.4.7-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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.5-doc-4.5.4-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.6-doc-4.6.3-alt14.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/info/gfortran.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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/info/gfortran.info.xz conflicts with the package gcc4.8-doc-4.8.2-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.9-doc-4.9.2-alt9.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/info/gfortran.info.xz conflicts with the package gcc5-doc-5.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt7.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 gcc8-go-doc-8.4.1-alt1.x86_64 File /usr/share/info/gccgo.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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 gcc9-fortran-doc-9.3.1-alt3.x86_64 File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.3-doc-4.3.2-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 /usr/share/info/gfortran.info.xz conflicts with the package gcc4.4-doc-4.4.7-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.; File /usr/share/info/gfortran.info.xz conflicts with the package gcc4.5-doc-4.5.4-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.6-doc-4.6.3-alt14.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/info/gfortran.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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/info/gfortran.info.xz conflicts with the package gcc4.8-doc-4.8.2-alt7.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/info/gfortran.info.xz conflicts with the package gcc4.9-doc-4.9.2-alt9.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/info/gfortran.info.xz conflicts with the package gcc5-doc-5.3.1-alt9.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/info/gfortran.info.xz conflicts with the package gcc6-doc-6.3.1-alt7.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 gcc9-go-doc-9.3.1-alt3.x86_64 File /usr/share/info/gccgo.info.xz conflicts with the package gcc4.7-doc-4.7.2-alt13.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-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/config.h conflicts with the package libbobpp-devel-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.; File /usr/include/mkdio.h conflicts with the package libdiscount-devel-2.2.3a-alt1.git.13.gddf8b6f.x86_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-alt1.x86_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.5.6-alt1.noarch File /usr/include/msgpack/sysdep.h conflicts with the package libmsgpack-c-devel-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 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.noarch File /usr/include/unicode/ustring.h conflicts with the package libicu-devel-6.9.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 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 glusterfs8-georeplication-8.4-alt1.x86_64 There are file conflicts with the package glusterfs9-georeplication-9.3-alt1.x86_64, for example, /usr/lib/glusterfs/python/syncdaemon/__pycache__/master.cpython-39.opt-1.pyc (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn glusterfs9-georeplication-9.3-alt1.x86_64 There are file conflicts with the package glusterfs8-georeplication-8.4-alt1.x86_64, for example, /usr/lib/glusterfs/python/syncdaemon/__pycache__/master.cpython-39.opt-1.pyc (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn go-task-2.4.0-alt1.x86_64 File /usr/bin/task conflicts with the package task-core-2.5.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 hunspell-utils-1.7.2-alt1.x86_64 File /usr/bin/analyze conflicts with the package SNNS-4.3-alt1.1.1.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 inn-2.6.4-alt1.x86_64 File /usr/share/man/man1/sm.1.xz conflicts with the package screen-message-0.6-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 installer-common-stage2-1.14.7-alt5.p10.x86_64 File /usr/sbin/postinstall conflicts with the package installworld-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 installer-distro-alt-server-v-stage2-10.1.0-alt1.noarch Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-10.4.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-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-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-centaurus-stage2-10.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/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh /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.0-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/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-cliff-stage2-10.0-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.; There are file conflicts with the package installer-distro-education-stage2-10.0-alt6.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-jeos-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-kworkstation-stage2-10.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/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-regular-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-server-light-stage2-8.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/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; warn installer-distro-alt-workstation-stage2-10.4.0-alt1.noarch Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-server-v-stage2-10.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/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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-centaurus-stage2-10.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/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-cliff-common-10.0-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/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-cliff-stage2-10.0-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.; There are file conflicts with the package installer-distro-education-stage2-10.0-alt6.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-kworkstation-stage2-10.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/install2/installer-steps conflicts with the package installer-distro-server-light-stage2-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.; 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-10.7.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.; warn installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch There are file conflicts with the package installer-distro-alt-server-v-stage2-10.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/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-10.4.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.; There are file conflicts with the package installer-distro-centaurus-stage2-10.4-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.0-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/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.0-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.; There are file conflicts with the package installer-distro-education-stage2-10.0-alt6.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-jeos-stage2-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.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.1-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.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-server-light-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; 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-server-v-stage2-10.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-alt-workstation-stage2-10.4.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-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-10.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/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.0-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/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-education-stage2-10.0-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-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.; 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.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/install2/installer-steps conflicts with the package installer-distro-regular-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-server-light-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; 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-server-v-stage2-10.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-alt-workstation-stage2-10.4.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.; 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-10.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/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.0-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/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-education-stage2-10.0-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-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.; 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.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/install2/installer-steps conflicts with the package installer-distro-regular-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-server-light-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; warn installer-distro-centaurus-stage2-10.4-alt1.x86_64 Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-server-v-stage2-10.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/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-10.4.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-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/01-remove-installer-server-pkgs.sh /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.0-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/share/install2/alterator-menu/module-expert-list conflicts with the package installer-distro-cliff-stage2-10.0-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.; There are file conflicts with the package installer-distro-education-stage2-10.0-alt6.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-jeos-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-regular-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-server-light-stage2-8.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/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; warn installer-distro-cliff-common-10.0-alt8.x86_64 Files /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh /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-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/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-alt-workstation-stage2-10.4.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/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/01-remove-installer-server-pkgs.sh /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-10.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/share/install2/preinstall.d/80-setup-user-groups conflicts with the package installer-distro-education-stage2-10.0-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.; Files /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh /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.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/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflicts with the package installer-distro-server-light-stage2-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.; 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.; warn installer-distro-cliff-stage2-10.0-alt8.x86_64 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-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 conflict with the package installer-distro-alt-workstation-stage2-10.4.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-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.; File /usr/share/install2/alterator-menu/module-expert-list conflicts with the package installer-distro-centaurus-stage2-10.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/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-education-stage2-10.0-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.; 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-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/alterator-menu/module-expert-list conflicts with the package installer-distro-kworkstation-stage2-10.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/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-regular-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-server-light-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; warn installer-distro-education-stage2-10.0-alt6.x86_64 There are file conflicts with the package installer-distro-alt-server-v-stage2-10.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.; There are file conflicts with the package installer-distro-alt-workstation-stage2-10.4.0-alt1.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-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-10.4-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.0-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/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.0-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/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-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-kworkstation-stage2-10.1-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.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-server-light-stage2-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.; There are file conflicts with the package installer-distro-simply-linux-stage2-10.7.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (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 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.; warn installer-distro-jeos-stage2-0.1-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-server-v-stage2-10.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-alt-workstation-stage2-10.4.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-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-10.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/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.0-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/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-education-stage2-10.0-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.; 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.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/install2/installer-steps conflicts with the package installer-distro-regular-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-server-light-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; warn installer-distro-kworkstation-stage2-10.1-alt1.x86_64 Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-server-v-stage2-10.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/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-10.4.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-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/01-remove-installer-server-pkgs.sh /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.0-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/share/install2/alterator-menu/module-expert-list conflicts with the package installer-distro-cliff-stage2-10.0-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.; There are file conflicts with the package installer-distro-education-stage2-10.0-alt6.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-jeos-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-regular-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-server-light-stage2-8.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/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; warn installer-distro-regular-stage2-0.1-alt2.noarch 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-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-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 conflict with the package installer-distro-centaurus-stage2-10.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/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-cliff-stage2-10.0-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/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-education-stage2-10.0-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-kworkstation-stage2-10.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/install2/installer-steps conflicts with the package installer-distro-server-light-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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.; warn installer-distro-server-light-stage2-8.0-alt1.noarch There are file conflicts with the package installer-distro-alt-server-v-stage2-10.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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-alt-workstation-stage2-10.4.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-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-10.4-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/postinstall.d/01-remove-installer-server-pkgs.sh conflicts with the package installer-distro-cliff-common-10.0-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/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.0-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/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-education-stage2-10.0-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.; File /usr/share/install2/installer-steps conflicts with the package installer-distro-jeos-stage2-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.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.1-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.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-simply-linux-stage2-10.7.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.; warn installer-distro-simply-linux-stage2-10.7.0-alt1.noarch 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-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 /usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh conflict with the package installer-distro-alt-workstation-stage2-10.4.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-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-10.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/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-cliff-stage2-10.0-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.; There are file conflicts with the package installer-distro-education-stage2-10.0-alt6.x86_64, for example, /usr/share/install2/alterator-menu/module-expert-list (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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-jeos-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-kworkstation-stage2-10.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/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-regular-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-server-light-stage2-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.; 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.; warn installer-distro-token-desktop-live-0.1.1-alt5.noarch File /usr/share/livecd-install/alterator-menu/module-expert-list conflicts with the package installer-feature-simply-livecd-10.5.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 installer-distro-token-desktop-stage2-0.1.1-alt5.noarch There are file conflicts with the package installer-distro-alt-server-v-stage2-10.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/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-alt-workstation-stage2-10.4.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-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-10.4-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.0-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/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.0-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.; There are file conflicts with the package installer-distro-education-stage2-10.0-alt6.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-jeos-stage2-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.; There are file conflicts with the package installer-distro-kworkstation-stage2-10.1-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.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-server-light-stage2-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.; Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-simply-linux-stage2-10.7.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-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-simply-livecd-10.5.1-alt1.noarch File /usr/share/livecd-install/alterator-menu/module-expert-list conflicts with the package installer-distro-token-desktop-live-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-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 installworld-0.1-alt1.noarch File /usr/sbin/postinstall conflicts with the package installer-common-stage2-1.14.7-alt5.p10.x86_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 java-wakeonlan-1.0.0-alt1_17jpp11.noarch File /usr/bin/wakeonlan conflicts with the package wakeonlan-0.41.0.19.git41b636c-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 jpeginfo-1.6.1-alt1.x86_64 File /usr/bin/jpeginfo conflicts with the package libjpeg-utils-2.1.5.1-alt1.p10.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 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 libbobpp-devel-0.2.0-alt1.1.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.; 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.; warn libcpufreq-devel-008-alt3.x86_64 File /usr/include/cpufreq.h conflicts with the package libcpupower-devel-6.1-alt0.p10.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 libcpupower-devel-6.1-alt0.p10.1.x86_64 File /usr/include/cpufreq.h conflicts with the package libcpufreq-devel-008-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 libdiscount-devel-2.2.3a-alt1.git.13.gddf8b6f.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-10-devel-static-10.23-alt1.p10.4.x86_64 There are file conflicts with the package libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-13-devel-static-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-14-devel-static-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-15-1C-devel-static-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-15-devel-static-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-16-devel-static-16.8-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-17-devel-static-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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.; warn libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-13-devel-static-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-14-devel-static-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-15-1C-devel-static-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-15-devel-static-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-16-devel-static-16.8-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-17-devel-static-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/libecpg.a (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.; warn libecpg6-12-devel-static-12.22-alt0.p10.2.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-13-devel-static-13.20-alt0.p10.1.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-alt0.p10.1.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-1C-devel-static-15.12-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-13-devel-static-13.20-alt0.p10.1.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.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-alt0.p10.1.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-1C-devel-static-15.12-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.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-13-devel-static-13.20-alt0.p10.1.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-1C-devel-static-15.12-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-1C-devel-static-15.12-alt0.p10.1.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.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-13-devel-static-13.20-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-16-devel-static-16.8-alt0.p10.1.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-alt0.p10.1.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.; File /usr/lib64/libpq.a conflicts with the package libpq5-devel-static-17.4-alt0.p10.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 libecpg6-15-devel-static-15.12-alt0.p10.1.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.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-13-devel-static-13.20-alt0.p10.1.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-alt0.p10.1.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-1C-devel-static-15.12-alt0.p10.1.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-16-devel-static-16.8-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.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-13-devel-static-13.20-alt0.p10.1.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-alt0.p10.1.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-1C-devel-static-15.12-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.x86_64 There are file conflicts with the package libecpg6-10-devel-static-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-11-devel-static-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/libecpg.a (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 libecpg6-12-devel-static-12.22-alt0.p10.2.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-13-devel-static-13.20-alt0.p10.1.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-alt0.p10.1.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-1C-devel-static-15.12-alt0.p10.1.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-alt0.p10.1.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-alt0.p10.1.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 libgccjit10-devel-10.3.1-alt2.x86_64 Files /usr/include/libgccjit++.h /usr/include/libgccjit.h conflict with the package custom-libgccjit13-devel-13.2.1-alt2.p10.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 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 libgoogle-sparsehash-1.5.2-alt1.1.noarch There are file conflicts with the package sparsehash-devel-2.0.4-alt1.x86_64, for example, /usr/include/google/dense_hash_map (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 libgphobos10-devel-10.3.1-alt2.x86_64 File /usr/lib64/libgphobos.spec conflicts with the package libgphobos9-devel-9.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 libgphobos9-devel-9.3.1-alt3.x86_64 File /usr/lib64/libgphobos.spec conflicts with the package libgphobos10-devel-10.3.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 libgtk+extra2-devel-docs-2.1.2-alt3.noarch There are file conflicts with the package libgtkextra-x11-devel-3.3.4-alt2_4.x86_64, for example, /usr/share/gtk-doc/html/gtkextra/GtkPlotArray.html (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.; warn libgtkextra-x11-devel-3.3.4-alt2_4.x86_64 There are file conflicts with the package libgtk+extra2-devel-docs-2.1.2-alt3.noarch, for example, /usr/share/gtk-doc/html/gtkextra/GtkPlotArray.html (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.; warn libicu-devel-6.9.1-alt2.x86_64 File /usr/include/unicode/ustring.h conflicts with the package gem-unicode-devel-0.4.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.; warn libinn-devel-2.6.4-alt1.x86_64 File /usr/share/man/man3/list.3.xz conflicts with the package man-pages-5.12-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 libjpeg-utils-2.1.5.1-alt1.p10.2.x86_64 File /usr/bin/jpeginfo conflicts with the package jpeginfo-1.6.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn liblinebreak-devel-2.1-alt1.x86_64 Files /usr/include/linebreak.h /usr/include/linebreakdef.h conflict with the package libunibreak-devel-3.0-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.; Files /usr/include/linebreak.h /usr/include/linebreakdef.h conflict with the package libunibreak5-devel-5.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 liblog4cplus-devel-docs-2.0.6-alt1.noarch File /usr/share/man/man3/config.h.3.xz conflicts with the package libpgf-devel-6.14.12-alt1_17.x86_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_11.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 libmsgpack-c-devel-6.0.0-alt2.x86_64 File /usr/include/msgpack/sysdep.h conflicts with the package gem-msgpack-devel-1.5.6-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-6.14.12-alt1_17.x86_64 File /usr/share/man/man3/config.h.3.xz conflicts with the package liblog4cplus-devel-docs-2.0.6-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 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.; File /usr/include/config.h conflicts with the package libbobpp-devel-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 libpq5-devel-static-17.4-alt0.p10.1.x86_64 File /usr/lib64/libpq.a conflicts with the package libecpg6-15-1C-devel-static-15.12-alt0.p10.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 libproxy-tools-0.4.17-alt1.1.x86_64 File /usr/bin/proxy conflicts 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 libquvi-devel-0.4.1-alt2.1.x86_64 File /usr/share/man/man3/libquvi.3.xz conflicts with the package libquvi0.9-devel-0.9.4-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 libquvi0.9-devel-0.9.4-alt2.1.x86_64 File /usr/share/man/man3/libquvi.3.xz conflicts with the package libquvi-devel-0.4.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 libreadline-devel-7.0.3-alt3.x86_64 There are file conflicts with the package libreadline5-devel-5.2.14-alt6.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 libreadline-devel-static-7.0.3-alt3.x86_64 Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline5-devel-static-5.2.14-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 libreadline5-devel-5.2.14-alt6.x86_64 There are file conflicts with the package libreadline-devel-7.0.3-alt3.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-static-5.2.14-alt6.x86_64 Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline-devel-static-7.0.3-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 libsexpr-devel-1.3-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.4.1-alt3.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 libshout-idjc-devel-2.4.1-alt1_4.x86_64 File /usr/share/aclocal/shout.m4 conflicts with the package libshout2-devel-2.4.6-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 libshout2-devel-2.4.6-alt2.x86_64 File /usr/share/aclocal/shout.m4 conflicts with the package libshout-idjc-devel-2.4.1-alt1_4.x86_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 libticables-devel-1.3.4-alt1_1.x86_64 Files /usr/include/tilp2/ticables.h /usr/lib64/pkgconfig/ticables2.pc conflict with the package libticables2-devel-1.3.5-alt1_4.x86_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/locale/fr/LC_MESSAGES/libticables2.mo conflicts with the package libticables2-i18n-1.3.5-alt1_4.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 libticables2-devel-1.3.5-alt1_4.x86_64 Files /usr/include/tilp2/ticables.h /usr/lib64/pkgconfig/ticables2.pc conflict with the package libticables-devel-1.3.4-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 libticables2-i18n-1.3.5-alt1_4.noarch File /usr/share/locale/fr/LC_MESSAGES/libticables2.mo conflicts with the package libticables-devel-1.3.4-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 libunibreak-devel-3.0-alt3.x86_64 Files /usr/include/linebreak.h /usr/include/linebreakdef.h conflict with the package liblinebreak-devel-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 libunibreak5-devel-5.1-alt2.x86_64 Files /usr/include/linebreak.h /usr/include/linebreakdef.h conflict with the package liblinebreak-devel-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 livecd-0ad-0.2-alt1.noarch 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.; 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-10.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 /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-myoffice-plus-xfce-settings-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.; File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-uzguard-server-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/.gconf/apps/%gconf.xml conflicts with the package branding-uzguard-workstation-xfce-settings-1.0-alt0.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 livecd-install-0.9.21-alt1.noarch File /usr/share/alterator/steps/notes-license.desktop conflicts with the package alterator-setup-0.4.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 lxc-templates-4.0.12-alt3.noarch File /usr/share/lxc/templates/lxc-download conflicts with the package pve-lxc-5.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 man-pages-5.12-alt1.noarch File /usr/share/man/man3/list.3.xz conflicts with the package libinn-devel-2.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 mariadb-client-10.6.21-alt1.x86_64 File /usr/share/man/man8/mysqld.8.xz conflicts with the package MySQL-server-8.0.40-alt1.x86_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 marss-riscv-1.0a-alt1.x86_64 Files /usr/bin/build_filelist /usr/bin/splitimg conflict with the package tinyemu-20191221-alt1.x86_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.26.1-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.0-alt1.7.x86_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-8.4.0-alt1.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/bump conflicts with the package bumper-0.1.13-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/bin/poly conflicts with the package polyml-5.4.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.; File /usr/bin/gearbox conflicts with the package python3-module-gearbox-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.; warn mplayer-1.4-alt7.38313.1.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.4-alt7.38313.1.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 nfft-3.2.3-alt1.x86_64 File /usr/bin/radon conflicts with the package python3-module-radon-5.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 obexftp-0.24.2-alt2.6.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-alt1.x86_64 File /usr/share/glib-2.0/schemas/gschemas.compiled conflicts with the package soundconverter-4.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 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.4.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-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 perl-Math-Prime-Util-scripts-0.73-alt2.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 perl-pip-1.19-alt1.noarch File /usr/bin/pip conflicts with the package pip-22.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 pgpdump-0.33-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 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.; 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 pip-22.2.2-alt1.noarch File /usr/bin/pip conflicts with the package perl-pip-1.19-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 pks-db-0.9.6-alt4.x86_64 There are file conflicts with the package db4.7-utils-4.7.25-alt11.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-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.; There are file conflicts with the package db6.1-utils-6.1.19-alt6.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.33-alt1.x86_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 planner-0.14.6-alt3.x86_64 File /usr/bin/planner conflicts with the package camotics-1.2.1-alt2.20191008.x86_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 policycoreutils-sandbox-3.2-alt5.x86_64 File /usr/bin/sandbox conflicts with the package sandbox-2.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 polyml-5.4.1-alt4.x86_64 File /usr/bin/poly conflicts with the package mesa-demos-8.4.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 postgresql10-contrib-10.23-alt1.p10.4.x86_64 There are file conflicts with the package postgresql11-contrib-11.22-alt0.p10.4.x86_64, for example, /usr/bin/pg_standby (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 postgresql12-contrib-12.22-alt0.p10.2.x86_64, for example, /usr/bin/oid2name (39 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-contrib-13.20-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (73 file conflicts in 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/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql13-python-13.20-alt0.p10.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.; There are file conflicts with the package postgresql14-contrib-14.17-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (71 file conflicts in 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/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql14-python-14.17-alt0.p10.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.; There are file conflicts with the package postgresql15-contrib-15.12-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (71 file conflicts in 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/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql15-python-15.12-alt0.p10.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.; There are file conflicts with the package postgresql16-contrib-16.8-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (75 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql16-python-16.8-alt0.p10.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.; There are file conflicts with the package postgresql17-contrib-17.4-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (76 file conflicts in 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/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql17-python-17.4-alt0.p10.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 postgresql10-perl-10.23-alt1.p10.4.x86_64 File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql11-perl-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-perl-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/plperl.so (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-perl-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-perl-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-perl-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql16-perl-16.8-alt0.p10.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.; Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql17-perl-17.4-alt0.p10.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 postgresql10-pg_partman-4.7.4-alt1.x86_64 File /usr/share/pgsql/extension/pg_partman--4.7.4.sql conflicts with the package postgresql11-pg_partman-4.7.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/pg_partman_bgw.so /usr/share/pgsql/extension/pg_partman--4.7.4.sql conflict with the package postgresql12-pg_partman-4.7.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/pg_partman_bgw.so /usr/share/pgsql/extension/pg_partman--4.7.4.sql conflict with the package postgresql13-pg_partman-4.7.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 postgresql14-pg_partman-5.2.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (83 file conflicts in 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 (83 file conflicts in 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 (83 file conflicts in 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 (83 file conflicts in 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 postgresql10-python-10.23-alt1.p10.4.x86_64 File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql11-python-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql12-python-12.22-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql13-python-13.20-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql14-python-14.17-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql15-python-15.12-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql16-python-16.8-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql17-python-17.4-alt0.p10.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 postgresql10-server-10.23-alt1.p10.4.x86_64 There are file conflicts with the package postgresql11-server-11.22-alt0.p10.4.x86_64, for example, /lib/systemd/system/postgresql.service (49 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-server-12.22-alt0.p10.2.x86_64, for example, /lib/systemd/system/postgresql.service (89 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-server-13.20-alt0.p10.1.x86_64, for example, /lib/systemd/system/postgresql.service (634 file conflicts in 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-alt0.p10.1.x86_64, for example, /lib/systemd/system/postgresql.service (637 file conflicts in 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-alt0.p10.1.x86_64, for example, /lib/systemd/system/postgresql.service (638 file conflicts in 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-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (641 file conflicts in 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-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (641 file conflicts in 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 postgresql10-tcl-10.23-alt1.p10.4.x86_64 File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql11-tcl-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-tcl-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-tcl-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-tcl-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-tcl-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-tcl-16.8-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-tcl-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql10-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql11-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.; File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql12-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.; File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql13-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.; File /usr/lib64/pgsql/tds_fdw.so conflicts 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.; File /usr/lib64/pgsql/tds_fdw.so conflicts 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.; File /usr/lib64/pgsql/tds_fdw.so conflicts 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.; File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql17-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.; warn postgresql11-contrib-11.22-alt0.p10.4.x86_64 There are file conflicts with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64, for example, /usr/bin/pg_standby (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 postgresql12-contrib-12.22-alt0.p10.2.x86_64, for example, /usr/bin/oid2name (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 postgresql13-contrib-13.20-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (72 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.20-alt0.p10.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.; There are file conflicts with the package postgresql14-contrib-14.17-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (70 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql14-python-14.17-alt0.p10.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.; There are file conflicts with the package postgresql15-contrib-15.12-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (71 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql15-python-15.12-alt0.p10.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.; There are file conflicts with the package postgresql16-contrib-16.8-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (74 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql16-python-16.8-alt0.p10.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.; There are file conflicts with the package postgresql17-contrib-17.4-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (75 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql17-python-17.4-alt0.p10.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 postgresql11-llvmjit-11.22-alt0.p10.4.x86_64 There are file conflicts with the package postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (704 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (765 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (778 file conflicts in 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-1C-llvmjit-15.12-alt0.p10.1.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 postgresql15-llvmjit-15.12-alt0.p10.1.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 postgresql16-llvmjit-16.8-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 file conflicts in 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-alt0.p10.1.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 postgresql11-perl-11.22-alt0.p10.4.x86_64 File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-perl-12.22-alt0.p10.2.x86_64, for example, /usr/share/pgsql/extension/plperl--1.0.sql (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql13-perl-13.20-alt0.p10.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.; There are file conflicts with the package postgresql14-perl-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-perl-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-perl-16.8-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-perl-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql11-pg_partman-4.7.4-alt1.x86_64 File /usr/share/pgsql/extension/pg_partman--4.7.4.sql conflicts with the package postgresql10-pg_partman-4.7.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 postgresql12-pg_partman-4.7.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 postgresql13-pg_partman-4.7.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 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 postgresql11-python-11.22-alt0.p10.4.x86_64 File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql10-python-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql12-python-12.22-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql13-python-13.20-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql14-python-14.17-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql15-python-15.12-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql16-python-16.8-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql17-python-17.4-alt0.p10.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 postgresql11-server-11.22-alt0.p10.4.x86_64 There are file conflicts with the package postgresql10-server-10.23-alt1.p10.4.x86_64, for example, /lib/systemd/system/postgresql.service (49 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-server-12.22-alt0.p10.2.x86_64, for example, /usr/bin/pg_controldata (69 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-server-13.20-alt0.p10.1.x86_64, for example, /usr/bin/initdb (631 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/bin/initdb (634 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/bin/initdb (635 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-server-16.8-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (638 file conflicts in 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-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (638 file conflicts in 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 postgresql11-tcl-11.22-alt0.p10.4.x86_64 File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-tcl-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-tcl-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-tcl-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-tcl-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-tcl-16.8-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-tcl-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql11-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql10-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 postgresql12-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 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.; 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 postgresql12-contrib-12.22-alt0.p10.2.x86_64 There are file conflicts with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64, for example, /usr/bin/oid2name (39 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-contrib-11.22-alt0.p10.4.x86_64, for example, /usr/bin/oid2name (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 postgresql13-contrib-13.20-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (63 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.20-alt0.p10.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.; There are file conflicts with the package postgresql14-contrib-14.17-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (64 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (68 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (72 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-contrib-17.4-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (73 file conflicts in 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 postgresql12-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.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql15-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 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 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 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 postgresql12-llvmjit-12.22-alt0.p10.2.x86_64 There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (704 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (745 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (788 file conflicts in 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-1C-llvmjit-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (794 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (792 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (803 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (799 file conflicts in 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 postgresql12-perl-12.22-alt0.p10.2.x86_64 There are file conflicts with the package postgresql10-perl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-perl-11.22-alt0.p10.4.x86_64, for example, /usr/share/pgsql/extension/plperl--1.0.sql (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql13-perl-13.20-alt0.p10.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.; There are file conflicts with the package postgresql14-perl-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-perl-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-perl-16.8-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-perl-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql12-pg-auto-failover-2.1-alt1.1.x86_64 There are file conflicts with the package postgresql13-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover.index.bc (13 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover.index.bc (13 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-1C-pg-auto-failover-2.1-alt1.p10.1.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 postgresql15-pg-auto-failover-2.1-alt1.p10.1.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.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql12-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-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 postgresql12-pg_partman-4.7.4-alt1.x86_64 Files /usr/lib64/pgsql/pg_partman_bgw.so /usr/share/pgsql/extension/pg_partman--4.7.4.sql conflict with the package postgresql10-pg_partman-4.7.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 postgresql11-pg_partman-4.7.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 postgresql13-pg_partman-4.7.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 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 postgresql12-pg_repack-1.5.2-alt1.x86_64 Files /usr/lib64/pgsql/bitcode/pg_repack/pgut/pgut-spi.bc /usr/lib64/pgsql/bitcode/pg_repack/repack.bc /usr/lib64/pgsql/pg_repack.so conflict with the package postgresql13-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.; 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-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 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-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 postgresql12-python-12.22-alt0.p10.2.x86_64 Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql10-python-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql /usr/share/pgsql/extension/plpython3u--unpackaged--1.0.sql conflict with the package postgresql11-python-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql13-python-13.20-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql14-python-14.17-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql15-python-15.12-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql16-python-16.8-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql17-python-17.4-alt0.p10.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 postgresql12-server-12.22-alt0.p10.2.x86_64 There are file conflicts with the package postgresql10-server-10.23-alt1.p10.4.x86_64, for example, /lib/systemd/system/postgresql.service (89 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-server-11.22-alt0.p10.4.x86_64, for example, /usr/bin/pg_controldata (69 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-server-13.20-alt0.p10.1.x86_64, for example, /usr/bin/initdb (620 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/bin/initdb (625 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/bin/initdb (631 file conflicts in 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-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (635 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-server-17.4-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (636 file conflicts in 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 postgresql12-tcl-12.22-alt0.p10.2.x86_64 There are file conflicts with the package postgresql10-tcl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-tcl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql13-tcl-13.20-alt0.p10.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.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql14-tcl-14.17-alt0.p10.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.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql15-tcl-15.12-alt0.p10.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.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql16-tcl-16.8-alt0.p10.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.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql17-tcl-17.4-alt0.p10.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 postgresql12-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql10-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 postgresql11-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 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.; 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-contrib-13.20-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64, for example, /usr/bin/oid2name (73 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-contrib-11.22-alt0.p10.4.x86_64, for example, /usr/bin/oid2name (72 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-contrib-12.22-alt0.p10.2.x86_64, for example, /usr/bin/oid2name (63 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-contrib-14.17-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (25 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-contrib-15.12-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (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 postgresql16-contrib-16.8-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (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-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (42 file conflicts in 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 postgresql12-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.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc /usr/lib64/pgsql/credcheck.so conflict with the package postgresql15-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 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-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-llvmjit-13.20-alt0.p10.1.x86_64 There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (765 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (745 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (763 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-1C-llvmjit-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (790 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (790 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (808 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (805 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql13-multicorn2-2.4-alt2.x86_64 There are file conflicts with the package postgresql14-multicorn2-2.4-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/multicorn/src/errors.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-multicorn2-2.4-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/multicorn/src/errors.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-perl-13.20-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-perl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql11-perl-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql12-perl-12.22-alt0.p10.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.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-perl-14.17-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.12-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.8-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.4-alt0.p10.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 postgresql13-pg-auto-failover-2.1-alt1.p10.1.x86_64 There are file conflicts with the package postgresql12-pg-auto-failover-2.1-alt1.1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover.index.bc (13 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-pg-auto-failover-2.1-alt1.p10.1.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-1C-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-pg-auto-failover-2.1-alt1.p10.1.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 postgresql17-pg-auto-failover-2.1-alt1.p10.1.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.; 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-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 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 conflict with the package postgresql15-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.; 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-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 postgresql13-pg_partman-4.7.4-alt1.x86_64 Files /usr/lib64/pgsql/pg_partman_bgw.so /usr/share/pgsql/extension/pg_partman--4.7.4.sql conflict with the package postgresql10-pg_partman-4.7.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 postgresql11-pg_partman-4.7.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 postgresql12-pg_partman-4.7.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 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 Files /usr/lib64/pgsql/bitcode/pg_repack/pgut/pgut-spi.bc /usr/lib64/pgsql/bitcode/pg_repack/repack.bc /usr/lib64/pgsql/pg_repack.so conflict with the package postgresql12-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.; 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-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 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-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-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 (86 file conflicts in 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 (90 file conflicts in 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 (94 file conflicts in 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 (93 file conflicts in 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-alt0.p10.1.x86_64 Files /usr/lib64/pgsql/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql10-python-10.23-alt1.p10.4.x86_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 postgresql11-contrib-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql11-python-11.22-alt0.p10.4.x86_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 postgresql12-contrib-12.22-alt0.p10.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.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql12-python-12.22-alt0.p10.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.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql14-python-14.17-alt0.p10.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 /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql15-1C-contrib-15.12-alt0.p10.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 /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql15-python-15.12-alt0.p10.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.; Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql16-python-16.8-alt0.p10.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.; Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql17-python-17.4-alt0.p10.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 postgresql13-repmgr-5.4.1-alt3.x86_64 Files /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc /usr/lib64/pgsql/repmgr.so conflict with the package postgresql14-repmgr-5.4.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-repmgr-5.4.1-alt3.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 postgresql16-repmgr-5.4.1-alt3.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-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-server-10.23-alt1.p10.4.x86_64, for example, /lib/systemd/system/postgresql.service (634 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-server-11.22-alt0.p10.4.x86_64, for example, /usr/bin/initdb (631 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-server-12.22-alt0.p10.2.x86_64, for example, /usr/bin/initdb (620 file conflicts in 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-alt0.p10.1.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-alt0.p10.1.x86_64, for example, /usr/bin/initdb (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 postgresql16-server-16.8-alt0.p10.1.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 postgresql17-server-17.4-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (37 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql13-tcl-13.20-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-tcl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-tcl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql12-tcl-12.22-alt0.p10.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 postgresql13-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql10-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 postgresql11-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 postgresql12-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/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/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.; warn postgresql13-timescaledb-2.15.3-alt1.x86_64 Files /usr/lib64/pgsql/timescaledb.so /usr/share/pgsql/extension/timescaledb.control 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.; Files /usr/lib64/pgsql/timescaledb.so /usr/share/pgsql/extension/timescaledb.control 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.so /usr/share/pgsql/extension/timescaledb.control 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 postgresql14-contrib-14.17-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64, for example, /usr/bin/oid2name (71 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-contrib-11.22-alt0.p10.4.x86_64, for example, /usr/bin/oid2name (70 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-contrib-12.22-alt0.p10.2.x86_64, for example, /usr/bin/oid2name (64 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-contrib-13.20-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (25 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-contrib-15.12-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-contrib-17.4-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.; 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 postgresql12-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 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 conflict with the package postgresql15-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 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-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-llvmjit-14.17-alt0.p10.1.x86_64 There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (778 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (788 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (763 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-1C-llvmjit-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (658 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (648 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (788 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (798 file conflicts in 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.4-alt2.x86_64 There are file conflicts with the package postgresql13-multicorn2-2.4-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/multicorn/src/errors.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/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.4-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql14-perl-14.17-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-perl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-perl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-perl-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.8-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.4-alt0.p10.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 postgresql14-pg-auto-failover-2.1-alt1.p10.1.x86_64 There are file conflicts with the package postgresql12-pg-auto-failover-2.1-alt1.1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover.index.bc (13 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-pg-auto-failover-2.1-alt1.p10.1.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-1C-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-pg-auto-failover-2.1-alt1.p10.1.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 postgresql17-pg-auto-failover-2.1-alt1.p10.1.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.; 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-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 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-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.; 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-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 postgresql10-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (83 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-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.; There are file conflicts with the package postgresql12-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.; 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 postgresql12-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 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-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 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-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.7.0-alt2.x86_64 File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql15-1C-pgaudit-1.7.0-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/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql15-pgaudit-1.7.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.; There are file conflicts with the package postgresql16-pgaudit-17.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgaudit.index.bc (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pgaudit-17.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgaudit.index.bc (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql14-pgauditlogtofile-1.6.4-alt1.x86_64 There are file conflicts with the package postgresql15-1C-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (9 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile.index.bc (9 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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 (86 file conflicts in 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 (87 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (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 postgresql17-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (94 file conflicts in 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-alt0.p10.1.x86_64 Files /usr/lib64/pgsql/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql10-python-10.23-alt1.p10.4.x86_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 postgresql11-contrib-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql11-python-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql12-python-12.22-alt0.p10.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.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.20-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.8-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql17-python-17.4-alt0.p10.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 postgresql14-repmgr-5.4.1-alt3.x86_64 Files /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc /usr/lib64/pgsql/repmgr.so conflict with the package postgresql13-repmgr-5.4.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/repmgr /usr/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql15-repmgr-5.4.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-repmgr-5.4.1-alt3.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-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-server-10.23-alt1.p10.4.x86_64, for example, /lib/systemd/system/postgresql.service (637 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-server-11.22-alt0.p10.4.x86_64, for example, /usr/bin/initdb (634 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-server-12.22-alt0.p10.2.x86_64, for example, /usr/bin/initdb (625 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-server-13.20-alt0.p10.1.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-alt0.p10.1.x86_64, for example, /usr/bin/initdb (28 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-server-16.8-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (37 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-server-17.4-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (37 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql14-tcl-14.17-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-tcl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-tcl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql12-tcl-12.22-alt0.p10.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 postgresql14-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql10-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 postgresql11-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 postgresql12-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 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.; Files /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.bc /usr/lib64/pgsql/bitcode/tds_fdw/src/tds_fdw.bc /usr/lib64/pgsql/tds_fdw.so conflict with the package postgresql17-tds_fdw-2.0.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-timescaledb-2.17.2-alt1.x86_64 Files /usr/lib64/pgsql/timescaledb.so /usr/share/pgsql/extension/timescaledb.control conflict 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-1C-contrib-15.12-alt0.p10.1.x86_64 File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.20-alt0.p10.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 postgresql15-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 postgresql12-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 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 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.; File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts 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/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-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-1C-llvmjit-15.12-alt0.p10.1.x86_64 There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.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 postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (794 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (790 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (658 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/adminpack/adminpack.bc (265 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (808 file conflicts in 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-1C-pg-auto-failover-2.1-alt1.p10.1.x86_64 There are file conflicts with the package postgresql12-pg-auto-failover-2.1-alt1.1.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 postgresql13-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/pgautofailover/metadata.bc /usr/lib64/pgsql/bitcode/pgautofailover/node_active_protocol.bc /usr/lib64/pgsql/bitcode/pgautofailover/pg_auto_failover.bc conflict with the package postgresql15-pg-auto-failover-2.1-alt1.p10.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.; There are file conflicts with the package postgresql16-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql15-1C-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-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-1C-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 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.; 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-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-1C-pg_repack-1.5.2-alt1.x86_64 There are file conflicts with the package postgresql12-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 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.; 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-1C-pgaudit-1.7.0-alt3.x86_64 File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql14-pgaudit-1.7.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/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql15-pgaudit-1.7.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.; There are file conflicts with the package postgresql16-pgaudit-17.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgaudit.index.bc (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pgaudit-17.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgaudit.index.bc (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql15-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 (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 postgresql16-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.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-contrib-15.12-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64, for example, /usr/bin/oid2name (71 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-contrib-11.22-alt0.p10.4.x86_64, for example, /usr/bin/oid2name (71 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-contrib-12.22-alt0.p10.2.x86_64, for example, /usr/bin/oid2name (68 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-contrib-13.20-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (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 postgresql14-contrib-14.17-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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-alt0.p10.1.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-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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.; 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 postgresql12-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 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 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.; File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts with the package postgresql15-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 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-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-llvmjit-15.12-alt0.p10.1.x86_64 There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.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 postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (792 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (790 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (648 file conflicts in 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-1C-llvmjit-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/adminpack/adminpack.bc (265 file conflicts in 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-alt0.p10.1.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 postgresql17-llvmjit-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (809 file conflicts in 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.4-alt2.x86_64 There are file conflicts with the package postgresql13-multicorn2-2.4-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/multicorn/src/errors.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/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.4-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql15-perl-15.12-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-perl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-perl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-perl-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql16-perl-16.8-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.4-alt0.p10.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 postgresql15-pg-auto-failover-2.1-alt1.p10.1.x86_64 There are file conflicts with the package postgresql12-pg-auto-failover-2.1-alt1.1.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 postgresql13-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/bitcode/pgautofailover/metadata.bc /usr/lib64/pgsql/bitcode/pgautofailover/node_active_protocol.bc /usr/lib64/pgsql/bitcode/pgautofailover/pg_auto_failover.bc conflict with the package postgresql15-1C-pg-auto-failover-2.1-alt1.p10.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.; There are file conflicts with the package postgresql16-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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-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 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.; 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-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.; 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-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 postgresql10-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (83 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-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.; There are file conflicts with the package postgresql12-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.; 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 postgresql12-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 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-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 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-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.0-alt2.x86_64 File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql14-pgaudit-1.7.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/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql15-1C-pgaudit-1.7.0-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.; There are file conflicts with the package postgresql16-pgaudit-17.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgaudit.index.bc (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pgaudit-17.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgaudit.index.bc (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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 (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 postgresql16-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.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 (90 file conflicts in 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 (87 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (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 postgresql17-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (87 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql15-python-15.12-alt0.p10.1.x86_64 Files /usr/lib64/pgsql/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql10-python-10.23-alt1.p10.4.x86_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 postgresql11-contrib-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql11-python-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql12-python-12.22-alt0.p10.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.; File /usr/lib64/pgsql/jsonb_plpython3.so conflicts with the package postgresql13-python-13.20-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql16-python-16.8-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql17-python-17.4-alt0.p10.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 postgresql15-repmgr-5.4.1-alt3.x86_64 There are file conflicts with the package postgresql13-repmgr-5.4.1-alt3.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/lib64/pgsql/bitcode/repmgr.index.bc /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql14-repmgr-5.4.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/bin/repmgr /usr/bin/repmgrd /usr/lib64/pgsql/bitcode/repmgr/repmgr.bc conflict with the package postgresql16-repmgr-5.4.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql15-server-15.12-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-server-10.23-alt1.p10.4.x86_64, for example, /lib/systemd/system/postgresql.service (638 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-server-11.22-alt0.p10.4.x86_64, for example, /usr/bin/initdb (635 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-server-12.22-alt0.p10.2.x86_64, for example, /usr/bin/initdb (631 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-server-13.20-alt0.p10.1.x86_64, for example, /usr/bin/initdb (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 postgresql14-server-14.17-alt0.p10.1.x86_64, for example, /usr/bin/initdb (28 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-server-16.8-alt0.p10.1.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-alt0.p10.1.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.; warn postgresql15-tcl-15.12-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-tcl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-tcl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql12-tcl-12.22-alt0.p10.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 postgresql15-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql10-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 postgresql11-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 postgresql12-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 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.; Files /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.bc /usr/lib64/pgsql/bitcode/tds_fdw/src/tds_fdw.bc /usr/lib64/pgsql/tds_fdw.so conflict with the package postgresql17-tds_fdw-2.0.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-timescaledb-2.17.2-alt1.x86_64 Files /usr/lib64/pgsql/timescaledb.so /usr/share/pgsql/extension/timescaledb.control conflict 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.; 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 postgresql16-contrib-16.8-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64, for example, /usr/bin/oid2name (75 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-contrib-11.22-alt0.p10.4.x86_64, for example, /usr/bin/oid2name (74 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-contrib-12.22-alt0.p10.2.x86_64, for example, /usr/bin/oid2name (72 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-contrib-13.20-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (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-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-contrib-15.12-alt0.p10.1.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-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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 postgresql16-credcheck-3.0-alt1.x86_64 Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflict with the package postgresql12-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 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-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 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.; File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts 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 postgresql16-llvmjit-16.8-alt0.p10.1.x86_64 There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (803 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (808 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (788 file conflicts in 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-1C-llvmjit-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (787 file conflicts in 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-alt0.p10.1.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 postgresql17-llvmjit-17.4-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (725 file conflicts in 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-alt0.p10.1.x86_64 Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql10-perl-10.23-alt1.p10.4.x86_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 postgresql11-perl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-perl-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-perl-14.17-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.12-alt0.p10.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 postgresql16-pg-auto-failover-2.1-alt1.p10.1.x86_64 There are file conflicts with the package postgresql12-pg-auto-failover-2.1-alt1.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-pg-auto-failover-2.1-alt1.p10.1.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.1-alt1.p10.1.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 postgresql15-1C-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql17-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover/formation_metadata.bc (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql16-pg_checksums-1.2-alt2.x86_64 File /usr/bin/pg_checksums_ext conflicts with the package postgresql12-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 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-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 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-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 (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 (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-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 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 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 postgresql16-pg_partman-5.2.4-alt1.x86_64 There are file conflicts with the package postgresql10-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (83 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-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.; There are file conflicts with the package postgresql12-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.; 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 postgresql12-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 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-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 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-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-17.0-alt1.x86_64 There are file conflicts with the package postgresql14-pgaudit-1.7.0-alt2.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-1C-pgaudit-1.7.0-alt3.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.0-alt2.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.; File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql17-pgaudit-17.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-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 (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.; There are file conflicts with the package postgresql15-1C-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile.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/pgauditlogtofile/logtofile.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.bc /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_log.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 (94 file conflicts in 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 (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 postgresql15-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/address_standardizer-3.so (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 postgresql17-postgis-3.5.2-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/address_standardizer-3/address_parser.bc (81 file conflicts in 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-alt0.p10.1.x86_64 Files /usr/lib64/pgsql/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql10-python-10.23-alt1.p10.4.x86_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 postgresql11-contrib-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql11-python-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql12-python-12.22-alt0.p10.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.; Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql13-python-13.20-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql14-python-14.17-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.12-alt0.p10.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 postgresql16-repmgr-5.4.1-alt3.x86_64 There are file conflicts with the package postgresql13-repmgr-5.4.1-alt3.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.4.1-alt3.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.4.1-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql16-server-16.8-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-server-10.23-alt1.p10.4.x86_64, for example, /etc/rc.d/init.d/postgresql (641 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-server-11.22-alt0.p10.4.x86_64, for example, /etc/rc.d/init.d/postgresql (638 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-server-12.22-alt0.p10.2.x86_64, for example, /etc/rc.d/init.d/postgresql (635 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-server-13.20-alt0.p10.1.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-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (37 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-server-15.12-alt0.p10.1.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-alt0.p10.1.x86_64, for example, /usr/bin/initdb (26 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql16-tcl-16.8-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-tcl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-tcl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql12-tcl-12.22-alt0.p10.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 postgresql16-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql10-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 postgresql11-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 postgresql12-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 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.; Files /usr/lib64/pgsql/bitcode/tds_fdw/src/deparse.bc /usr/lib64/pgsql/bitcode/tds_fdw/src/tds_fdw.bc /usr/lib64/pgsql/tds_fdw.so conflict with the package postgresql17-tds_fdw-2.0.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-timescaledb-2.17.2-alt1.x86_64 Files /usr/lib64/pgsql/timescaledb.so /usr/share/pgsql/extension/timescaledb.control conflict 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.; 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.; warn postgresql17-contrib-17.4-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64, for example, /usr/bin/oid2name (76 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-contrib-11.22-alt0.p10.4.x86_64, for example, /usr/bin/oid2name (75 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-contrib-12.22-alt0.p10.2.x86_64, for example, /usr/bin/oid2name (73 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-contrib-13.20-alt0.p10.1.x86_64, for example, /usr/bin/oid2name (42 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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 postgresql15-contrib-15.12-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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 postgresql16-contrib-16.8-alt0.p10.1.x86_64, for example, /usr/bin/pg_archivecleanup (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 postgresql17-credcheck-3.0-alt1.x86_64 Files /usr/lib64/pgsql/bitcode/credcheck.index.bc /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflict with the package postgresql12-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 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-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 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.; File /usr/lib64/pgsql/bitcode/credcheck/credcheck.bc conflicts 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.; warn postgresql17-llvmjit-17.4-alt0.p10.1.x86_64 There are file conflicts with the package postgresql11-llvmjit-11.22-alt0.p10.4.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 postgresql12-llvmjit-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (799 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-llvmjit-13.20-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (805 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-llvmjit-14.17-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (798 file conflicts in 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-1C-llvmjit-15.12-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (808 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (809 file conflicts in 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-alt0.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int/_int_bool.bc (725 file conflicts in 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-alt0.p10.1.x86_64 Files /usr/share/pgsql/extension/plperl--1.0.sql /usr/share/pgsql/extension/plperl.control /usr/share/pgsql/extension/plperlu--1.0.sql conflict with the package postgresql10-perl-10.23-alt1.p10.4.x86_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 postgresql11-perl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-perl-12.22-alt0.p10.2.x86_64, for example, /usr/lib64/pgsql/plperl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql13-perl-13.20-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql14-perl-14.17-alt0.p10.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 /usr/lib64/pgsql/plperl.so conflicts with the package postgresql15-perl-15.12-alt0.p10.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 postgresql17-pg-auto-failover-2.1-alt1.p10.1.x86_64 There are file conflicts with the package postgresql12-pg-auto-failover-2.1-alt1.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-pg-auto-failover-2.1-alt1.p10.1.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.1-alt1.p10.1.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 postgresql15-1C-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/bin/pg_autoctl (14 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql16-pg-auto-failover-2.1-alt1.p10.1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgautofailover/formation_metadata.bc (10 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql17-pg_checksums-1.2-alt2.x86_64 File /usr/bin/pg_checksums_ext conflicts with the package postgresql12-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 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-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 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 (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 (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-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 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 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.; warn postgresql17-pg_partman-5.2.4-alt1.x86_64 There are file conflicts with the package postgresql10-pg_partman-4.7.4-alt1.x86_64, for example, /usr/bin/dump_partition.py (83 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-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.; There are file conflicts with the package postgresql12-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.; 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 postgresql12-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 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-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 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.0-alt1.x86_64 There are file conflicts with the package postgresql14-pgaudit-1.7.0-alt2.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-1C-pgaudit-1.7.0-alt3.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.0-alt2.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.; File /usr/lib64/pgsql/bitcode/pgaudit/pgaudit.bc conflicts with the package postgresql16-pgaudit-17.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-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 (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.; There are file conflicts with the package postgresql15-1C-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.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-pgauditlogtofile-1.6.4-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/pgauditlogtofile/logtofile_bgw.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.bc /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.; 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 (93 file conflicts in 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 (94 file conflicts in 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 (87 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 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 (81 file conflicts in 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-alt0.p10.1.x86_64 Files /usr/lib64/pgsql/hstore_plpython3.so /usr/lib64/pgsql/ltree_plpython3.so conflict with the package postgresql10-contrib-10.23-alt1.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql10-python-10.23-alt1.p10.4.x86_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 postgresql11-contrib-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql11-python-11.22-alt0.p10.4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql12-python-12.22-alt0.p10.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.; Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql13-python-13.20-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql14-python-14.17-alt0.p10.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 /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql15-python-15.12-alt0.p10.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 postgresql17-server-17.4-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-server-10.23-alt1.p10.4.x86_64, for example, /etc/rc.d/init.d/postgresql (641 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-server-11.22-alt0.p10.4.x86_64, for example, /etc/rc.d/init.d/postgresql (638 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql12-server-12.22-alt0.p10.2.x86_64, for example, /etc/rc.d/init.d/postgresql (636 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql13-server-13.20-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (37 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql14-server-14.17-alt0.p10.1.x86_64, for example, /etc/rc.d/init.d/postgresql (37 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql15-server-15.12-alt0.p10.1.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 postgresql16-server-16.8-alt0.p10.1.x86_64, for example, /usr/bin/initdb (26 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn postgresql17-tcl-17.4-alt0.p10.1.x86_64 There are file conflicts with the package postgresql10-tcl-10.23-alt1.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package postgresql11-tcl-11.22-alt0.p10.4.x86_64, for example, /usr/lib64/pgsql/pltcl.so (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; Files /usr/share/pgsql/extension/pltcl--1.0.sql /usr/share/pgsql/extension/pltcl.control /usr/share/pgsql/extension/pltclu--1.0.sql conflict with the package postgresql12-tcl-12.22-alt0.p10.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 postgresql17-tds_fdw-2.0.4-alt1.x86_64 File /usr/lib64/pgsql/tds_fdw.so conflicts with the package postgresql10-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 postgresql11-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 postgresql12-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 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.; 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.; warn pve-lxc-5.0.2-alt1.x86_64 File /usr/share/lxc/templates/lxc-download conflicts with the package lxc-templates-4.0.12-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 pve-manager-7.4.17-alt2.x86_64 Files /usr/bin/vzdump /usr/share/man/man1/vzdump.1.xz conflict with the package vzdump-1.0-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 pve-qemu-common-7.2.10-alt1.x86_64 File /usr/share/qemu/hppa-firmware.img conflicts with the package qemu-system-hppa-core-8.2.6-alt0.p10.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 /usr/share/qemu/trace-events-all conflicts with the package qemu-tools-8.2.6-alt0.p10.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 pve-qemu-system-7.2.10-alt1.x86_64 There are file conflicts with the package qemu-common-8.2.6-alt0.p10.1.x86_64, for example, /usr/libexec/qemu-bridge-helper (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/libexec/vhost-user-gpu conflicts with the package qemu-device-display-vhost-user-gpu-8.2.6-alt0.p10.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.; 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-8.2.6-alt0.p10.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 /usr/bin/qemu-system-aarch64 conflicts with the package qemu-system-aarch64-core-8.2.6-alt0.p10.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 /usr/bin/qemu-system-x86_64 conflicts with the package qemu-system-x86-core-8.2.6-alt0.p10.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 /usr/libexec/virtiofsd conflicts with the package virtiofsd-1.6.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 python-module-commonmark-0.8.1-alt0.1.noarch File /usr/bin/cmark conflicts with the package cmark-0.29.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 python-module-twisted-conch-18.9.0-alt2.x86_64 There are file conflicts with the package python3-module-twisted-conch-20.3.0-alt2.x86_64, for example, /usr/bin/cftp (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 python-module-twisted-mail-18.9.0-alt2.x86_64 File /usr/bin/mailmail conflicts with the package python3-module-twisted-mail-20.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 python-module-wx3.0-3.0.2.0-alt2.x86_64 There are file conflicts with the package python3-module-wx-utils-4.0.7-alt3.1.x86_64, for example, /usr/bin/img2png (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 python-module-xstatic-1.0.1-alt3.noarch File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-html5shiv-3.6.1-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/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-less-1.3.0.1-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/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-socialshareprivacy-1.4.1-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 python-module-xstatic-html5shiv-3.6.1-alt4.noarch File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.0.1-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 python-module-xstatic-less-1.3.0.1-alt4.noarch File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.0.1-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 python-module-xstatic-socialshareprivacy-1.4.1-alt4.noarch File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.0.1-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 python3-module-django-facebook-utils-1.0.4-alt2.noarch There are file conflicts with the package python3-module-facebook_utils-0.50.5-alt1.noarch, for example, /usr/lib/python3/site-packages/facebook_utils/__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-facebook-2.3.14-alt2.noarch There are file conflicts with the package python3-module-facebook_api-0.1.10-alt1.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 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-facebook-sdk-1.0.0-alt2.noarch There are file conflicts with the package python3-module-facebook_api-0.1.10-alt1.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.; 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-facebook_api-0.1.10-alt1.noarch There are file conflicts with the package python3-module-facebook-2.3.14-alt2.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (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 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.; 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-facebook_utils-0.50.5-alt1.noarch There are file conflicts with the package python3-module-django-facebook-utils-1.0.4-alt2.noarch, for example, /usr/lib/python3/site-packages/facebook_utils/__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-gearbox-0.2.1-alt1.noarch File /usr/bin/gearbox conflicts with the package mesa-demos-8.4.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 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_11.x86_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-libsass-0.20.1-alt1.x86_64 File /usr/bin/sassc conflicts with the package sassc-3.6.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; warn python3-module-odf-1.4.1-alt1.noarch There are file conflicts with the package python3-module-odfpy-1.4.0-alt1.noarch, for example, /usr/lib/python3/site-packages/odf/attrconverters.py (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.; warn python3-module-odfpy-1.4.0-alt1.noarch There are file conflicts with the package python3-module-odf-1.4.1-alt1.noarch, for example, /usr/lib/python3/site-packages/odf/attrconverters.py (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.; warn python3-module-radon-5.0.1-alt1.noarch File /usr/bin/radon conflicts with the package nfft-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.; 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-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-tornado-facebook-sdk-0.1.0-alt2.noarch There are file conflicts with the package python3-module-facebook-2.3.14-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.; 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.; There are file conflicts with the package python3-module-facebook_api-0.1.10-alt1.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-twisted-conch-20.3.0-alt2.x86_64 There are file conflicts with the package python-module-twisted-conch-18.9.0-alt2.x86_64, for example, /usr/bin/cftp (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-twisted-mail-20.3.0-alt2.x86_64 File /usr/bin/mailmail conflicts with the package python-module-twisted-mail-18.9.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 python3-module-wx-utils-4.0.7-alt3.1.x86_64 There are file conflicts with the package python-module-wx3.0-3.0.2.0-alt2.x86_64, for example, /usr/bin/img2png (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 qemu-common-8.2.6-alt0.p10.1.x86_64 There are file conflicts with the package pve-qemu-system-7.2.10-alt1.x86_64, for example, /usr/libexec/qemu-bridge-helper (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-device-display-vhost-user-gpu-8.2.6-alt0.p10.1.x86_64 File /usr/libexec/vhost-user-gpu conflicts with the package pve-qemu-system-7.2.10-alt1.x86_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-8.2.6-alt0.p10.1.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-7.2.10-alt1.x86_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-8.2.6-alt0.p10.1.x86_64 File /usr/bin/qemu-system-aarch64 conflicts with the package pve-qemu-system-7.2.10-alt1.x86_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-8.2.6-alt0.p10.1.x86_64 File /usr/share/qemu/hppa-firmware.img conflicts with the package pve-qemu-common-7.2.10-alt1.x86_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-8.2.6-alt0.p10.1.x86_64 File /usr/bin/qemu-system-x86_64 conflicts with the package pve-qemu-system-7.2.10-alt1.x86_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-8.2.6-alt0.p10.1.x86_64 File /usr/share/qemu/trace-events-all conflicts with the package pve-qemu-common-7.2.10-alt1.x86_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_1jpp8.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 rclone-1.65.2-alt1.x86_64 File /usr/share/zsh/site-functions/_rclone conflicts with the package zsh-completions-0.32.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 sandbox-2.18-alt1.x86_64 File /usr/bin/sandbox conflicts with the package policycoreutils-sandbox-3.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 sassc-3.6.2-alt1.x86_64 File /usr/bin/sassc conflicts with the package python3-module-libsass-0.20.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 screen-message-0.6-alt2.x86_64 File /usr/share/man/man1/sm.1.xz conflicts with the package inn-2.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.; 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_11.x86_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 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 sleuthkit-4.10.2-alt1.x86_64 File /usr/bin/jcat conflicts with the package can-uilts-v2019.00.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 soundconverter-4.0.1-alt1.noarch File /usr/share/glib-2.0/schemas/gschemas.compiled conflicts with the package oregano-0.84.43-alt1.x86_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 sparsehash-devel-2.0.4-alt1.x86_64 There are file conflicts with the package libgoogle-sparsehash-1.5.2-alt1.1.noarch, for example, /usr/include/google/dense_hash_map (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 syslinux-4.04-alt18.x86_64 File /usr/share/man/man1/extlinux.1.xz conflicts with the package extlinux-6.04.pre3-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.; 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-alt18.x86_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-alt3.x86_64 File /usr/bin/task conflicts with the package go-task-2.4.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 terminfo-extra-6.3.20220618-alt1.noarch File /usr/share/terminfo/f/fbterm conflicts with the package fbterm-1.7-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 tinyemu-20191221-alt1.x86_64 Files /usr/bin/build_filelist /usr/bin/splitimg conflict with the package marss-riscv-1.0a-alt1.x86_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 virtiofsd-1.6.0-alt1.x86_64 File /usr/libexec/virtiofsd conflicts with the package pve-qemu-system-7.2.10-alt1.x86_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-server-1.2-alt1.noarch 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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-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.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 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-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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-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.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 volumes-profile-alt-workstation-0.4-alt1.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-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-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.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 volumes-profile-centaurus-0.13-alt1.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-0.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 /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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-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.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 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-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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-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.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 volumes-profile-cliff-workstation-0.2-alt1.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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-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.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 volumes-profile-education-10.0-alt6.x86_64 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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-jeos-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-kdesktop-0.13.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.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-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.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 volumes-profile-jeos-0.2-alt1.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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.13.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.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-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.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 volumes-profile-kdesktop-0.13.1-alt1.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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-lite-0.4.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-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.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 volumes-profile-lite-0.4.1-alt1.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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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-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.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 volumes-profile-master-0.2-alt1.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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-regular-0.5.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 volumes-profile-regular-0.5.1-alt1.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-0.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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.13-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.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-education-10.0-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.; File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-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-kdesktop-0.13.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.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-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 vzdump-1.0-alt3.x86_64 Files /usr/bin/vzdump /usr/share/man/man1/vzdump.1.xz conflict with the package pve-manager-7.4.17-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 wakeonlan-0.41.0.19.git41b636c-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 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.9.0-alt1.x86_64 File /usr/bin/xfreerdp conflicts with the package baikal-openuds-0.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 zsh-completions-0.32.0-alt1.noarch File /usr/share/zsh/site-functions/_rclone conflicts with the package rclone-1.65.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.;