* Moby <moby@mobsternet.com> [07-28-15 23:36]:

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

...

* Moby <moby@mobsternet.com> [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. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dimstar / Dominique Leuenberger <dimstar@opensuse.org> writes:

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

...

* Moby <moby@mobsternet.com> [07-28-15 23:36]:

...

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

...

* Moby <moby@mobsternet.com> [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.

But it doesn't matter here, since it's /usr/lib64/YaST2/plugin/libpy2Pkg.so.2 that's out of date. 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 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, -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>

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 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. Without you posting the repo list, 2 can't be ruled out. If the repos are really all correct, and zypper dup indeed does not propose the removal by itself, then this would be a zypper bug, worthy to be reported. Cheers, -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>

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

Dimstar / Dominique Leuenberger <dimstar@opensuse.org> 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.

-- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>

* Moby <moby@mobsternet.com> [07-29-15 15:59]:

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 <dimstar@opensuse.org> 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.

note: Tumbleweed != Factory != Tumbleweed It did but does NOT now. Tumbleweed comes from Factory, after testing. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Moby <moby@mobsternet.com> [07-29-15 19:07]: [...]

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?

Then you need to use obs and provide tw builds or prevail on the goodness of another to do the same. And you might request the packager of samba STABLE to provide a Tw build, probably a miniminal effort for him/her. If you take this route, you will have to find the email addr for the current packager. It is there. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- 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 16:29 -0400, Patrick Shanahan wrote:

* Moby <moby@mobsternet.com> [07-29-15 15:59]:

...

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 <dimstar@opensuse.org> 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.

note: Tumbleweed != Factory != Tumbleweed

Stop spreading this rumor Patrick! If you look/understand in OBS on what it actually means to build against openSUSE:Tumbleweed, you'd know how very wrong you are. A project that is built against openSUSE:Tumbleweed/standard in fact is nothing different as any other project that builds against openSUSE:Factory/snapshot and this, because:

osc meta prj openSUSE:Tumbleweed <repository name="standard" rebuild="direct"> <path project="openSUSE:Factory" repository="snapshot"/> <arch>i586</arch> <arch>x86_64</arch> </repository>

So, please, STOP spreading this silly rumor that Factory would not be Tumbleweed... and: NO: /snapshot is NOT related in any way to the 'released' FTP tree of TW (unfortunately). As for Moby: you are certainly saer to add any Factory repository than any 13.2 repository. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Wed, 29 Jul 2015 15:40:40 +0200 Dimstar / Dominique Leuenberger <dimstar@opensuse.org> пишет:

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.

On Thu, Jul 30, 2015 at 10:45 AM, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:

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

...

В Wed, 29 Jul 2015 15:40:40 +0200 Dimstar / Dominique Leuenberger <dimstar@opensuse.org> пишет:

...

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...

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.

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.

As long as I can believe sources (I do not claim to read them all) it removes packages that are marked as weakremover in https://build.opensuse.org/package/view_file/openSUSE:Factory/_product:openS.... I suppose any RPM can Provide: weakremover(xxx), not only this one, but I am not sure. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dimstar / Dominique Leuenberger <dimstar@opensuse.org> writes:

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.

IIRC it will first ask you how to resolve the conflict. Only if the package is marked as weakremover in the release package it will be remove automatically. 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

* Moby <moby@mobsternet.com> [07-28-15 23:36]:

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

...

* Moby <moby@mobsternet.com> [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. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dimstar / Dominique Leuenberger <dimstar@opensuse.org> writes:

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

...

* Moby <moby@mobsternet.com> [07-28-15 23:36]:

...

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

...

* Moby <moby@mobsternet.com> [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.

But it doesn't matter here, since it's /usr/lib64/YaST2/plugin/libpy2Pkg.so.2 that's out of date. 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