Cristian Rodríguez wrote:

El 28/02/14 19:12, Per Jessen escribió:

...

<rant on>

Tonight I deciced it was time to give our laptop an upgrade, I ran "zypper up", quickly glanced over the stuff to be done and said "yes". It's not the fastest of laptops any more, it took about 90 minutes until it suddenly changed mode and the "crescent" symbol started flahsing. I think that means suspended. I have no idea why it would suspend just like that, but when I tried to reboot it, it couldn't access root any more, so kernel panic. Oh well, I know what my Saturday morning is going to be spent on. I wish had so "no" to that upgrade.

<rant off>

Maybe it ran out of battery or somehow you disconnected the AC power + lid was closed,,,

Nope. The battery isn't very good any longer, so it's always hooked up to the mains. -- Per Jessen, Zürich (3.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen wrote:

On 2/28/2014 2:12 PM, Per Jessen wrote:

...

<rant on>

Tonight I deciced it was time to give our laptop an upgrade, I ran "zypper up", quickly glanced over the stuff to be done and said "yes". It's not the fastest of laptops any more, it took about 90 minutes until it suddenly changed mode and the "crescent" symbol started flahsing. I think that means suspended. I have no idea why it would suspend just like that, but when I tried to reboot it, it couldn't access root any more, so kernel panic. Oh well, I know what my Saturday morning is going to be spent on. I wish had so "no" to that upgrade.

<rant off>

What the heck is a crescent symbol. Is that like a Moon or something, indicating the sleeping?

Yup, crescent = half moon. https://en.wikipedia.org/wiki/Crescent -- Per Jessen, Zürich (3.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-03-01 09:08 (GMT+0100) Per Jessen composed:

I have now recovered the laptop to a point where it boots and gets me to the X login screen. I cannot login via X, but I have access via a console. Any hints on how to resume the upgrade in a safe manner?

(only tested on well working 13.1) # zypper verify Loading repository data... Reading installed packages... Dependencies of all installed packages are satisfied. When I upgrade, I typically start approximately thus (depending whether release version or Factory): # zypper -v in zypper libzypp libsolv-tools \ rpm glibc [mkinitrd|dracut] udev systemd \ openSUSE-release Those & the deps they pull are pretty good at avoiding the perils of an interrupted subsequent zypper dup or zypper up. -- "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: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-03-01 10:15 (GMT+0100) Per Jessen composed:

I still can't login though - my password is accepted, but then I'm fairly promptly returned to the login screen. It seems that I ought to continue with another "zypper up", but is that the best/correct approach?

I remember this happening on one or more of the mailing lists a year or somewhat less ago, but can't remember the cause or fix, 12.3 or Factory or something else. When logging into X, do you get kicked out no matter which session type you pick, or only for the one you actually want? And which, KDE? Gnome? LXDE? Mate? XFCE? KDE3? TDE? If KDE4, are all of kdebase4- [workspace|session|runtime] installed? Same problem if you try to login as root? -- "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: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Saturday 01 of March 2014 10:48:36 Per Jessen wrote:

Don't know, judging by /var/log/zypper.log, the upgrade was interrupted in the middle of installing some kde packages.

Try running xinit as root, then type su <username> startkde in the xterm. This should display error messages that point to the corrupted package. Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-03-01 10:48 (GMT+0100) Per Jessen composed:

...

If KDE4, are all of kdebase4-[workspace|session|runtime] installed?

Don't know, judging by /var/log/zypper.log, the upgrade was interrupted in the middle of installing some kde packages.

# rpm -qa | egrep 'kdm|kde' | sort kde-gtk-config-2.2.1-2.1.3.x86_64 kde4-filesystem-4.11-3.3.1.x86_64 kde4-kgreeter-plugins-4.11.6-107.1.x86_64 kdebase4-artwork-4.11.5-142.1.noarch kdebase4-libkonq-4.11.5-474.8.x86_64 kdebase4-openSUSE-13.1-6.9.11.x86_64 kdebase4-runtime-4.11.5-478.3.x86_64 kdebase4-runtime-branding-upstream-4.11.5-478.3.x86_64 kdebase4-session-4.11-2.4.1.noarch kdebase4-wallpaper-default-4.11.5-142.1.noarch kdebase4-workspace-4.11.6-107.1.x86_64 kdebase4-workspace-branding-upstream-4.11.6-107.1.x86_64 kdebase4-workspace-ksysguardd-4.11.6-107.1.x86_64 kdebase4-workspace-liboxygenstyle-4.11.6-107.1.x86_64 kdelibs4-4.11.5-480.3.x86_64 kdelibs4-branding-upstream-4.11.5-480.3.x86_64 kdelibs4-core-4.11.5-480.3.x86_64 kdenlive-0.9.6-2.1.3.x86_64 kdepimlibs4-4.11.5-478.4.x86_64 kdm-4.11.6-107.1.x86_64 kdm-branding-upstream-4.11.6-107.1.x86_64 libkde4-4.11.5-480.3.x86_64 libkdecore4-4.11.5-480.3.x86_64 libkdepimlibs4-4.11.5-478.4.x86_64 liblockdev1-1.0.3_git201003141408-25.1.2.x86_64 lockdev-1.0.3_git201003141408-25.1.2.x86_64 polkit-kde-agent-1-0.99.0-19.1.1.x86_64 # uname -a Linux big41 3.11.10-7-desktop #1 SMP PREEMPT Mon Feb 3 09:41:24 UTC 2014 (750023e) x86_64 x86_64 x86_64 GNU/Linux -- "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: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

jdd wrote:

Le 01/03/2014 10:15, Per Jessen a écrit :

...

I still can't login though - my password is accepted, but then I'm fairly promptly returned to the login screen. It seems that I ought to continue with another "zypper up", but is that the best/correct approach?

did you try to launch yast? when the second pass is not complete it usually sees it and continue

jdd

The 2nd pass? There's no yast involved here, I only ran "zypper yp". Anyway, with reckless abandon, I decided to run another "zypper up" which reported about 14 to-be-installed packages, some of them kde4* - this went fine, and I can now log in. Thanks for the hand-holding everyone. (I still don't like updates though.) -- Per Jessen, Zürich (4.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

This problem is very well known. i try to keep all systems up to date. problematical (and or self debugged) packages are frozen, e.g. ISDN, CAPI, asterisk.. On Mar 1 2014 11:08, jdd wrote:

Date: Sat, 01 Mar 2014 11:08:45 +0100 From: jdd To: opensuse@opensuse.org Subject: Re: [opensuse] Why I dislike upgrading ....

Le 01/03/2014 11:03, Per Jessen a écrit :

...

everyone. (I still don't like updates though.)

I have updates to do, and still repôrt them because I know it's too often a trial and error procedure... but it's not really a good idea, because as more as I wait, the upgrade become more difficult :-(

(I have 11.4, 12.1 and 12.3 remote machines to update to 13.1 :-((()

jdd

-- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 03/01/2014 07:10 AM, Per Jessen pecked at the keyboard and wrote:

Paul Neuwirth wrote:

...

This problem is very well known. i try to keep all systems up to date. problematical (and or self debugged) packages are frozen, e.g. ISDN, CAPI, asterisk..

Yes, I have to admit I avoid touching our asterisk box as much as possible. We don't have test hardware so can't test it

Perhaps use a VirtualBox VM for testing?

and any screw-up during an update would be a MAJOR issue. I also don't like touching my home mythtv boxes, problems here would make me most unpopular in the family :-(

-- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 2014-03-02 at 10:30 +0100, Per Jessen wrote:

Ken Schneider - openSUSE wrote:

...

On 03/01/2014 07:10 AM, Per Jessen pecked at the keyboard and wrote:

...

Paul Neuwirth wrote:

...

This problem is very well known. i try to keep all systems up to date. problematical (and or self debugged) packages are frozen, e.g. ISDN, CAPI, asterisk..

Yes, I have to admit I avoid touching our asterisk box as much as possible. We don't have test hardware so can't test it

Perhaps use a VirtualBox VM for testing?

Yes, I would do that for e.g. asterisk itself, but without the extra hardware (multi-port ISDN cards basically), the my testing would be way incomplete. This is probably an area that receives very little testing/attention during development.

Without any spare hardware it is nearly impossible to avoid awkward situations. At work, i tried to minimalize the impact... I separated the ISDN-trunk-line from the main PABX-functionality of asterisk. One box acting only as ISDB-bri gateway, and asterisk and the real-time-DB virtualized on other hardware. Instead of upgrading the asterisk-box, just make another virtual client, and when satisfied enough, switch one vm off, and have the new vm and the isdn-gw point to each other. hw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ellanios82 wrote:

On 03/01/2014 12:03 PM, Per Jessen wrote:

...

(I still don't like updates though.)

---

- perhaps it is less over-all sweat, following Tumbleweed's constant gradual updates?

Not for me, no thanks. Much too much work. -- Per Jessen, Zürich (6.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Greg Freemyer wrote:

Per Jessen wrote:

...

I still can't login though - my password is accepted, but then I'm fairly promptly returned to the login screen. It seems that I ought to continue with another "zypper up", but is that the best/correct approach?

Per,

You keep saying "zypper up"

Yes, I am updating a 12.3 system. My $SUBJ should have said "updating", not "upgrading". -- Per Jessen, Zürich (6.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Mar 1, 2014 at 12:37 PM, Greg Freemyer wrote:

On Sat, Mar 1, 2014 at 10:53 AM, Per Jessen wrote:

...

Greg Freemyer wrote:

...

Per Jessen wrote:

...

I still can't login though - my password is accepted, but then I'm fairly promptly returned to the login screen. It seems that I ought to continue with another "zypper up", but is that the best/correct approach?

Per,

You keep saying "zypper up"

Yes, I am updating a 12.3 system. My $SUBJ should have said "updating", not "upgrading".

In that case, zypper patch pulls exclusively updates from the official update repos only. It is a safer option than zypper up which can pull from any of the configured repos, and as such is more dangerous.

I sent that to fast. I meant to add that the repos "zypper patch" can pull is only those found at: http://download.opensuse.org/update/ which you can see is just the official update repos that the opensuse support team maintains. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 03/02/2014 04:33 AM, Per Jessen pecked at the keyboard and wrote:

Greg Freemyer wrote:

...

On Sat, Mar 1, 2014 at 12:37 PM, Greg Freemyer wrote:

...

On Sat, Mar 1, 2014 at 10:53 AM, Per Jessen wrote:

...

Greg Freemyer wrote:

...

Per Jessen wrote:

...

I still can't login though - my password is accepted, but then I'm fairly promptly returned to the login screen. It seems that I ought to continue with another "zypper up", but is that the best/correct approach?

Per,

You keep saying "zypper up"

Yes, I am updating a 12.3 system. My $SUBJ should have said "updating", not "upgrading".

In that case, zypper patch pulls exclusively updates from the official update repos only. It is a safer option than zypper up which can pull from any of the configured repos, and as such is more dangerous.

I sent that to fast. I meant to add that the repos "zypper patch" can pull is only those found at:

http://download.opensuse.org/update/

which you can see is just the official update repos that the opensuse support team maintains.

Greg

Yeah, I usually only play with other repos on systems I'm testing or debugging - for plain office machines like this laptop, I stick to vanilla openSUSE.

I appreciate your comments Greg - I've never used "zypper patch", I think I'll be switching to that.

You don't "switch" to using 'zypper patch', you use it as well as 'zypper up'. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

afaik, "zypper patch" only applies recommended or security updates. "zypper up" applies all available updates. i always check available packages using nagios, i use zypper patch to install only the urgent updates. On Mar 2 2014 17:51, Per Jessen wrote:

Date: Sun, 02 Mar 2014 17:51:55 +0100 From: Per Jessen To: opensuse@opensuse.org Subject: Re: [opensuse] Why I hate updating ....

Ken Schneider - openSUSE wrote:

...

On 03/02/2014 04:33 AM, Per Jessen pecked at the keyboard and wrote:

...

Greg Freemyer wrote:

...

On Sat, Mar 1, 2014 at 12:37 PM, Greg Freemyer wrote:

...

On Sat, Mar 1, 2014 at 10:53 AM, Per Jessen wrote:

...

Greg Freemyer wrote:

> > > Per Jessen wrote: > >> >> I still can't login though - my password is accepted, but then >> I'm >> fairly promptly returned to the login screen. It seems that I >> ought to continue with another "zypper up", but is that the >> best/correct approach? > > Per, > > You keep saying "zypper up"

Yes, I am updating a 12.3 system. My $SUBJ should have said "updating", not "upgrading".

In that case, zypper patch pulls exclusively updates from the official update repos only. It is a safer option than zypper up which can pull from any of the configured repos, and as such is more dangerous.

I sent that to fast. I meant to add that the repos "zypper patch" can pull is only those found at:

http://download.opensuse.org/update/

which you can see is just the official update repos that the opensuse support team maintains.

Greg

Yeah, I usually only play with other repos on systems I'm testing or debugging - for plain office machines like this laptop, I stick to vanilla openSUSE.

I appreciate your comments Greg - I've never used "zypper patch", I think I'll be switching to that.

You don't "switch" to using 'zypper patch', you use it as well as 'zypper up'.

Hmm, I'm not sure I quite get that - Greg says above "zypper patch pulls exclusively updates from the official update repos only.". As I mentioned, I generally only use the official repos anyway, so what would I use "zypper up" for?

-- Per Jessen, Zürich (5.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/03/14 04:37, Greg Freemyer wrote:

On Sat, Mar 1, 2014 at 10:53 AM, Per Jessen wrote:

...

Greg Freemyer wrote:

...

Per Jessen wrote:

...

I still can't login though - my password is accepted, but then I'm fairly promptly returned to the login screen. It seems that I ought to continue with another "zypper up", but is that the best/correct approach? Per,

You keep saying "zypper up"

Yes, I am updating a 12.3 system. My $SUBJ should have said "updating", not "upgrading". In that case, zypper patch pulls exclusively updates from the official update repos only. It is a safer option than zypper up which can pull from any of the configured repos, and as such is more dangerous.

I distinctly recall mentioning that I always do 'zypper refresh' then 'zypper patch' then 'zypper up' when somebody told me that I was "mad" because doing 'zypper up' was all that was required as 'up' included 'patch'. But your comment supports my actions of doing 'patch' as a separate step. Thanks for showing that I am not "mad" (as some may think :-) ). BC -- Secrecy is completely inadequate for democracy but totally appropriate for tyranny. If the minister will not inform the public, then we are within our right to assume the worst. Malcolm Fraser - Former Prime Minister of Australia, February 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. [03.03.2014 12:39]:

On 2014-03-03 05:04, Basil Chupin wrote:

You are not mad, but certainly it is a superfluous operation, as a "zypper up" includes what "zypper patch" would do. The "zypper ref" step is also unneeded, because the first zypper operation will do that automatically - unless you disabled automatic refresh.

Or unless the last refresh was less than 10 minutes ago. Or whatever time you set as repo.refresh.delay in /etc/zypp/zypper.conf :-)

But then, we will need to adjust that affirmation. A "zypper patch" could update some things, that the subsequent "zypper up" updates again, differently, because it considers other repos. The end result should be in any case the same as only doing a "zypper up".

I do not agree. As far as I see it, "zypper patch" also draws the latest packages from other repos. If "zypper patch" sees that package XYZ has to be patched, and that the update-repo contains XYZ-1.4.7, and another repo holds XYZ-1.4.9, it may as well install XYZ-1.4.9. At least it did for me :-\ If "zypper patch" updates only from the "official sources" including the update repo, a "zypper up" will not update the same packages again. Where should they be from? If the newer package version is from another repo, zypper regards this as "vendor change", and will not update this package (by default, because solver.allowVendorChange is set to false in /etc/zypp/zypper.conf). Instead, it puts a line "the following packages will NOT be updated" followed by the package list on the screen. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am 03.03.2014 14:15, schrieb Marcus Meissner:

On Mon, Mar 03, 2014 at 02:08:34PM +0100, Werner Flamme wrote:

...

Carlos E. R. [03.03.2014 12:39]:

...

On 2014-03-03 05:04, Basil Chupin wrote:

You are not mad, but certainly it is a superfluous operation, as a "zypper up" includes what "zypper patch" would do. The "zypper ref" step is also unneeded, because the first zypper operation will do that automatically - unless you disabled automatic refresh. Or unless the last refresh was less than 10 minutes ago. Or whatever time you set as repo.refresh.delay in /etc/zypp/zypper.conf :-)

...

But then, we will need to adjust that affirmation. A "zypper patch" could update some things, that the subsequent "zypper up" updates again, differently, because it considers other repos. The end result should be in any case the same as only doing a "zypper up". I do not agree. As far as I see it, "zypper patch" also draws the latest packages from other repos. If "zypper patch" sees that package XYZ has to be patched, and that the update-repo contains XYZ-1.4.7, and another repo holds XYZ-1.4.9, it may as well install XYZ-1.4.9.

At least it did for me :-\

If "zypper patch" updates only from the "official sources" including the update repo, a "zypper up" will not update the same packages again. Where should they be from? If the newer package version is from another repo, zypper regards this as "vendor change", and will not update this package (by default, because solver.allowVendorChange is set to false in /etc/zypp/zypper.conf). Instead, it puts a line "the following packages will NOT be updated" followed by the package list on the screen. You need to understand that a "patch" file for "zypper patch" basically only consists of rules:

PACKAGENAME >= NEWVERSION

So when "installing" the "patch" the update stack just ensures that the version of PACKAGENAME is same or higher than the NEWVERSION mentioned in the patch file.

If you have a package from a different repo or vendor, but with the same name, it will also try to update that to meet this requirement. And not just from the official update repository.

That might give confusions where the same package lives in the Update repo and in others that you have subscribed.

Ciao, Marcus

I'm following the discussion with interest, but I'm still confused ;) I always update my system by going to "yast2 --qt sw_single &". There I have the possibility to "Packages => Update all packages with newer Versions". What exactly is this happening then - zypper up - zypper patch - both Thanks Karl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

...

I'm following the discussion with interest, but I'm still confused ;)

LOL!

Surely not! :-D

(I've stopped using zypper because it keeps on insisting of installing kernel-desktop 3.11.x but I have kernel-desktop 3.13.x installed; so now I only use YaST and everything is back to being peaceful and normal :-) .)

:D happy to not be alone :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Basil Chupin [03-04-14 00:58]: [...]

(I've stopped using zypper because it keeps on insisting of installing kernel-desktop 3.11.x but I have kernel-desktop 3.13.x installed; so now I only use YaST and everything is back to being peaceful and normal :-) .)

zypper al kernel-desktop -r "openSUSE Current OSS" 3.13 is not in 13.1's "regular" or basic repos and as that deviates from the "norm", and adjustment is necessary. Another case of shooting everything that moves rather than the impending threat. But it does seem to be in caricature :^) -- (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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-03-03 14:08, Werner Flamme wrote:

Carlos E. R. [03.03.2014 12:39]:

...

But then, we will need to adjust that affirmation. A "zypper patch" could update some things, that the subsequent "zypper up" updates again, differently, because it considers other repos. The end result should be in any case the same as only doing a "zypper up".

I do not agree. As far as I see it, "zypper patch" also draws the latest packages from other repos. If "zypper patch" sees that package XYZ has to be patched, and that the update-repo contains XYZ-1.4.7, and another repo holds XYZ-1.4.9, it may as well install XYZ-1.4.9.

No, "zypper patch" does not consider other repos. That's the main practical difference.

At least it did for me :-\

If "zypper patch" updates only from the "official sources" including the update repo, a "zypper up" will not update the same packages again. Where should they be from? If the newer package version is from another repo, zypper regards this as "vendor change", and will not update this package (by default, because solver.allowVendorChange is set to false in /etc/zypp/zypper.conf). Instead, it puts a line "the following packages will NOT be updated" followed by the package list on the screen.

It depends. Sometimes a "zypper patch" wants to update a package which you already changed to another repository, generating a conflict. So if you first do a "patch" and later "up", first you get one update, later a different one. I have seen it happen. Maybe because "patch" does not respect vendor change (there was a bugzilla about that time ago), or because some of those extra repos have the same vendor string. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2014-03-03 15:00, Per Jessen wrote:

Carlos E. R. wrote:

...

You are not mad, but certainly it is a superfluous operation, as a "zypper up" includes what "zypper patch" would do.

I guess that's why I've never seen much reason to use zypper patch. Just now I updated an office desktop - zypper patch wanted to upgrade 4 packages, zypper up wanted to upgrade 332.

Me, on the contrary, never run "zypper up" :-) Now and then, I do selective updates using yast. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)