[Bug 1189024] New: Sway: potential name conflict pattern vs package
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024 Bug ID: 1189024 Summary: Sway: potential name conflict pattern vs package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar@opensuse.org Reporter: tammo.oepkes@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 851501 --> http://bugzilla.opensuse.org/attachment.cgi?id=851501&action=edit Screenshot from sway install on minimal system There are a package and a pattern which are both called `sway`. If one attempts to install the sway package, the pattern unintentionally gets installed. Reproduce: - install Tumbleweed, choose server install (to get minimal system) - modify `/etc/zypp/zypp.conf`: `solver.onlyRequires = true` - modify `/etc/zypp/zypper.conf`: `installRecommends = no` - run dist-upgrade - run `zypper install sway` This will attempt to install the sway _pattern_ (with 196 packages, consuming 343 MiB). For comparison, an i3 installation attempt on the same (minimal) system attempts to install 23 packages, weighing only 6.9 MiB. I tried to install sway package (instead of pattern) explicitly with `zypper install --type package sway`, but this yields the same result as omitting the switch. My assumption is that the identical names for pattern and package cause unintended behavior. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
Tammo Oepkes
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c1
Dominique Leuenberger
Reproduce: - install Tumbleweed, choose server install (to get minimal system) - modify `/etc/zypp/zypp.conf`: `solver.onlyRequires = true` - modify `/etc/zypp/zypper.conf`: `installRecommends = no` - run dist-upgrade - run `zypper install sway`
This will attempt to install the sway _pattern_ (with 196 packages, consuming 343 MiB).
For comparison, an i3 installation attempt on the same (minimal) system attempts to install 23 packages, weighing only 6.9 MiB.
I tried to install sway package (instead of pattern) explicitly with `zypper install --type package sway`, but this yields the same result as omitting the switch.
That rather sounds like a zypper/libzypp bug not being able to handle the same names. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c2
--- Comment #2 from Tammo Oepkes
That rather sounds like a zypper/libzypp bug not being able to handle the same names.
Later yesterday evening I compared the sway package/pattern behavior to similar patterns/packages (like kde, gnome, mint, cinnamon, lxde, lxqt). Out of these, the only package/pattern combination with identical names for package/pattern was cinnamon. But installing cinnamon package shows a different package selection than installing the cinnamon pattern. My original assumed cause (name conflict) seems to be wrong then. So it would be something specific to the sway package that causes the sway _pattern_ to be pulled as a dependency. --- toe@toe-tp-20uj ~ % sudo zypper install --type pattern cinnamon (...) The following 141 NEW packages are going to be installed: (...) The following 4 NEW patterns are going to be installed: basesystem cinnamon cinnamon_basis x11 141 new packages to install. Overall download size: 59,0 MiB. Already cached: 0 B. After the operation, additional 171,8 MiB will be used. Continue? [y/n/v/...? shows all options] (y): --- toe@toe-tp-20uj ~ % sudo zypper install cinnamon (...) The following 99 NEW packages are going to be installed: (...) 99 new packages to install. Overall download size: 29,1 MiB. Already cached: 0 B. After the operation, additional 70,5 MiB will be used. Continue? [y/n/v/...? shows all options] (y): -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c3
--- Comment #3 from Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c4
--- Comment #4 from Tammo Oepkes
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
Tammo Oepkes
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c5
--- Comment #5 from Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c6
--- Comment #6 from Tammo Oepkes
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c7
--- Comment #7 from Tammo Oepkes
Package sway-branding-openSUSE has patterns-sway-sway under requires, while package sway-branding-upstream doesn't.
This makes me wonder what strategy zypper uses to resolve alternative dependencies. The sway package itself has `sway-branding` as requirement (without specifying -openSUSE or -upstream). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c8
Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c9
Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c10
Tammo Oepkes
According to the testcase you have branding-openSUSE installed, so the solver chooses sway-branding-openSUSE which supplements (sway and branding-openSUSE).
I hadn't installed anything on the system that relates to graphical interfaces until I installed Sway. Then it picked the branding-openSUSE during Sway install. Maybe branding-openSUSE was a remnant of the first sway installation run (according to https://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c5) and the subsequent `--clean-deps` did not remove it. I'll do a new minimal install and provide another test case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c11
Simon Lees
Package sway-branding-openSUSE has patterns-sway-sway under requires, while package sway-branding-upstream doesn't.
Yeah this is probably slightly backwards, the sway-branding-openSUSE package should require all the things needed to get sway functioning on openSUSE without requiring a pattern, then either the sway package or the pattern should require a branding package in such a way either the openSUSE or Upstream one can be installed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c12
Denys Kondratenko
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c13
--- Comment #13 from Denys Kondratenko
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c14
--- Comment #14 from Simon Lees
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c15
--- Comment #15 from Denys Kondratenko
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024
http://bugzilla.opensuse.org/show_bug.cgi?id=1189024#c16
--- Comment #16 from Simon Lees
Hi Simon,
thanks for the hint.
When I was thinking about openSUSEway (sway DE for openSUSE), I thought: - openSUSEway package and/or pattern - to install branded openSUSE sway DE - patterns-sway-sway to install basic sway with upstream branding - sway should have only sway and branding package installed (with is default sway config)
So I was thinking: sway-branding-upstream should go with default sway installation.
For openSUSE branding - there is special package/pattern.
In the installation media - both patterns are available and could be chosen.
So I think I messed up somewhere in Supplements/branding so sway package somehow chooses openSUSE branding instead upstream one by default.
Thanks, Denys
I couldn't quite see where the sway-branding-openSUSE comes from, but in sway-branding-upstream you have "Supplements: (%{name} and branding-upstream)", if you wanted it to be the default for all systems you probably also want Supplements: (%{name} and branding-openSUSE)" then no supplements in the sway-branding-openSUSE package otherwise the solver would be back to having a choice. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com