[Bug 1017486] New: no-allow-vendor-change uselessly interactive
http://bugzilla.opensuse.org/show_bug.cgi?id=1017486 Bug ID: 1017486 Summary: no-allow-vendor-change uselessly interactive Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@forge.provo.novell.com Reporter: bwiedemann@suse.com QA Contact: qa-bugs@suse.de Found By: Development Blocker: --- Created attachment 708047 --> http://bugzilla.opensuse.org/attachment.cgi?id=708047&action=edit solver testcase I usually update my Tumbleweed system with zypper up --no-recommends which leaves some packages un-updated, so what is usually recommended as a replacement is zypper dup --no-allow-vendor-change But this only lets me upgrade after answering 37 interactive prompts with only 1 option each (besides useless skip, retry or cancel) There could be several approaches to solve this. 1) there could be an option to apply an interactive response to all similar cases 2) there could be a CLI option for selecting this 3) the default could allow those required vendor changes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017486
http://bugzilla.opensuse.org/show_bug.cgi?id=1017486#c1
Richard Brown
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.
I do not think this is a bug to be fixed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017486
http://bugzilla.opensuse.org/show_bug.cgi?id=1017486#c3
--- Comment #3 from Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=1017486
http://bugzilla.opensuse.org/show_bug.cgi?id=1017486#c4
Michael Andres
participants (1)
-
bugzilla_noreply@novell.com