http://bugzilla.suse.com/show_bug.cgi?id=1148622 http://bugzilla.suse.com/show_bug.cgi?id=1148622#c1 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |zypp-maintainers@suse.de Flags| |needinfo?(zypp-maintainers@ | |suse.de) --- Comment #1 from Ladislav Slezák --- Questions: I guess we could trigger removing the old version via weakremoval(libyui9) etc... in the base product. But I'm not sure if that would trigger the upgrade for both libyui-qt-pkg10 and libyui-ncurses-pkg10. In theory the solver could upgrade only one of them. Zypp maintainers, could you help us to solve the dependency/upgrade problem? Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148622 David Diaz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED URL| |https://trello.com/c/JaItPL | |y4 CC| |dgonzalez@suse.com Assignee|yast2-maintainers@suse.de |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148622 http://bugzilla.suse.com/show_bug.cgi?id=1148622#c4 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(zypp-maintainers@ | |suse.de) --- Comment #4 from Ladislav Slezák --- (In reply to Michael Schröder from comment #2)

Change the libyui-X-pkgY package so that it provides "libyui_pkg = Y" instead of just "libyui_pkg" and then add also add a

Conflicts: libyui_pkg < Y

to them so that the plugins stay in sync.

Um, the problem is that there is actually no real conflict. You can have installed both libyui*9 and libyui*10 in parallel, in theory there might other (non-YaST) 3rd party application linked against libyui9. In that case it's fine to have both of them in the system. We would rather need to fix the "yast2-packager -> libyui_pkg" dependency so it means something like "install libyui-*-pkg* in the same version as the yast2-ycp-ui-bindings is linked against". The problem is also that "install" dependency is a soft dependency (e.g. libyui-ncurses-pkg contains "Supplements: packageand(libyui-ncurses:yast2-packager)". And I'm not sure if adding "yast2-packager -> libyui_pkg = 10" dependency would upgrade both libyui-ncurses-pkg and libyui-qt-pkg if they are installed. Any hints? TIA! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148622 http://bugzilla.suse.com/show_bug.cgi?id=1148622#c6 --- Comment #6 from Ladislav Slezák --- (In reply to Lukas Ocilka from comment #5)

1. GUI

The fact, that libyui-qt is installed, is because some pattern wanted that.

BTW in GUI also the ncurses packages are installed. (Just to have a fallback when X does not start for whatever reason.)

This libyui-qt-9 MUST require libyui-9 New libyui-qt-10 MUST require libyui-10

That's OK, these dependencies are handled properly. We actually miss a dependency to enforce at upgrade the libyui-*-pkg in the version which is used by YaST (which is required by yast2-ycp-ui-bindings). Also the patterns usually use only the soft dependencies (Recommends/Suggests) so the solver is not required to select them. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148622 http://bugzilla.suse.com/show_bug.cgi?id=1148622#c8 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | --- Comment #8 from Stefan Hundhammer --- Maybe this would help: libyui10 conflicts libyui-qt-pkg9 libyui10 conflicts libyui-ncurses-pkg9 This would throw out the older pkg widgets when a new libyui base lib is installed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148622 http://bugzilla.suse.com/show_bug.cgi?id=1148622#c10 --- Comment #10 from Ladislav Slezák --- Side note: if somebody would like to build testing packages with additional Conflicts/Obsoletes/whatever keep in mind that the packages built in OBS will have a different package vendor and the solver might ignore them at upgrade. You will need to touch solver.dupAllowVendorChange in /etc/zypp/zypp.conf or use "zypper dup --allow-vendor-change". For upgrade using the YaST installer you could create a vendor file in /etc/zypp/vendors.d, like here https://github.com/yast/yast-migration/blob/afeea3caf58d3195acbcc0b411e2b780... we do for the openSUSE (Leap) => SUSE (SLE) packages. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148622 http://bugzilla.suse.com/show_bug.cgi?id=1148622#c12 --- Comment #12 from Michael Schröder --- Well, that's basically "we're switching from libyui-ncurses-pkg9 to libyui-ncurses-pkg", i.e. you're dropping the version suffix. That might not be a bad idea, as the ui bindings also are not versioned. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1148622 http://bugzilla.suse.com/show_bug.cgi?id=1148622#c14 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #14 from Ladislav Slezák --- The Obsoletes dependencies were added in - https://github.com/libyui/libyui-qt-pkg/pull/74 - https://github.com/libyui/libyui-ncurses-pkg/pull/29 The upgrade works fine now. -- You are receiving this mail because: You are on the CC list for the bug.