On 28 December 2016 at 10:48, Aleksa Sarai firstname.lastname@example.org wrote:
On 12/28/2016 09:16 PM, nicholas wrote:
from experience and looking around forums, how to update tumbleweed correctly is not obvious, and not clearly presented. The lack of guidence is causing confusion and problems.
The rest of this post is based on my ASSUMPTION that 'sudo zypper dup --no- allow-vendor-change' is best practice.
AFAIK, "zypper up" is all you need to do -- Tumbleweed is a rolling release so there's no distribution version to update to. In fact, "zypper dup" will probably not do what you want.
`zypper up` is all you need to do, most of the time. It's certainly safe, and won't do anything stupid.
but zypper up will rarely/never tidy up after itself, leaving to orphaned packages lurking around over time. These are often benign.
zypper up is also very conservative in some aspects of its dependency resolution, so if Tumbleweed or any additional repo package maintainers have done major changes to the dependency tree of a package it's possible zypper up might get tripped up while `zypper dup` will be fine.
Of course, zypper dup comes with the additional risk of freely changing repositories, making it practically like russian roulette on a TW machine with OBS devel or home repos present. (Remember, Devel and Home repos do not use the openSUSE Vendor).
But this risk is mitigated by `zypper dup --no-allow-vendor-change` which does the tidy up, more relaxed dependency resolution, and yet still ensures you're getting packages from the repositories you as the admin have intended, by only upgrading from the same 'vendor' as the current packages.
zypper dup does not. It's purpose is to allow you to upgrade between Leap versions (or to switch between distributions entirely like Leap -> Tumbleweed).
Yes, but, see above ;) dup still has it's place for Tumbleweed.
- Is the dup default of allow-vendor-change really required for leap
It shouldn't be, because both vendors are "openSUSE" (IIRC).
Yes, but any additional repos are not "openSUSE", and as the instructions advise removing additional repos and starting from a fresh official-only base, zypper dup gets you there :)
Doing a dup with --no-allow-vendor-change from Leap 42.1 to Leap 42.2 on a machine that had additional repos will likely lead to a very broken Leap 42.2 machine.