[yast-devel] yast2 --qt requires unavailable libyui6
RE: http://lists.opensuse.org/opensuse-factory/2015-10/msg00474.html Is requirement of unavailable libyui6 expected behavior on TW? Shouldn't presence of libyui7 and deps cause removal of libyui6 and deps? Is this a misfortune of following widespread recommendation to use up rather than dup to upgrade TW? # rpmqa yui libyui-ncurses-pkg7-2.48.1-1.1.x86_64 libyui-ncurses6-2.47.2-1.1.x86_64 libyui-ncurses7-2.47.4-1.1.x86_64 libyui-qt-graph6-2.44.3-1.4.x86_64 libyui-qt6-2.46.18-1.3.x86_64 libyui6-3.2.0-1.1.x86_64 libyui7-3.2.3-1.1.x86_64 # yast2 --qt # rpmqa qt | grep y libyui-qt-graph6-2.44.3-1.4.x86_64 libyui-qt6-2.46.18-1.3.x86_64 yast2-control-center-qt-3.1.5-2.3.x86_64 yast2-qt-branding-openSUSE-13.2-11.3.noarch # zypper rm libyui6 Loading repository data... Reading installed packages... Resolving package dependencies... The following 4 packages are going to be REMOVED: libyui-ncurses6 libyui-qt-graph6 libyui-qt6 libyui6 4 packages to remove. After the operation, 3.3 MiB will be freed. Continue? [y/n/? shows all options] (y): y (1/4) Removing libyui-qt-graph6-2.44.3-1.4 ....................................................................................[done] (2/4) Removing libyui-qt6-2.46.18-1.3 .........................................................................................[done] (3/4) Removing libyui-ncurses6-2.47.2-1.1 .....................................................................................[done] (4/4) Removing libyui6-3.2.0-1.1 ..............................................................................................[done] big41:~ # yast2 --qt Qt GUI wanted but not found, falling back to ncurses. # zypper in libyui6 Loading repository data... Reading installed packages... 'libyui6' not found in package names. Trying capabilities. No provider of 'libyui6' found. Resolving package dependencies... Nothing to do. # zypper in libyui-qt7 ... The following NEW package is going to be installed: libyui-qt7 2.46.20-1.1 ... (1/1) Installing: libyui-qt7-2.46.20-1.1 ......................................................................................[done] committingCommitResult (total 1, done 1, error 0, skipped 0, updateMessages 0) # zypper in libyui-qt-pkg7 The following NEW package is going to be installed: libyui-qt-pkg7 2.45.4-1.1 ... (1/1) Installing: libyui-qt-pkg7-2.45.4-1.1 ...................................................................................[done] committingCommitResult (total 1, done 1, error 0, skipped 0, updateMessages 0) # yast2 --qt # -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 16.10.2015 v 23:26 Felix Miata napsal(a):
RE: http://lists.opensuse.org/opensuse-factory/2015-10/msg00474.html
Is requirement of unavailable libyui6 expected behavior on TW? Shouldn't presence of libyui7 and deps cause removal of libyui6 and deps? Is this a misfortune of following widespread recommendation to use up rather than dup to upgrade TW?
Um, I'm not a packaging expert, but for me it looks like the dependency is somewhat broken: # rpm -q --obsoletes libyui7 yast2-libyui < 2.42.0 # rpm -q --provides libyui6 libyui.so.6()(64bit) libyui6 = 3.1.4-1.8 libyui6(x86-64) = 3.1.4-1.8 yast2-libyui = 2.42.0 So libyui7 does not obsolete libyui6 because the obsolete version does not match the libyui6 version... Martin? -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Mon, Oct 19, 2015 at 11:53 AM, Ladislav Slezak
Dne 16.10.2015 v 23:26 Felix Miata napsal(a):
RE: http://lists.opensuse.org/opensuse-factory/2015-10/msg00474.html
Is requirement of unavailable libyui6 expected behavior on TW? Shouldn't presence of libyui7 and deps cause removal of libyui6 and deps? Is this a misfortune of following widespread recommendation to use up rather than dup to upgrade TW?
Um, I'm not a packaging expert, but for me it looks like the dependency is somewhat broken:
# rpm -q --obsoletes libyui7 yast2-libyui < 2.42.0 # rpm -q --provides libyui6 libyui.so.6()(64bit) libyui6 = 3.1.4-1.8 libyui6(x86-64) = 3.1.4-1.8 yast2-libyui = 2.42.0
So libyui7 does not obsolete libyui6 because the obsolete version does not match the libyui6 version...
Nor it should - the versionned library packages exist exactly to enable multiple different major library versions to coexist. So having both libyui6 and libyui7 is absolutely normal - there could be users of libyui6 that are not yet (or never) ported to libyui7. For "normal" libraries dependency should automatically be added by RPM build. But apparently removal of libyui6 does not trigger any error due to unsatisfied "require". So the actual problem is in yast packaging - either it should manually include Requires for correct version(s) or RPM build should be extended to handle this library type. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 19.10.2015 v 12:47 Andrei Borzenkov napsal(a):
Nor it should - the versionned library packages exist exactly to enable multiple different major library versions to coexist. So having both libyui6 and libyui7 is absolutely normal - there could be users of libyui6 that are not yet (or never) ported to libyui7.
Oh, good point, I completely forgot about multiversion libs... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Fri, Oct 16, 2015 at 05:26:40PM -0400, Felix Miata wrote:
RE: http://lists.opensuse.org/opensuse-factory/2015-10/msg00474.html
Is requirement of unavailable libyui6 expected behavior on TW? Shouldn't presence of libyui7 and deps cause removal of libyui6 and deps? Is this a misfortune of following widespread recommendation to use up rather than dup to upgrade TW?
Hi! as others have mentioned, libyui7 intentionally does not obsolete libyui6. This is so that you are able to have them both used by different programs/libraries. For YaST, the requiring component is yast2-ycp-ui-bindings: # rpm -qia --requires yast2-ycp-ui-bindings Name : yast2-ycp-ui-bindings Version : 3.1.9 Release : 1.3 Architecture: x86_64 Install Date: Fri Oct 9 09:53:32 2015 ... libyui.so.7()(64bit) ... Then on the way down, libyui7.rpm requires 'yui_backend = 7' which can be fulfilled EITHER by libyui-ncurses7 OR libyui-qt7. I hope this explains the situation a bit. In the original Factory post, Kyrill was able to fix the problem once he remembered to query for "libyui". -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On Mon, Oct 19, 2015 at 3:02 PM, Martin Vidner
For YaST, the requiring component is yast2-ycp-ui-bindings:
# rpm -qia --requires yast2-ycp-ui-bindings Name : yast2-ycp-ui-bindings Version : 3.1.9 Release : 1.3 Architecture: x86_64 Install Date: Fri Oct 9 09:53:32 2015 ... libyui.so.7()(64bit) ...
Then on the way down, libyui7.rpm requires 'yui_backend = 7' which can be fulfilled EITHER by libyui-ncurses7 OR libyui-qt7.
In such cases it is custom to have package, like yast-qt, and associate it with the latest and current version. Then if user had installed libyui-qt6 *and* uast-qt in the past, update would update yast-qt which would pull in libyui-qt7. Otherwise how users are supposed to know what version number of the day they have to install? Or yast could simply go ahead at (propose to) install it itself when yast2 --qt is called. This would be more user friendly. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Felix Miata -
Ladislav Slezak -
Martin Vidner