http://bugzilla.opensuse.org/show_bug.cgi?id=1128543 http://bugzilla.opensuse.org/show_bug.cgi?id=1128543#c1 --- Comment #1 from Carlos Gonzalez --- Any response? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1128543 http://bugzilla.opensuse.org/show_bug.cgi?id=1128543#c5 --- Comment #5 from Antoine Ginies --- The patch is on the github upstream repo but not in the patterns-yast-yast2_basis-20180409-lp150.3.1.x86_64.rpm package available for leap15. So this means that your are facing this issue, but there is already a fix available upstream to fix it. Last changelog are: * Thu Apr 26 2018 lnussel@suse.de - move yast2-fonts in the x11_yast pattern as it pulls in freetype and stuff related to it (boo#1090189) - remove kde and gnome conflicts in x11_yast pattern (boo#1090319) * Thu Apr 19 2018 lnussel@suse.de - Recommend chrony instead of ntp (bsc#936378) * Tue Apr 03 2018 sflees@suse.de - Suggest yast2-kdump on all arches (bsc#1078393) - yast2_install_wf shouldn't be a visible pattern (bsc#1081724) - Recommend yast2-support (bsc#1084073) - yast2-auth-server package should be recommended (bsc#1085330) * Wed Mar 14 2018 aginies@suse.com - remove yast2-vm from Recommends as it will be only install if this this is a sles-release (BSC#1083398) - version 20180314 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1128543 http://bugzilla.opensuse.org/show_bug.cgi?id=1128543#c7 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Ancor Gonzalez Sosa --- (In reply to Carlos Gonzalez from comment #6)

Half a year in github upstream, and no one has been able to fix it in actual Leap 15.0 package release?

Which is fully expected. Leap is not a rolling distro, so it doesn't automatically get all the changes in the packages or patterns done to the repositories or to the upstream projects. Traducing that to Github. Every pattern repository has a master branch where new activity takes place. Those changes are visible (almost) immediately in Tumbleweed and (in some cases) also in the next release of Leap. Of course, that change is not applied retrospectively to all the already released versions of Leap. If someone wants a certain change to be released as a maintenance update for already released versions. That person has to change the appropriate branch (not only the master one) and do some manual work. That's exactly the point of having a release-based distribution, as opposed to a rolling one like Tumbleweed.

...

Well, Leap 15.1 is on the way anyways. Do you think this issue could really be fixed at least by then?

Yes, as you can see here[1], Leap 15.1 includes a newer version of the YaST pattern that includes the changes mentioned on comment#5. [1] https://build.opensuse.org/package/show/openSUSE:Leap:15.1/patterns-yast So everything works as expected, the fix was submitted for the next version of Leap and for Tumbleweed. So it has been there in TW for a long time and will be there in the next Leap release. It was never submitted as a maintenance update for Leap 15.0 (it was not a critical bug or security problem, so it makes sense), so it was never released as an update for 15.0. -- You are receiving this mail because: You are on the CC list for the bug.