On 29 December 2016 at 08:32, Bernhard M. Wiedemann
On 2016-12-28 17:54, Richard Brown wrote:
zypper dup --no-allow-vendor-change - 'get me the latest packages from the same vendor/repos I previously installed those packages from'
The one problem I have with that approach is that it gives me a long chain of interactive prompts with only one option - could be a bug?
Problem: problem with installed package fdupes-1.51-3.19.x86_64 Solution 1: install fdupes-1.61-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE
Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1
Problem: problem with installed package gstreamer-1.8.2-75.6.x86_64 Solution 1: install gstreamer-1.10.2-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE
Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1
Problem: problem with installed package gstreamer-0_10-0.10.36-21.7.x86_64 Solution 1: install gstreamer-0_10-0.10.36-20.3.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE
Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1
Problem: problem with installed package gstreamer-0_10-lang-0.10.36-21.7.noarch Solution 1: install gstreamer-0_10-lang-0.10.36-20.3.noarch (with vendor change) http://packman.links2linux.de --> openSUSE
and so on... Also this prevents it to work with zypper --non-interactive which one would want for cron-jobs or other mass-updating methods.
This is why I use most of the time zypper -n up --no-recommends (where the last arg prevents plenty unwanted packages to be installed)
I understand why you'd want non-interactivity but you need to consider why you get the prompts above In all the cited examples above, the root cause is Packman fdupes, gstreamer, etc have all been dropped from Packman your chosen "zypper -n up --no-recommends" is therefore clinging to orphaned packages like a rotting corpse, and sooner or later your Tumbleweed system will run into issues as other packages depend on newer fdupes, gstreamer, etc which are resolved by using the packages in the official distro This is a perfect case study of precisely why 'zypper dup --no-allow-vendor-change' is my recommended way of patching a Tumbleweed machine - for all the time Packman had fdupes, gstreamer, etc you would have continued receiving updates from them, but now they've restructured what they're doing you currently have your system in an unhealthy state because it no longer reflects where your repositories expect you to be. Of course, when a reluctant vendor change is proposed by zypper, zypper needs to inform you that it is doing something that potentially could have significant consequences on your system. I think zyppers behaviour here is totally sane. It is most certainly not a bug. The problem is that external repositories a rarely maintained in a way that facilitates good smooth upgrades in all circumstances. And in this case, Packman is actually improving, but in order to make those improvements, you have painpoints like this during the transitiions. I think the only viable option for a 100% automated Tumbleweed installation with consistent dependencies is one without any external OBS or Packman repos. This is also true for Leap, which is not immune from the problem cited above. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org