On Wed, Oct 01, 2008 at 03:22:25PM +0200, Susanne Oberhauser wrote:

Jano Kupec writes:

...

To anyone who uses 'zypper update' or 'zypper list-updates' without explicitly specifying the --type option: the default has been changed from 'patch' to 'package' since zypper 0.12.7

Is there a way to do package and patch updates in one run?

Actually this could be made to work. You would need to set the "update system" flag in the sat solver plus install all patch selectables that are not irrelevant. Cheers, Michael -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Duncan Mac-Vicar Prett writes:

Patches aren't installed. Actually if you update all packages, then none of the remaining patches should be relevant for your system, so they wont show as "needed".

A patch can trigger the installation of a pacakge that wasn't on your system before, can't it?

Patches are just a different view, where the grouping is by "problem" and not per package.

Sometimes the newest package is not good for everybody, and patches allow you to be selective on when to update a package and when not to update it. For example, when it comes to drivers, patches can allow you to select specific package versions for specific hardware versions, using the modalias, while the packages overclaim they were good for everything. Basically I think the package update is best for those repos that do not provide patches. So why did I ask wether they can be done both at the same time? To update all packages and to also get all additional changes that are triggered by the patches. However the most important thing to me is to tell in repos.d/*.conf wether to do package or patch updates per default on this or that repo, I have use cases for that. The other one (patches and packages in one run) to me is less important. S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Duncan, now I'm getting your point and why we are discussing: You are telling me how _we_, SUSE, are using patches today. I am talking about how we evaluated our partners to possibly use patches. In the past, we've had crazy ideas how to use patches to enable different systems that need different driver versions from one single repository. For example, if you had one common repository for acme corp and their hardware, there could be an acme-cool-box and an acme-laptop, and they'd need different versions of a foofoo KMP, like this: Patch 1 Name: acme-cool-box Version: 1 # maybe the name/version works different for patches, # but conceptually this has to exist. Supplements: modalias(kernel-$FLAVOR:pci:...) Requires: foofoo-KMP = 47.11 Patch 3: Name: acme-laptop Version: 1 Supplements: modalias(kernel-$FLAVOR:pci:...) Requires: foofoo-KMP = 47.13 And if ever an update is needed later for acme-cool-box: Patch 2 Name: acme-cool-box Version: 2 Supplements: modalias(kernel-$FLAVOR:pci:...) Requires: foofoo-KMP = 47.15 nota bene: the laptop won't get the update, and this is intentional! Nobody has ever done this, as a) libzypp didn't handle it yet when we decided hwo to implement driver kits and b) we felt individual repos for the acme box easyer to maintain than the above. So nobody has ever done this, so far, and the plan is to stay with seperate repos for different products. What I'm getting from your helpfull comments is that nobody has ever intended patches to be used like this. From the discussion I'm also understanding that all kinds of weird stuff may happen if someone actually tries this, as libzypp may make assumptions that the above is never done. So thx again for your explanations, they helped to understand which route to go ;) S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Dňa Sunday 05 October 2008 00:13:37 Cristian Rodríguez ste napísal:

Duncan Mac-Vicar Prett escribió:

...

Susanne Oberhauser wrote:

...

Duncan Mac-Vicar Prett writes:

A patch can trigger the installation of a pacakge that wasn't on your system before, can't it?

No

Yes, they do, or at least they did the last time I tested it, it was pulling the "recommended" packages that werent installed previously, I was told that it wasnt a bug (!!)

The only way to drag in new packages is if the updated package has new dependencies AFAIK. Patch itself does not have dependencies anymore. Stano -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org