[opensuse] zypper dup
Just asking for a clarification regarding 'zypper dup'. Does running zypper dup also install any patches that would be installed using zypper patch? -- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-17 17:59, Ken Schneider - openSUSE wrote:
Just asking for a clarification regarding 'zypper dup'. Does running zypper dup also install any patches that would be installed using zypper patch?
It may. But it does not if there is a newer version on another repo. It is a dangerous command, don't use it for routine updates. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlMCSt0ACgkQja8UbcUWM1zH1gD/bn2VAMPh5/Aeqb4s9L6og/DA uCvoVLOUrT3II6eHZ+MA/RIqapQLDyICiukc/tLzyD44psWVjD7zvBCGeb6N8LyK =ishY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/17/2014 12:46 PM, Carlos E. R. pecked at the keyboard and wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-02-17 17:59, Ken Schneider - openSUSE wrote:
Just asking for a clarification regarding 'zypper dup'. Does running zypper dup also install any patches that would be installed using zypper patch?
It may.
Thanks, but not what I'm looking for, either it does or it doesn't. And to clarify further, if there is no newer package in another repo but there is a patch available will the patch get installed with zypper dup?
It is a dangerous command, don't use it for routine updates.
I never did and never will, I'm just making sure that newbees don't get fed wrong information. -- 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 Mon, Feb 17, 2014 at 01:45:08PM -0500, Ken Schneider - openSUSE wrote:
Thanks, but not what I'm looking for, either it does or it doesn't. And to clarify further, if there is no newer package in another repo but there is a patch available will the patch get installed with zypper dup?
Patches are basically version constraints, i.e. a patch enforces something like "for that package the version must at least be x.x-x". 'Zypper dup' is like 'zypper up', i.e. it tries to update each package to th newest version (considering repo priorities and so on). It does not look at the patches metadata, i.e. if the update to the newest versions works out, the patches might all be satisfied as well, but if there's a dependency problem and the newest version is not installable, it may also stay with an older version leading to an unsatisfied patch. So "may" is actually a good answer, most of the times all patches will be satisfied, but nothing is enforced. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[17.02.2014 19:45] [Ken Schneider - openSUSE]:
On 02/17/2014 12:46 PM, Carlos E. R. pecked at the keyboard and wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-02-17 17:59, Ken Schneider - openSUSE wrote:
Just asking for a clarification regarding 'zypper dup'. Does running zypper dup also install any patches that would be installed using zypper patch?
It may.
Thanks, but not what I'm looking for, either it does or it doesn't.
"It may" describes reality best. Maybe you are not content with this answer, but it is correct nevertheless. As far as my experience goes, even "zypper patch" does not always install all patches. A patch is always aimed at a certain version of a certain package. If you have another version of this package, the patch will most probably not be applied. And: if "zypper patch" finds a newer version of the package-to-be-patched in any other repository, this version might be installed instead. I saw both kinds of behaviour several times on my machines. Regarding the latest KDE 4.11 patch for 13.1 (openSUSE-RU-2014:0240-1): it pulled all the KDE 4.12 packages into the system (current tumbleweed), though the patches were for KDE 4.11-
And to clarify further, if there is no newer package in another repo but there is a patch available will the patch get installed with zypper dup?
As far as I know, the newer package will be installed instead of the patch. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/02/2014 20:03, Werner Flamme a écrit :
will most probably not be applied. And: if "zypper patch" finds a newer version of the package-to-be-patched in any other repository, this version might be installed instead. I saw both kinds of behaviour several times on my machines. Regarding the latest KDE 4.11 patch for 13.1 (openSUSE-RU-2014:0240-1): it pulled all the KDE 4.12 packages into the system (current tumbleweed), though the patches were for KDE 4.11-
And to clarify further, if there is no newer package in another repo but there is a patch available will the patch get installed with zypper dup?
As far as I know, the newer package will be installed instead of the patch.
this is pretty surprising, zypper patch (IMHO) should only do what he is aimed to: install patche"s, and only that and of course only the relevant ones. I beg he do not install ne version without asking? jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-17 20:15, jdd wrote:
Le 17/02/2014 20:03, Werner Flamme a écrit :
will most probably not be applied. And: if "zypper patch" finds a newer version of the package-to-be-patched in any other repository, this version might be installed instead. I saw both kinds of behaviour several times on my machines. Regarding the latest KDE 4.11 patch for 13.1 (openSUSE-RU-2014:0240-1): it pulled all the KDE 4.12 packages into the system (current tumbleweed), though the patches were for KDE 4.11-
this is pretty surprising, zypper patch (IMHO) should only do what he is aimed to: install patche"s, and only that and of course only the relevant ones.
That's my understanding as well. It is possible, though, that a patch needs to also install a package that is not already installed, and if vendor change is enabled, it may be so from another repo. And this action could bring further package from there. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlMCeJ8ACgkQja8UbcUWM1z1DAEAltWrMzfLDVIkGzFg5HzqZFeQ 9OKwDb48rVtmkWyUgM0A/jIN382mgOzvrPRoAxoEfXaIBb79x7LjN7VjZRVZoDWB =makc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Werner Flamme
"It may" describes reality best. Maybe you are not content with this answer, but it is correct nevertheless.
As far as my experience goes, even "zypper patch" does not always install all patches. A patch is always aimed at a certain version of a certain package. If you have another version of this package, the patch will most probably not be applied. And: if "zypper patch" finds a newer version of the package-to-be-patched in any other repository, this version might be installed instead. I saw both kinds of behaviour several times on my machines. Regarding the latest KDE 4.11 patch for 13.1 (openSUSE-RU-2014:0240-1): it pulled all the KDE 4.12 packages into the system (current tumbleweed), though the patches were for KDE 4.11-
Well, for Tw Gregg KH does emphasize using *only* "zypper dup". And has recently posted specifically advising against "zypper patch". -- (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 Monday, February 17, 2014 04:52:38 PM Patrick Shanahan wrote:
* Werner Flamme
[02-17-14 14:05]: [...] "It may" describes reality best. Maybe you are not content with this answer, but it is correct nevertheless.
As far as my experience goes, even "zypper patch" does not always install all patches. A patch is always aimed at a certain version of a certain package. If you have another version of this package, the patch will most probably not be applied. And: if "zypper patch" finds a newer version of the package-to-be-patched in any other repository, this version might be installed instead. I saw both kinds of behaviour several times on my machines. Regarding the latest KDE 4.11 patch for 13.1 (openSUSE-RU-2014:0240-1): it pulled all the KDE 4.12 packages into the system (current tumbleweed), though the patches were for KDE 4.11-
Well, for Tw Gregg KH does emphasize using *only* "zypper dup". And has recently posted specifically advising against "zypper patch".
So far it is understood TW is delivering the last packages of State of the Art on top of the openSUSE Stable platform. So it is, de facto, a full packages upgrade. Giving the same priority for the repos let install the needed packages for the openSUSE distribution base and then upgrade them to the last version. It gives the opportunity to not missing any package and dependencies on their way to get the last ones. Regards, -- R. Chung openSUSE Projects -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/17/2014 05:25 PM, Ricardo Chung pecked at the keyboard and wrote:
On Monday, February 17, 2014 04:52:38 PM Patrick Shanahan wrote:
* Werner Flamme
[02-17-14 14:05]: [...] "It may" describes reality best. Maybe you are not content with this answer, but it is correct nevertheless.
As far as my experience goes, even "zypper patch" does not always install all patches. A patch is always aimed at a certain version of a certain package. If you have another version of this package, the patch will most probably not be applied. And: if "zypper patch" finds a newer version of the package-to-be-patched in any other repository, this version might be installed instead. I saw both kinds of behaviour several times on my machines. Regarding the latest KDE 4.11 patch for 13.1 (openSUSE-RU-2014:0240-1): it pulled all the KDE 4.12 packages into the system (current tumbleweed), though the patches were for KDE 4.11-
Well, for Tw Gregg KH does emphasize using *only* "zypper dup". And has recently posted specifically advising against "zypper patch".
So far it is understood TW is delivering the last packages of State of the Art on top of the openSUSE Stable platform. So it is, de facto, a full packages upgrade. Giving the same priority for the repos let install the needed packages for the openSUSE distribution base and then upgrade them to the last version. It gives the opportunity to not missing any package and dependencies on their way to get the last ones.
Regards,
Thanks to everyone for their input. The use of using "dup" in regards to also pulling patches for installed packages is a little clearer. I know what to tell new users when the question comes 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-17 22:52, Patrick Shanahan wrote:
Well, for Tw Gregg KH does emphasize using *only* "zypper dup". And has recently posted specifically advising against "zypper patch"
Yes, but Tw is a factory derivative. You also are supposed to use "zypper dup" with factory, not "zypper patch". The stables releases are different: there you are supposed to use "zypper patch", or "zypper up". - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlMCn/UACgkQja8UbcUWM1wg3QD+Jr+4N1BrATLvWn67ADMDd9W9 4R72CuJhJ6SeqQI4vYUA/iNrKE0JnuL+6MDL/89KTXzevQAiC0bvaZS6vzN02354 =NRym -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, February 18, 2014 12:49:09 AM Carlos E. R. wrote:
On 2014-02-17 22:52, Patrick Shanahan wrote:
Well, for Tw Gregg KH does emphasize using *only* "zypper dup". And has recently posted specifically advising against "zypper patch"
Yes, but Tw is a factory derivative. You also are supposed to use "zypper dup" with factory, not "zypper patch".
The stables releases are different: there you are supposed to use "zypper patch", or "zypper up".
-- Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith))
+1 Very clear differenciation. -- Ricardo Chung openSUSE Projects -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R.
-
jdd
-
Ken Schneider - openSUSE
-
Michael Schroeder
-
Patrick Shanahan
-
Ricardo Chung
-
Werner Flamme