On Mon, Apr 13, 2009 at 05:11:55PM -0400, Ken Schneider - openSUSE wrote:

Michael Roberts pecked at the keyboard and wrote:

...

For some time now, zypper lu reports have been inconsistent with zypper up actions. The liboil problem has been around for some time, disappearing sometimes after an update and then reappearing, bashdb is new just now. Running OpenSUSE 11.0. Can I (or should I in the case of raising a bug report) do anything about this?

xxx> zypper lu -t package Reading installed packages... S | Repository | Name | Version | Arch --+--------------------+--------------+----------------+------- v | Packman Repository | bashdb | 4.0_0.3-0.pm.0 | x86_64 v | Packman Repository | liboil-0_3-0 | 0.3.16-0.pm.1 | x86_64 v | Packman Repository | liboil-devel | 0.3.16-0.pm.1 | x86_64 xxx> sudo zypper up -t package Reading installed packages... Nothing to do. xxx>

This usually happens when some dependency cannot be satisfied and zypper stops with giving the error. Try using YOU to do the update to find out what error might be involved.

It would actually report the error I think, so it is strange. Btw, run both as "root" to check if there isn't something root-nonroot interaction breaking it. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Apr 13, 2009 at 04:30:58PM -0500, Rajko M. wrote:

On Monday 13 April 2009 04:17:16 pm Marcus Meissner wrote:

...

Btw, run both as "root" to check if there isn't something root-nonroot interaction breaking it.

Which means don't use sudo on openSUSE? (or I'm wrong)

WHich means: Run "zypper lu" and "zypper lu" as the same user and not just one as root and one not. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 14 April 2009 01:34:41 Rajko M. wrote:

Why is difference in output of command echo?

Because $HOME gets evaluated before sudo is called. The call is translated by bash to sudo echo /home/rm Try sudo bash -c 'echo $HOME' The apostrophes prevent bash from translating it before passing it on to sudo Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Apr 14, 2009 at 02:03:39AM +0200, Michael Roberts wrote:

2009/4/14 Rajko M. :

...

On Monday 13 April 2009 04:41:17 pm Marcus Meissner wrote:

...

On Mon, Apr 13, 2009 at 04:30:58PM -0500, Rajko M. wrote:

...

On Monday 13 April 2009 04:17:16 pm Marcus Meissner wrote:

...

Btw, run both as "root" to check if there isn't something root-nonroot interaction breaking it.

Which means don't use sudo on openSUSE? (or I'm wrong)

WHich means: Run "zypper lu" and "zypper lu" as the same user and not just one as root and one not.

You really have good eye. I missed difference between xxx> and xxx> sudo ...

Yes well spotted, but running both with sudo (self-configured to allow zypper to run as root without password) gives the same output:

xxx> sudo zypper lu -t package Reading installed packages... S | Repository | Name | Version | Arch --+--------------------+--------------+----------------+------- v | Packman Repository | bashdb | 4.0_0.3-0.pm.0 | x86_64 v | Packman Repository | liboil-0_3-0 | 0.3.16-0.pm.1 | x86_64 v | Packman Repository | liboil-devel | 0.3.16-0.pm.1 | x86_64 xxx> sudo zypper up -t package Reading installed packages... Nothing to do.

This looks like a bug then. zypper.log file and/or solver testcase -> Bugzilla. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Michael Roberts wrote:

2009/4/14 Marcus Meissner :

...

On Tue, Apr 14, 2009 at 02:03:39AM +0200, Michael Roberts wrote:

...

... This looks like a bug then.

zypper.log file and/or solver testcase -> Bugzilla.

Ciao, Marcus

Thanks for the reminder about what data to submit with a zypper bug. Anders Johansson has found an existing report of this problem (see parallel mail) and it looks fixed in 11.1:

https://bugzilla.novell.com:443/show_bug.cgi?id=429157

Yes, the issue was discussed at http://lists.opensuse.org/opensuse-softwaremgmt/2008-07/msg00005.html and it's fixed in 11.1. -- cheers, jano Ján Kupec YaST team ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz ---------------------------------------------------------(EOF)---

2009/4/13 Ken Schneider - openSUSE :

Michael Roberts pecked at the keyboard and wrote:

...

For some time now, zypper lu reports have been inconsistent with zypper up actions. ...

This usually happens when some dependency cannot be satisfied and zypper stops with giving the error. Try using YOU to do the update to find out what error might be involved.

Well I selected "Online Updates" from Yast. That opens the "Patch Selection - YAST" dialog which currently shows no updates. There is a selector at bottom left which says "Patches" but the up-arrow and down-arrow do not offer any other choices, so that is not going to help with Packages. Did you mean something else? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

2009/4/13 Anders Johansson :

On Monday 13 April 2009 21:23:15 Michael Roberts wrote:

...

xxx> zypper lu -t package Reading installed packages... S | Repository         | Name         | Version        | Arch --+--------------------+--------------+----------------+------- v | Packman Repository | bashdb       | 4.0_0.3-0.pm.0 | x86_64 v | Packman Repository | liboil-0_3-0 | 0.3.16-0.pm.1  | x86_64 v | Packman Repository | liboil-devel | 0.3.16-0.pm.1  | x86_64 xxx> sudo zypper up -t package Reading installed packages... Nothing to do. xxx>

What happens if you try "zypper in bashdb".

My guess is that you get a warning that the package is about to change vendor.

It seems packman changed the vendor string in bashdb, and zypper will generally not install a package from a vendor not previously listed in its vendor file, unless you force it (with zypper in).

You are right about the change of vendor (output below.) In that case I think it is a bug for zypper up not to report the reason for its inaction -- particularly once zypper lu is reporting an update. (I said 'no' to the installations so we can continue to look at this.) xxx> sudo zypper in bashdb Reading installed packages... The following package is going to be upgraded: bashdb The following package is going to change vendor: bashdb Overall download size: 249.0 K. After the operation, additional 3.0 K will be used. Continue? [YES/no]: n xxx> sudo zypper in liboil Reading installed packages... Nothing to do. xxx> sudo zypper in liboil-devel Reading installed packages... The following packages are going to be upgraded: liboil-devel liboil-0_3-0 The following packages are going to change vendor: liboil-devel liboil-0_3-0 Overall download size: 265.0 K. After the operation, additional 13.0 K will be used. Continue? [YES/no]: n xxx> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

2009/4/14 Anders Johansson :

On Tuesday 14 April 2009 01:56:07 Michael Roberts wrote:

...

You are right about the change of vendor (output below.) In that case I think it is a bug for zypper up not to report the reason for its inaction -- particularly once zypper lu is reporting an update.

Yes, I agree. This seems to be

https://bugzilla.novell.com:443/show_bug.cgi?id=429157

I'm not sure, I don't have 11.0 here to try it out. In 11.1, I simply don't see the updates with 'zypper lu' when the vendor field has changed.

Yes that is it, sounds as if it is fixed along with package/patch inconsistencies in 11.1. It appears as no 7 in the list when searching for "zypper up", but not if the search string includes "lu" -- I must try a bit harder to find similar bug entries...

The real bug here I think is to get the packman packagers to not change their 'vendor' field all the time. It seems the OBS does this on occasion too, which is nasty

Yes I'm sure that would be helpful. How can we 'encourage' more stability in the 'vendor' field? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org