[Bug 1080244] New: conflict of liberation-fonts and liberation2-fonts
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244 Bug ID: 1080244 Summary: conflict of liberation-fonts and liberation2-fonts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: thomas.schraitle@suse.com Reporter: sbrabec@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When calling zypper dup, I got an upgrade problem: Problem: suse-xsl-stylesheets-2.0.8-2.1.noarch requires liberation-fonts, but this requirement cannot be provided uninstallable providers: liberation-fonts-1.07.4-1.8.noarch[repo-oss] Solution 1: Following actions will be done: deinstallation of suse-xsl-stylesheets-2.0.8-1.4.noarch deinstallation of daps-2.4.0-3.5.noarch Solution 2: deinstallation of liberation2-fonts-2.00.1-7.8.noarch Solution 3: keep obsolete suse-xsl-stylesheets-2.0.8-1.4.noarch Solution 4: break suse-xsl-stylesheets-2.0.8-2.1.noarch by ignoring some of its dependencies I tried 2, and it works, but I am not sure whether it is correct. It looks as downgrade. In any case, it indicates missing Obsoletes or Provides in the spec file and blocks seamless Tumbleweed update. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c1
Thomas Schraitle
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c2
--- Comment #2 from Thomas Schraitle
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c4
Dominique Leuenberger
I have opened an SR for the liberation-fonts package at:
https://build.opensuse.org/request/show/574628
Dominique, would you mind having a look too? I was only 90% sure of what I was doing.
This SR is an option, but not strictly nescessary - since suse-xsl-stylesheets with the dep changed to liberation-fonts is now in TW, I can drop liberation2-fonts there, which would result in an automatic (weak) obsoletes by openSUSE-release. Your SR is not wront per se though, and can be used to further aid the migration 'back' to liberation-fonts' -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c7
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c8
--- Comment #8 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c9
--- Comment #9 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c10
--- Comment #10 from Thomas Schraitle
I may be wrong but it seems to me that (with this patch) unoconv and suse-xsl-stylesheets cannot be installed together at the moment on Leap 42.3.
I think that is a side effect related to the change in bsc#1044521. I don't think this has anything to do with the unoconv package. There aren't files or requirements which conflicts with suse-xsl-stylesheets. @sknorr: can you confirm this? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c12
--- Comment #12 from Tony Mechelynck
I think this issue exists because LibO 6.0 was packaged with a dependency on liberation-fonts while 5.4 had a dependency on liberation2-fonts. Essentially, you can now either: * update LibO and delete suse-xsl-stylesheets or * keep the old version of LibO and also keep the stylesheets
I am not quite sure how to resolve that. I could update the stylesheets to require liberation-fonts again, but then you would be unable to keep your old LibO enabled.
As a user (not a developer) I can do without the "old" libreoffice if I can get the "new" one. Especially if it installs with no conflict. This would IIUC (or would it?) reverse the fix in boo#1044521 (sorry, let's be installation-agnostic, in bug #1044521) but it's not for me to decide if "the way of the future" is from liberation-fonts to liberation2-fonts or vice-versa.
Or I could submit the changes from https://build.opensuse.org/request/show/574628 to Leap 42.3 as well but I am unsure what will happen then, as both liberation-fonts and liberation2-fonts are still available in 42.3.
Again as a user and not a developer I would feel ill at ease if I knew that a long-run divergence is creeping between the packages in Tumbleweed and in Leap. Maybe (but it isn't for me to decide) this is the right time to decide which one of liberation-fonts and liberation2-fonts is the best for both Tumbleweed and Leap, and do away with the other after making sure that the change won't create conflicts in other packages. However, this might be too big a change for 42.3, and it may or may not be too late for Leap 15.0 ("package freeze April 24, final submission deadline May 14, release end of May").
Tomas, as the most likely packager of LibO -- do you have ideas?
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c13
--- Comment #13 from Thomas Schraitle
However, this might be too big a change for 42.3, and it may or may not be too late for Leap 15.0 ("package freeze April 24, final submission deadline May 14, release end of May").
As far as I know, the change is already in Factory and as such also in Leap 15.0. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c14
Jon Stephens
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c15
Carlos Robinson
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c16
Thomas Schraitle
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c17
Tony Mechelynck
according to bsc#1044521, this seems to be fixed, so I'll close this bug now. Just reopen it if I'm mistaken. :)
*** This bug has been marked as a duplicate of bug 1044521 ***
Bug 1044521 was VERIFIED FIXED on 2017-06-18 while this bug was reported on 2018-02-09. IMHO it cannot be a duplicate of a bug fixed several months before it was reported, especially since this bug was reported for Tumbleweed then seen also (comment #7) on 42.3 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c18
--- Comment #18 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
Jon Stephens
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244
http://bugzilla.opensuse.org/show_bug.cgi?id=1080244#c22
--- Comment #22 from Tony Mechelynck
participants (1)
-
bugzilla_noreply@novell.com