warn	LibreOffice4-integrated-4.2-alt1.M70P.3.x86_64	symlink /usr/share/applications/base.desktop is a file in the package libreoffice-3.6.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.; symlink /usr/share/applications/calc.desktop is a file in the package libreoffice-3.6.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.; symlink /usr/share/applications/draw.desktop is a file in the package libreoffice-3.6.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.; symlink /usr/share/applications/impress.desktop is a file in the package libreoffice-3.6.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.; symlink /usr/share/applications/math.desktop is a file in the package libreoffice-3.6.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.; symlink /usr/share/applications/writer.desktop is a file in the package libreoffice-3.6.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	alterator-setup-0.2.1-alt2.noarch	symlink /usr/share/install2/installer-steps is a file in the package installer-distro-backup-server-stage2-6.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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-office-server-stage2-5.0-alt28.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-server-light-stage2-6.0-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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-workbench-stage2-5.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.; symlink /usr/share/install2/installer-steps is a file in the package installer-office-desktop-stage2-5.0-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.; symlink /usr/share/install2/installer-steps is a file in the package installer-server-lite-stage2-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.; symlink /usr/share/install2/installer-steps is a file in the package installer-server-stage2-0.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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-desktop-stage2-5.0-alt23.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-lxdesktop-stage2-6.0-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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-tablet-stage2-6.0-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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-junior-stage2-7.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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-altlinux-desktop-stage2-7.0.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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-school-server-stage2-7.0-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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-centaurus-stage2-7.0-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.; symlink /usr/share/install2/installer-steps is a file in 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.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-simply-linux-stage2-7.0-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/install2/installer-steps is a file in the package installer-distro-altlinux-server-stage2-7.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	atftp-0.7-alt1.qa1.x86_64	symlink /usr/sbin/in.tftpd is a file in the package inquisitor-tftpd-0.48-alt1.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	atftp-debuginfo-0.7-alt1.qa1.x86_64	symlink /usr/lib/debug/usr/sbin/in.tftpd.debug is a file in the package tftpd-debuginfo-5.0-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/lib/debug/usr/sbin/in.tftpd.debug is a file in the package inquisitor-tftpd-debuginfo-0.48-alt1.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	branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch	symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-informika-schoolmaster-alterator-6.0.0-alt46.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-sisyphus-server-light-alterator-1.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.; symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-altlinux-kdesktop-alterator-7.0.5-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.; symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; 
warn	branding-school-teacher-alterator-7.0.5-alt0.M70P.2.noarch	symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-altlinux-p7-alterator-20140902-alt0.M70P.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.; symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-altlinux-starterkit-alterator-p7-alt7.M70P.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.; 
warn	ccid-debuginfo-1.3.13-alt1.qa1.x86_64	symlink /usr/lib/debug/usr/lib64/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so.debug is a file in the package pcsc-lite-ccid-debuginfo-1.4.5-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	exim-common-4.76-alt3.x86_64	symlink /usr/sbin/sendmail is a file in the package postfix-2.9.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.; symlink /usr/sbin/sendmail is a file in the package sendmail-submit-8.14.9-alt0.M70T.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	ibm-data-db2-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/IBM.Data.DB2.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/IBM.Data.DB2.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	info-install-4.13-alt9.x86_64	symlink /usr/share/info/dir is a file in the package gforth-info-0.7.2-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	jboss-as-7.1.1-alt3_6jpp7.noarch	symlink /usr/bin/jboss-cli is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/jboss-modules.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/cli/main/jboss-as-cli-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/api/main/jboss-as-clustering-api-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/common/main/jboss-as-clustering-common-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/ejb3/infinispan/main/jboss-as-clustering-ejb3-infinispan-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/impl/main/jboss-as-clustering-impl-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/infinispan/main/jboss-as-clustering-infinispan-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/jgroups/main/jboss-as-clustering-jgroups-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/registry/main/jboss-as-clustering-registry-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/service/main/jboss-as-clustering-service-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/web/infinispan/main/jboss-as-clustering-web-infinispan-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/clustering/web/spi/main/jboss-as-clustering-web-spi-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/cmp/main/jboss-as-cmp-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/configadmin/main/jboss-as-configadmin-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/connector/main/jboss-as-connector-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/controller-client/main/jboss-as-controller-client-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/controller/main/jboss-as-controller-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/deployment-repository/main/jboss-as-deployment-repository-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/deployment-scanner/main/jboss-as-deployment-scanner-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/domain-http-error-context/main/jboss-as-domain-http-error-context-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/domain-http-interface/main/jboss-as-domain-http-interface-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/domain-management/main/jboss-as-domain-management-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/ee/deployment/main/jboss-as-ee-deployment-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/ee/main/jboss-as-ee-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/ejb3/main/jboss-as-ejb3-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/embedded/main/jboss-as-embedded-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/host-controller/main/jboss-as-host-controller-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jaxr/main/jboss-as-jaxr-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jaxrs/main/jboss-as-jaxrs-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jdr/main/jboss-as-jdr-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jdr/main/jboss-as-sos-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jmx/main/jboss-as-jmx-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jpa/main/jboss-as-jpa-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jpa/spi/main/jboss-as-jpa-spi-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jpa/util/main/jboss-as-jpa-util-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/jsr77/main/jboss-as-jsr77-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/logging/main/jboss-as-logging-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/mail/main/jboss-as-mail-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/management-client-content/main/jboss-as-management-client-content-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/modcluster/main/jboss-as-modcluster-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/naming/main/jboss-as-naming-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/network/main/jboss-as-network-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/osgi/main/jboss-as-osgi-service-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/platform-mbean/main/jboss-as-platform-mbean-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/pojo/main/jboss-as-pojo-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/process-controller/main/jboss-as-process-controller-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/protocol/main/jboss-as-protocol-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/remoting/main/jboss-as-remoting-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/sar/main/jboss-as-sar-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/security/main/jboss-as-security-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/server/main/jboss-as-server-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/threads/main/jboss-as-threads-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/transactions/main/jboss-as-transactions-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/web/main/jboss-as-web-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/webservices/main/jboss-as-webservices-server-integration-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; symlink /usr/share/jboss-as/modules/org/jboss/as/weld/main/jboss-as-weld-7.1.1.Final.jar is a file in the package jboss-as-vanilla-7.1.1-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.; 
warn	libatlas-devel-3.9.35-alt1.qa1.x86_64	symlink /usr/include/cblas.h is a file in the package libclapack-devel-3.2.1-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; symlink /usr/include/clapack.h is a file in the package libclapack-devel-3.2.1-alt2.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	libmpg123-devel-1.13.4-alt2.x86_64	symlink /usr/lib64/libmpg123.so is a file in the package kdemultimedia-arts-3.5.13.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	mono-basic-2.10-alt1.x86_64	symlink /usr/lib/mono/2.0/Microsoft.VisualBasic.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.VisualBasic.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-csharp-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Mono.CSharp.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.CSharp.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-data-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Mono.Data.Tds.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Novell.Directory.Ldap.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Data.DataSetExtensions.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Data.Linq.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Data.Services.Client.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Data.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.DirectoryServices.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.EnterpriseServices.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.Data.Tds.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Novell.Directory.Ldap.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Data.DataSetExtensions.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Data.Linq.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Data.Services.Client.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Data.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.DirectoryServices.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.EnterpriseServices.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/WebMatrix.Data.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-data-oracle-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/System.Data.OracleClient.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Data.OracleClient.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-data-postgresql-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Npgsql.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Npgsql.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-data-sqlite-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Mono.Data.Sqlite.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.Data.Sqlite.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-devel-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Microsoft.Build.Engine.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Microsoft.Build.Framework.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Microsoft.Build.Tasks.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Microsoft.Build.Utilities.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Mono.CompilerServices.SymbolWriter.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Mono.Debugger.Soft.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/PEAPI.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.Build.Engine.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.Build.Framework.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.Build.Tasks.v4.0.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.Build.Utilities.v4.0.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.Build.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.CSharp.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.CompilerServices.SymbolWriter.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.Debugger.Soft.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/PEAPI.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-extras-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Mono.Messaging.RabbitMQ.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Mono.Messaging.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/RabbitMQ.Client.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Configuration.Install.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Management.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Messaging.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.ServiceProcess.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.Messaging.RabbitMQ.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.Messaging.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/RabbitMQ.Client.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Configuration.Install.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Management.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Messaging.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Runtime.Caching.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.ServiceProcess.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Xaml.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-locale-extras-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/I18N.CJK.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/I18N.CJK.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-mvc-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/System.Web.DynamicData.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Web.Extensions.Design.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Web.Extensions.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Web.Mvc.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.DynamicData.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.Extensions.Design.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.Extensions.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-wcf-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/System.Data.Services.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.IdentityModel.Selectors.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.IdentityModel.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Runtime.Serialization.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.ServiceModel.Web.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.ServiceModel.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Data.Services.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.IdentityModel.Selectors.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.IdentityModel.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Runtime.DurableInstancing.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Runtime.Serialization.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.ServiceModel.Discovery.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.ServiceModel.Routing.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.ServiceModel.Web.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.ServiceModel.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-web-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Mono.Http.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.ComponentModel.DataAnnotations.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Runtime.Remoting.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Runtime.Serialization.Formatters.Soap.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Web.Abstractions.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Web.Routing.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Web.Services.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Web.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Microsoft.Web.Infrastructure.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.Http.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.ComponentModel.Composition.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.ComponentModel.DataAnnotations.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Runtime.Remoting.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Runtime.Serialization.Formatters.Soap.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.Abstractions.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.ApplicationServices.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.Routing.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.Services.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Web.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-winforms-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/Accessibility.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/Mono.WebBrowser.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Design.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Drawing.Design.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/2.0/System.Windows.Forms.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Accessibility.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/Mono.WebBrowser.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Design.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Drawing.Design.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Windows.Forms.DataVisualization.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/System.Windows.Forms.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono-winfxcore-2.10.11-alt3.x86_64	symlink /usr/lib/mono/2.0/WindowsBase.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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.; symlink /usr/lib/mono/4.0/WindowsBase.dll is a file in the package mono4-core-4.3.1.1-alt5.M70P.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	mono4-core-debuginfo-4.3.1.1-alt5.M70P.1.x86_64	symlink /usr/lib/debug/usr/bin/mono.debug is a file in the package mono-debuginfo-2.10.11-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.; symlink /usr/lib/debug/usr/lib64/libmono-2.0.so.1.0.0.debug is a file in the package libmono-debuginfo-2.10.11-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	mysql-workbench-gpl-debuginfo-5.2.47-alt1.M70P.2.x86_64	symlink /usr/lib/debug/usr/lib64/mysql-workbench/libwbscintilla.so.debug is a file in the package mysql-workbench-community-debuginfo-6.3.4-alt0.M70T.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	nss_ldap-debuginfo-265-alt3.x86_64	symlink /usr/lib/debug/lib64/libnss_ldap.so.2.debug is a file in the package nss-ldapd-debuginfo-0.8.14-alt0.M70P.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	plexus-cli14-1.0.10-alt9.a13_5jpp6.noarch	symlink /usr/share/java/plexus/cli.jar is a file in the package plexus-cli-1.2-alt3_12jpp7.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	slocate-debuginfo-0.2.16-alt1.qa1.x86_64	symlink /usr/lib/debug/usr/bin/locate.debug is a file in the package mlocate-debuginfo-0.23.1-alt1.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	ssmtp-debuginfo-2.64-alt3.x86_64	symlink /usr/lib/debug/usr/sbin/sendmail.debug is a file in the package postfix-debuginfo-2.9.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	swi-prolog-5.6.15-alt1.qa2.x86_64	symlink /usr/bin/pl is a file in the package gnustep-base-1.24.6-alt3.svn20140126.M70T.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	swi-prolog-debuginfo-5.6.15-alt1.qa2.x86_64	symlink /usr/lib/debug/usr/bin/pl.debug is a file in the package gnustep-base-debuginfo-1.24.6-alt3.svn20140126.M70T.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	texlive-extra-utils-2008.0-alt0.15.5.x86_64	symlink /usr/bin/oxdvi is a file in the package tetex-xdvi-2.0-alt12.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	vuze-4.2.0.2-alt1.noarch	symlink /usr/bin/azureus is a file in the package azureus-4.9.0.0-alt1_1jpp7.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	xmlrpc-client-3.1.3-alt5_2jpp7.noarch	symlink /usr/share/java/xmlrpc3-client.jar is a file in the package xmlrpc3-client-3.1.3-alt1_12jpp7.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	xmlrpc-common-3.1.3-alt5_2jpp7.noarch	symlink /usr/share/java/xmlrpc3-common.jar is a file in the package xmlrpc3-common-3.1.3-alt1_12jpp7.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	xmlrpc-server-3.1.3-alt5_2jpp7.noarch	symlink /usr/share/java/xmlrpc3-server.jar is a file in the package xmlrpc3-server-3.1.3-alt1_12jpp7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.;