-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For example, I have just updated LibreOffice from the LO Stable repo to 3.5.3 (I'm using oS 11.4). When running YOU, it wants to update a LibreOffice package with vendor change, and we have to assume that having LO components from different vendors might break things. Is this a bug in YOU, or is it intentional behaviour? #### YaST2 conflicts list - generated 2012-05-31 21:19:01 #### patch:libreoffice-34-5253.noarch conflicts with libreoffice-languagetool-es.noarch < 1.4-2.2.1 provided by libreoffice-languagetool-es-1.4-2.1.noarch [ ] do not install patch:libreoffice-34-5253.noarch [ ] Following actions will be done: install libreoffice-languagetool-es-1.4-2.2.1.noarch (with vendor change) obs://build.opensuse.org/LibreOffice --> openSUSE install libreoffice-languagetool-en-1.4-2.2.1.noarch (with vendor change) obs://build.opensuse.org/LibreOffice --> openSUSE install libreoffice-languagetool-1.4-2.2.1.noarch (with vendor change) obs://build.opensuse.org/LibreOffice --> openSUSE #### YaST2 conflicts list END ### The solution I use is "do not install patch libreoffice-34-5253.noarch", and inmediately taboo it. By the way, while I'm writing this, I still have the YOU conflicts dialog opened, and one CPU core pegs at 100%. Another bug? Another similar conflict happens because I have updated KDE from the KDE Stable repo, but YOU wants to update, with vendor change, dbus-1, kdebase4-openSUSE, and yast2-control-center; and if I accept this, I get a cascade of dependency conflicts. #### YaST2 conflicts list - generated 2012-05-30 12:13:25 #### patch:yast2-control-center-4200.noarch conflicts with yast2-control-center-qt.x86_64 < 2.20.2-1.3.1 provided by yast2-control-center-qt-2.19.3-4.1.x86_64 [x] do not install patch:yast2-control-center-4200.noarch [ ] Following actions will be done: install yast2-control-center-qt-2.20.2-1.3.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install yast2-control-center-2.20.2-1.3.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE patch:dbus-1-4962.noarch conflicts with dbus-1-devel.x86_64 < 1.4.1-7.8.1 provided by dbus-1-devel-1.4.1-7.1.x86_64 [x] do not install patch:dbus-1-4962.noarch [ ] Following actions will be done: install dbus-1-devel-1.4.1-7.8.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install dbus-1-32bit-1.4.1-7.8.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install dbus-1-1.4.1-7.8.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE patch:kdebase4-openSUSE-5043.noarch conflicts with kio_sysinfo-branding-openSUSE.x86_64 < 11.4-33.42.1 provided by kio_sysinfo-branding-openSUSE-11.4-33.3.3.x86_64 [ ] Following actions will be done: install kio_sysinfo-branding-openSUSE-11.4-33.42.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install kio_sysinfo-11.4-33.42.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install kdm-branding-openSUSE-11.4-33.42.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install kdelibs4-branding-openSUSE-11.4-33.42.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install kdebase4-workspace-branding-openSUSE-11.4-33.42.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install kdebase4-runtime-branding-openSUSE-11.4-33.42.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE install kdebase4-openSUSE-11.4-33.42.1.x86_64 (with vendor change) obs://build.opensuse.org/KDE --> openSUSE [x] do not install patch:kdebase4-openSUSE-5043.noarch #### YaST2 conflicts list END ### Should I report this in Bugzilla? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk/H0ngACgkQtTMYHG2NR9UekACdF8ZJHTAb3PXaOdQ7UdBSuJ9C zQsAn0LZ8HUUPw+DAknAHUZh18PyStNb =IQNG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org