[Bug 1223986] New: conflicting package gets selected during zypper dup
https://bugzilla.suse.com/show_bug.cgi?id=1223986 Bug ID: 1223986 Summary: conflicting package gets selected during zypper dup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@suse.de Reporter: ohering@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874710 --> https://bugzilla.suse.com/attachment.cgi?id=874710&action=edit vlc-beta.zypper.solverTestCase.tar.xz There is a pkg named "vlc-beta", which is supposed to be installed only if explicitly requested, like 'zypper in vlc-beta'. There are Conflict tags in 'vlc-beta' for this purpose. The Obsolete tags in 'vlc-beta' are supposed to wipe all subpackages from the ordinary 'vlc' pkg, in case 'vlc-beta' is installed either manually or via zypper. Doing "zypper dup -l --no-recommends" will replace rpms from pkg 'vlc' with 'vlc-beta', which is unexpected. I just noticed this also happens in Leap now. What Conflicts/Obsoletes/Provides tags are actually required in 'vlc-beta.spec' to make sure it does not get selected? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1223986 https://bugzilla.suse.com/show_bug.cgi?id=1223986#c2 --- Comment #2 from Olaf Hering <ohering@suse.com> --- Provides is for what the tag name suggests. Obsoletes is just for a smooth transaction because rpm silently deletes the listed packages. Conflicts is to prevent accident installation. But Obsoletes will do what it does in case a package is installed anyway. Does our package management confuse the meaning of those tags? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1223986 https://bugzilla.suse.com/show_bug.cgi?id=1223986#c3 Michael Schröder <mls@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls@suse.com --- Comment #3 from Michael Schröder <mls@suse.com> --- No. "Obsoletes: foo" means that this package is the new "foo". It's not "just for a smooth transaction". -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1223986 https://bugzilla.suse.com/show_bug.cgi?id=1223986#c4 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #4 from Michael Andres <ma@suse.com> --- Closing it. Package management works as expected. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1223986 https://bugzilla.suse.com/show_bug.cgi?id=1223986#c5 --- Comment #5 from Michael Schröder <mls@suse.com> --- Regarding your question about the tags to use: if it is an alternative, just use a conflict without obsoletes. The software stack will then 1) not automatically switch to the alternative, and 2) will ask the user if it has to switch because of some dependency. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com