On 28 December 2016 at 15:03, Anton Aylward <opensuse@antonaylward.com> wrote:
On 12/28/2016 05:48 AM, Richard Brown wrote:
- 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.
I must admit I'm confused here. Regular readers will recall that I make use of the kernel_Stable repository. I'm running kernel 4.9.0.
Why? are you involved in Tumbleweed kernel testing? If not ,then the correct way to consume a new kernel is to wait until it's actually tested and in Tumbleweed properly.
I'm sorry, but I don't consider making use of up-to-date builds 'cruft'.
The 'cruft' comes when devel projects, which have no qualty controls and no standards, restructure and remove packages, leading to zypper up leaving them on your system, or leading to zypper dup moving more packages to those OBS repos than a sensible user would be comfortable with
While 13.2 is coming to the end of its life soon, everything I've seen about the update into the 42 series seems fraught with minor hassles and issues that I don't have time to deal with. Threads like this seem to hint that an upgrade to tumbleweed will also be fraught with 'things that might go wrong'.
The risks are less today than they ever were with the 13.x series, but the risks are still there, and people need to be wary to mitigate them. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org