On Thu, May 31, 2012 at 10:20:01PM +0200, Carlos E. R. wrote:
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.
This needs some design review, bug 736100 is opened for this. We need to change the solver if we decide to do this. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org