On 28 December 2016 at 17:32, Anton Aylward
On 12/28/2016 09:00 AM, nicholas wrote:
yes "zypper dup ---no-allow-vendor-change" should be the *one and only one* *default* and *communicated* method of updating tumbleweed (unless the user has an explicit need otherwise) then we do not need all the [epic poems regarding ifs, buts, mights, shoulds]. Since the command is quite long lets create a shortcut of some sort and include in TW. *Then communicate clearly*.
well from my POV that's not merely 'as clear as mud' but sows confusion and perplexations.
Does that me that if you, as I do, have other repositories to ensure latest releases of other things (kernel, tools for specific projects, fixes to specific problems) that one should run the "-dup" ONLY and SPECIFICALLY on the tubleweed repository, replying of the fact that the "--no-allow-vendor-change" means my darktable (for instance) from another repository will not be updated by this 'dup"?
Or if that's not the case, then what? Please don't talk about 'locks'. The whole point of those other repositories is that I want either a different style of implementation or a different way of updating.
zypper dup - 'get me the latest packages from wherever, I don't care' Using the darktable example, lets say you have Tumbleweed with a darktable repo chosen and darktable installed from that repo, but you also have other repos enabled (eg packman) When you do a zypper dup you might get darktable from the darktable repo you might get darktable from packman you might get darktable from the official repos it all depends on which package has the highest version number, that's all - that's likely to change stuff in ways you do not expect, which is why I do not consider a plain 'dup' a sensible option for another running additional repos zypper dup --no-allow-vendor-change - 'get me the latest packages from the same vendor/repos I previously installed those packages from' Using the same darktable example, this now means you will always get darktable from the darktable repo, because you originally installed it from the darktable repo Unlike it's no longer in the darktable repo, in which case it'll get it from whatever repo it is available, with a notification of the 'vendor change' All of this is accomplished without locks or micromanagement, zypper is just being smart based on what you've previously installed and from where you've previously installed it. That is why I recommend it as a safer option to zypper dup for day to day patching of complex Tumbleweed+OBS Repo installations. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org