[softwaremgmt] zypper-0.12.7 update/list-updates now defaults to --type package
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 For more info see https://bugzilla.novell.com/show_bug.cgi?id=395480 cheers, jano -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Jano Kupec <jkupec@suse.cz> 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? Or even better, to configure which type of updtaes should be expected on a per repo basis? e.g. in /etc/zypp/repos.d/* I'd expect the openSUSE repo (or SLES or which ever base distro) to provide updates as patches and the smaller opensuse build serverhosted repos to host updates as packages. That's because I'd hope a single run of 'zypper update' to update my system in the Right Way, without me having to know that I have different types of repos, with different ways to update each of them. 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-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On Wed, Oct 01, 2008 at 03:22:25PM +0200, Susanne Oberhauser wrote:
Jano Kupec <jkupec@suse.cz> 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-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Susanne Oberhauser wrote:
Jano Kupec <jkupec@suse.cz> 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?
Or even better, to configure which type of updtaes should be expected on a per repo basis? e.g. in /etc/zypp/repos.d/*
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". Patches are just a different view, where the grouping is by "problem" and not per package. Duncan -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Duncan Mac-Vicar Prett <dmacvicar@suse.de> 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-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Susanne Oberhauser wrote:
Duncan Mac-Vicar Prett <dmacvicar@suse.de> writes:
A patch can trigger the installation of a pacakge that wasn't on your system before, can't it?
No
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.
No. Patch just conflict with the last version with the problem, so selecting the "patch" it will select the latest version of the packages (from the same vendor). If you are selecting an specific version of a package, then you are not operating over patches anymore. Also, making a patch require an exact version of the package would have no sense for a dependency solver, as then updating to a newer version of the package would break the patch, unless a new patch obsoletes it, which would be quite a lot of work and confusion.
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.
Also no. Patches did not had different packages for different hardware. It is the solver that selects the packages based on the modalias. modalias has nothing to do with patches.
Basically I think the package update is best for those repos that do not provide patches.
Technically, unless you select a patch manually, a full system "update" is no real difference between packages and patches since patches are not installed. The result of applying all patches has to be the same as the result of updating all packages. As I said, it is just a different view.
So why did I ask wether they can be done both at the same time?
Again, it is no difference.
To update all packages and to also get all additional changes that are triggered by the patches.
Those changes are zero AFAIK now. Scripts could had been a reason, but now scripts are in packages too...
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.
Again, it is just a different view on the system. The content is the same. Duncan -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Dňa Wednesday 01 October 2008 17:16:56 Duncan Mac-Vicar Prett ste napísal:
Susanne Oberhauser wrote:
Duncan Mac-Vicar Prett <dmacvicar@suse.de> writes:
To update all packages and to also get all additional changes that are triggered by the patches.
Those changes are zero AFAIK now. Scripts could had been a reason, but now scripts are in packages too...
... but not run automatically unless the package is installed via libzypp (clarification). Stano -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Stanislav Visnovsky wrote:
... but not run automatically unless the package is installed via libzypp (clarification).
Stano
Yes. The idea is, any post commit script is supplied with the package. (Here we are talking about scripts that can be run in postin because they block rpm or something) so they just go to some location. after the whole transaction, libzypp runs them one by one. If you are using plain rpm, you run them manually. Duncan -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+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-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
participants (6)
-
Duncan Mac-Vicar P. -
Duncan Mac-Vicar Prett
-
Jano Kupec -
Michael Schroeder -
Stanislav Visnovsky -
Susanne Oberhauser