Libreoffice-calc-5.2.3.3-16.1.x86_64 requires libuno_sal.so.3()(64bit), but this requirement cannot be provided As an intermediary step in the YAST update configuration, you may have to "break" LibreOffice 5.3.2.2, but that sounds more dramatic than it is and will correct itself automagically.Ĭode: # YaST2 conflicts list - generated 19:12:33 # Just install libreoffice-l10n-en I have it installed (together with its German counterpart libeoffice-l10n-de) it's only a language component. # YaST2 conflicts list END #That should not be a problem. break libreoffice-5.2.3.3-16.1.x86_64 by ignoring some of its dependencies Uninstallable providers: libreoffice-l10n-en-5.2.3.3-16.1.noarch Libreoffice-5.2.3.3-16.1.x86_64 requires libreoffice-l10n-en = 5.2.3.3, but this requirement cannot be provided So, indeed, locking LO 5.1.3.2 recommends itself as the safest solution for the time being, with or without upgrading to Leap 42.2.Ĭode: # YaST2 conflicts list - generated 16:15:07 # What makes it worse, if somebody having the bug upgrades to Leap 42.2 without locking LO 5.1.3.2, the upgrade will replace it with LO 5.1.5.2-12.1 without keeping 5.1.3.2, and he will lose the ability to easily go back from LO 5.1.5.2 to 5.1.3.2. In any case, for us lowly users, it is obviously NOT resolved. So - is there such info?Bug 1005336 was declared "resolved duplicate of bug 1006201" on Bugzilla, as I quoted in message #42.įrom that, it seemed to me that they had a solution (otherwise, the problem could hardly be regarded as "resolved") and were planning to include it in an update in the "near" future, as they wrote.īut maybe to just declare it as a duplicate of an internal bug was enough for them to call it resolved. If there is really some official info that a future version fixes the bug, I will unlock it. Personally I have locked my version to 5.1.3.2 in order to survive any potential updates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |