On 28 December 2016 at 10:16, nicholas
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.
Forums are filled with confusion over the update process e.g. https://forums.opensuse.org/showthread.php/517451-Differnce-between-zypper-u...
I have seen other suggestions of (including by forum global moderator) 'zypper up' mostly, 'zypper dup' occasionally, this is without clarfying to disable extra repos. https://forums.opensuse.org/showthread.php/504212-I-get-no-updates-to-Tumble...
there are also MANY implicit postings of problems suggesting the OP is not even aware of the issues.
The current update process would appear: non-evident (not communicated, ambiguous (when to up/dup?), non deterministic (its ok to get out of sync sometimes?), error prone (new user forgets to disable extra repos), time consuming mess.
in fact, do zypper up/dup really make sense conceptually or functionally to a rolling distribution?
zypper up/upgrade makes sense as a conservative upgrade choice It's very similar in concept and function to the 'apt upgrade' function which has since been renamed to 'apt safe-upgrade' FYI zypper dup/dist-upgrade is similar in concept and function to 'apt dist-upgrade' which has since been renamed to 'apt full-upgrade' I think both up and dup have their place in zypper and ergo in Tumbleweed also, but I do feel the best practice for a day-to-day upgrade is `zypper dup --no-allow-vendor-change`
The question, IF the 'no allow vendor change' is best practice, should we make a more accessible command for updating out of the box (i.e. zypper tup/or other) and should best practices not be better communicated to new users?
I like this idea.
- I have 'alias tup=sudo zypper dup --no-allow-vendor-change' in .bashrc
I do something similar
- Is the dup default of allow-vendor-change really required for leap upgrade?
Yes, in order to ensure you don't have cruft from additional repositories from earlier distribution releases hanging around when there are better upgrade targets available in the main repositories. no-allow-vendor-change is great at ensuring you keep getting your packages from the same sources you currently installed them from, but in the case of a distribution upgrade, that's the last thing you want.
[my own learning curve was quite painful, you should not underestimate the conceptual overhead to new user of understanding all the zypper ins and outs regarding 'packages not being updated', 'changing vendor' etc -> your basically expecting the noob to learn *everything* in order to get a working and reliable system within the first few months]
As you might have gathered from some of my points above, there is a lot in common in concepts between zypper and aptitude, so any knowledge you may have or be able to find from there is likely to transfer rather smoothly, at least at a high level until you get down and dirty with zypper or RPM specifics. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org