Mailinglist Archive: opensuse-bugs (9648 mails)

< Previous Next >
[Bug 337370] yast2-theme-openSUSE-Crystal removes yast2-*
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 6 Nov 2007 08:15:57 -0700 (MST)
  • Message-id: <20071106151557.B53F324526A@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=337370#c11


Ján Kupec <jkupec@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC|
|visnov@xxxxxxxxxx, mvidner@xxxxxxxxxx
Status|NEW |ASSIGNED




--- Comment #11 from Ján Kupec <jkupec@xxxxxxxxxx> 2007-11-06 08:15:57 MST ---
indeed, when false, it correctly prompts for solution:

Solution 1: do not install yast2-theme-openSUSE-Crystal
do not install yast2-theme-openSUSE-Crystal-2.15.14-16.noarch[factory]
Solution 2: delete yast2-theme-openSUSE
delete yast2-theme-openSUSE-2.15.14-4.noarch
Solution 3: Ignore this conflict of yast2-theme-openSUSE-Crystal
Choose the number, (s)kip, (r)etry or (c)ancel>

So i guess it's time to add an option to zypper which would enable us to turn
the forceResolve on/off _and_ to rethink which mode do we want to be the
default.

Since forceResolve == true is the default for rug/zmd, i guess that's why
Martin (or Duncan?) decided to use this mode when writing zypper install.

I suggest to leave that as it is in rug compatibility mode, and use
forceResolve == false in zypper by default, with an option to turn it on (e.g.,
somewhat surprisingly, --force-resolution :O).


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >