On 07/28/2015 07:04 PM, Patrick Shanahan wrote:

* Moby [07-28-15 19:47]:

...

Latest Tumbleweed continues to have the yast issue, whereby running anything in yast produces the error: /usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2Pkg.so.2: undefined symbol: _Z16should_be_loggediRKSs You may have something wrong locally. I have no problem with yast/yast2 in tw.20150727 x86_64. Possibly but not sure and where -.. /usr/loca/libXXX are empty as someone had asked to check prior. Not even sure where to look for this.

-- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, 2015-07-29 at 07:37 -0400, Patrick Shanahan wrote:

* Moby [07-28-15 23:36]:

...

On 07/28/2015 07:04 PM, Patrick Shanahan wrote:

...

* Moby [07-28-15 19:47]:

...

Latest Tumbleweed continues to have the yast issue, whereby running anything in yast produces the error: /usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2Pkg.so.2: undefined symbol: _Z16should_be_loggediRKSs You may have something wrong locally. I have no problem with yast/yast2 in tw.20150727 x86_64. Possibly but not sure and where -.. /usr/loca/libXXX are empty as someone had asked to check prior. Not even sure where to look for this.

I don't know how that is relevant, but mine are, also.

It's relevant insofar that libraries in there have priority over libraries in /usr/libXX - any lib with the same name there can break functionality provided. Cheers, Dominique -- Dimstar / Dominique Leuenberger

On 07/29/2015 02:32 AM, Dimstar / Dominique Leuenberger wrote:

On Tue, 2015-07-28 at 18:46 -0500, Moby wrote:

...

Latest Tumbleweed continues to have the yast issue, whereby running anything in yast produces the error: /usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2Pkg.so.2: undefined symbol: _Z16should_be_loggediRKSs Very likely another package not updated. Please paste the outputs of:

...

rpm -q yast2-core yast2-pkg-bindings (you should have yast2-core-3.1.17-3.3 and yast2-pkg-bindings-3.1.27 -1.1)

...

zypper lu if you are fully updated, you should not see any output

...

zypper lu -a Maybe something blocked and update - let's see what we get here

Cheers, Dominique Thanks to all who have replied so far, here is the output of the various commands requested:

rpm -qif /usr/lib64/YaST2/plugin/libpy2Pkg.so.2 gives: " Name : yast2-pkg-bindings Version : 3.1.20 Release : 8.1 Architecture: x86_64 Install Date: Sat 27 Jun 2015 10:55:54 AM CDT Group : System/YaST Size : 1792852 License : GPL-2.0 Signature : RSA/SHA256, Fri 26 Jun 2015 07:56:40 AM CDT, Key ID b88b2fd43dbdc284 Source RPM : yast2-pkg-bindings-3.1.20-8.1.src.rpm Build Date : Thu 18 Jun 2015 04:13:15 AM CDT Build Host : build78 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE Summary : YaST2 - Package Manager Access Description : This package contains a name space for accessing the package manager library in YaST2. Distribution: openSUSE 13.2 " rpm -q yast2-core yast2-pkg-bindings gives: " yast2-core-3.1.17-3.3.x86_64 yast2-pkg-bindings-3.1.20-8.1.x86_64 " zypper lu gives: " No updates found. " zypper lu -a gives 67 lines in the output - showing many packages out of date, including yast2-pkg-binding So now the question is why the packages are out of date - and on 3 different machines. All 3 machines have zpper ref followed by zypper dup done on them almost daily. The only packages showing locked are ModemManager and Plymouth - so not sure why all these other packages are not being updated. -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 07/29/2015 08:26 AM, Dimstar / Dominique Leuenberger wrote:

On Wed, 2015-07-29 at 08:21 -0500, Moby wrote:

...

rpm -qif /usr/lib64/YaST2/plugin/libpy2Pkg.so.2 gives: " Name : yast2-pkg-bindings Version : 3.1.20 Release : 8.1 Architecture: x86_64 Install Date: Sat 27 Jun 2015 10:55:54 AM CDT Group : System/YaST Size : 1792852 License : GPL-2.0 Signature : RSA/SHA256, Fri 26 Jun 2015 07:56:40 AM CDT, Key ID b88b2fd43dbdc284 Source RPM : yast2-pkg-bindings-3.1.20-8.1.src.rpm Build Date : Thu 18 Jun 2015 04:13:15 AM CDT Build Host : build78 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE Summary : YaST2 - Package Manager Access Description : This package contains a name space for accessing the package manager library in YaST2. Distribution: openSUSE 13.2 " I thought you run Tumbleweed? This package does NOT come from Tumbleweed, but from a 13.2 setup.

Verify your repositories (zypper lr --details) - at least something is fishy there.

...

zypper lu -a gives 67 lines in the output - showing many packages out of date, including yast2-pkg-binding

So now the question is why the packages are out of date - and on 3 different machines. All 3 machines have zpper ref followed by zypper dup done on them almost daily. The only packages showing locked are ModemManager and Plymouth - so not sure why all these other packages are not being updated. you could try to "zypper up yast2-pkg-binding" and see what kind of message you get.

My guess is that, due to invalid / incompatible repositories on your systems, zypper comes up with 'the best valid solution' - which is not the correct one... your repo list might give some clues on where things go wrong.

Cheers, Thanks Dominique. Doing zypper in yast2-pkg-bindings produced: " Problem: yast2-pkg-bindings-3.1.27-1.1.i586 requires libzypp.so.1505, but this requirement cannot be provided uninstallable providers: libzypp-15.9.0-1.1.i586[tumbleweed_oss] Solution 1: deinstallation of libyui-gtk-pkg6-2.43.2-2.8.1.i586 Solution 2: do not install yast2-pkg-bindings-3.1.27-1.1.i586 Solution 3: break yast2-pkg-bindings-3.1.27-1.1.i586 by ignoring some of its dependencies "

Choosing solution 1 brought down the correct bits to where Yast is working now. All 3 systems are almost identical with same repos etc. The repos are the standard tumbleweed ones with some factory ones for the kernel. Thanks again for your help -- --Moby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dimstar / Dominique Leuenberger writes:

libyu-gtk-pkg6 indeed no longer exists in Tumbleweed (YaST's GTK interface has not been maintained in a long time). There are two possibilities why this did not work here: a) zypper has a bug - and did not realize that it should get rid of this package, despite dist upgrade b) you have repositories around that carry old packages (like an old libzypp for example), which resulted in zypper seeing a valid option in not having to remove the package.

c) he didn't use zypper dup. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 07/29/2015 09:05 AM, Dimstar / Dominique Leuenberger wrote:

On Wed, 2015-07-29 at 16:02 +0200, Andreas Schwab wrote:

...

Dimstar / Dominique Leuenberger writes:

...

libyu-gtk-pkg6 indeed no longer exists in Tumbleweed (YaST's GTK interface has not been maintained in a long time). There are two possibilities why this did not work here: a) zypper has a bug - and did not realize that it should get rid of this package, despite dist upgrade b) you have repositories around that carry old packages (like an old libzypp for example), which resulted in zypper seeing a valid option in not having to remove the package. c) he didn't use zypper dup. which would assume that he mis-presented the case, as he wrote:

...

So now the question is why the packages are out of date - and on 3 different machines. All 3 machines have zypper ref followed by zypper dup done on them almost daily. It was a question of zypper handling the different repos etc. Manually updating the package fixed the issue, and I also found some other updates (e.g. systemd) which were not updating with zypper dup. All fixed now, many thanks for the help. I guess with Tumbleweed, if using some other factory repos, one does zypper dup but one should also watch what is missing updates with zypper lu. Lesson learned.

-- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 07/29/2015 03:29 PM, Patrick Shanahan wrote:

* Moby [07-29-15 15:59]:

...

...

On Wed, 2015-07-29 at 16:02 +0200, Andreas Schwab wrote:

...

Dimstar / Dominique Leuenberger writes:

...

libyu-gtk-pkg6 indeed no longer exists in Tumbleweed (YaST's GTK interface has not been maintained in a long time). There are two possibilities why this did not work here: a) zypper has a bug - and did not realize that it should get rid of this package, despite dist upgrade b) you have repositories around that carry old packages (like an old libzypp for example), which resulted in zypper seeing a valid option in not having to remove the package. c) he didn't use zypper dup. which would assume that he mis-presented the case, as he wrote:

...

So now the question is why the packages are out of date - and on 3 different machines. All 3 machines have zypper ref followed by zypper dup done on them almost daily. It was a question of zypper handling the different repos etc. Manually updating the package fixed the issue, and I also found some other updates (e.g. systemd) which were not updating with zypper dup. All fixed now, many

On 07/29/2015 09:05 AM, Dimstar / Dominique Leuenberger wrote: thanks for the help. I guess with Tumbleweed, if using some other factory repos, one does zypper dup but one should also watch what is missing updates with zypper lu. Lesson learned.

note: Tumbleweed != Factory != Tumbleweed

It did but does NOT now.

Tumbleweed comes from Factory, after testing.

I cleaned up all the repos and the systems are good now. However, I have one question. I use some repos (e.,g. http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_13...) for which I cannot find a "tumbleweed" repo - I see the one for openSUSE13.2 (which is what I am using), and I see one for factory etc but none for Tumbleweed. What should a Tumbleweed user do in this case? -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Moby writes:

I cleaned up all the repos and the systems are good now. However, I have one question. I use some repos (e.,g. http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_13...)

Why do you need network:samba:STABLE? It's already part of tumbleweed.

for which I cannot find a "tumbleweed" repo - I see the one for openSUSE13.2 (which is what I am using), and I see one for factory etc but none for Tumbleweed. What should a Tumbleweed user do in this case?

Remove it. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-30 09:20, Dominique Leuenberger wrote:

So, please, STOP spreading this silly rumor that Factory would not be Tumbleweed...

Perhaps we should agree on a name for the untested factory, which I call so here because i don't know how to name it. :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlW6DkQACgkQja8UbcUWM1wKJAD+LZDLQL9Izn0CERdptzTB6Giz tkqgh7Kt4OrHTm+uVVsA/2yLj+2spICbn6QL7s/vSOI5BEfqx1VPNmL6Ml/WKJOX =KMHJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, 2015-07-29 at 20:35 +0300, Andrei Borzenkov wrote:

В Wed, 29 Jul 2015 15:40:40 +0200 Dimstar / Dominique Leuenberger пишет:

...

On Wed, 2015-07-29 at 08:31 -0500, Moby wrote:

...

Thanks Dominique. Doing zypper in yast2-pkg-bindings produced: " Problem: yast2-pkg-bindings-3.1.27-1.1.i586 requires libzypp.so.1505, but this requirement cannot be provided uninstallable providers: libzypp-15.9.0 -1.1.i586[tumbleweed_oss] Solution 1: deinstallation of libyui-gtk-pkg6-2.43.2-2.8.1.i586 Solution 2: do not install yast2-pkg-bindings-3.1.27-1.1.i586 Solution 3: break yast2-pkg-bindings-3.1.27-1.1.i586 by ignoring some of its dependencies "

libyu-gtk-pkg6 indeed no longer exists in Tumbleweed (YaST's GTK interface has not been maintained in a long time). There are two possibilities why this did not work here: a) zypper has a bug - and did not realize that it should get rid of this package, despite dist upgrade

Well, zypper dup deletes only those packages explicitly marked for deletion. I also hardly consider not removing a library a bug - unless this library was explicitly Obsolete by something else.

Nope: dup deletes packages that cause issues during an upgrade and are no longer in the repositories added... at least, that's what zypper's man page sais and what it used to do: from man zypper: dist-upgrade (dup) [options] Perform a distribution upgrade. This command applies the state of (specified) repositories onto the system; upgrades (or even downgrades) installed packages to versions found in repositories, removes packages that are no longer in the repositories and pose a dependency problem for the upgrade, handles package splits and renames, etc. -- Dimstar / Dominique Leuenberger

On Thu, 2015-07-30 at 12:17 +0300, Andrei Borzenkov wrote:

...

Nope: dup deletes packages that cause issues during an upgrade and are no longer in the repositories added...

If this would be the case, this would be outright bug. I definitely do not want it to remove packages that were installed manually and are not contained in any repository.

IF they cause an update problem - DUP is supposed to get you the system in a healthy state.. if any of your manual packages hinder that, it has to move out of the way... irrespective where it comes from. DUP gives an overview of what it's doing: up to you to decide then if this is the right things it wants to do. -- Dimstar / Dominique Leuenberger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-29 15:31, Moby wrote:

All 3 systems are almost identical with same repos etc. The repos are the standard tumbleweed ones with some factory ones for the kernel.

Please post the output of "zypper lr --details". - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlW431QACgkQja8UbcUWM1x7bAD/RNvIiWkJfvCitXGjMc9y15db sMzWsxnnTv1Fo6N4gTcBAIHLxOR7gZ5B8iqsTRmdL0jQJ/lmdNnbRAxGik7kY6nL =wyiv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org