Mailinglist Archive: opensuse-bugs (4724 mails)

< Previous Next >
[Bug 592640] patterns and/or their contents get installed even if the pattern is tabooed/locked
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 1 Apr 2010 13:36:03 +0000
  • Message-id: <20100401133603.6B9F9CC7CD@xxxxxxxxxxxxxxxxxxxxxx>

Michael Andres <ma@xxxxxxxxxx> changed:

What |Removed |Added
CC| |mc@xxxxxxxxxx
AssignedTo|zypp-maintainers@xxxxxxxxxx |coolo@xxxxxxxxxx
| |

--- Comment #8 from Michael Andres <ma@xxxxxxxxxx> 2010-04-01 13:36:02 UTC ---
The curse of code11 pattern handling. I pass it to Coolo, as he broke it by
introducing the patterns-openSUSE-* packages. By duplicating all dependencies
on the package layer, one is still able to trigger installation of AA by
selecting the pattern, but locking the pattern has no effect, as it does not
affect the package layer.

UI: pattern:base --recommends--> pattern:AppArmor
| |
requires requires
v v
Packages: patterns-openSUSE-base --recommends--> patterns-openSUSE-apparmor

If we want a solution for 11.3 (and also future SLE) we should think about it
ASAP. We could think about dropping patterns (also product) as primary solvable
objects in the pool. Instead represent them as specialized packages. But that
will also have some impact on zypper, pkgkit and the UIs.

A probably cheaper solution is the same approach as we currently have for
products. We let the pattern and the representing package share the same status
(selecting the pattern in fact selects the packages). All dependencies must be
expressed on the package level. As the objects would stay in the pool, there
should be almost no impact on zypper, pkgkit and the UIs (but mls@ will sigh).

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >