Bugzilla – Bug 683274
Version conflict when trying to install samba with yast
Last modified: 2011-03-30 10:01:15 UTC
Created attachment 421809 [details] Package conflict in yast User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0 I wanted to configure samba after configuring my ldap server. But in yast, when I try to install the necessary packages (samba and samba client) it seems to be a conflict somewhere, see picture. Reproducible: Always Steps to Reproduce: 1. in yast try to install samba 2. 3. Actual Results: package conflict between samba and samba client
using zypper: euler:/ # zypper install samba Loading repository data... Reading installed packages... Resolving package dependencies... Problem: samba-3.5.7-1.17.1.x86_64 requires samba-client >= 3.5.7, but this requirement cannot be provided uninstallable providers: samba-client-3.5.7-1.17.1.x86_64[openSUSE-11.4-11.4-0] samba-client-3.5.7-1.17.1.i586[repo-oss] samba-client-3.5.7-1.17.1.x86_64[repo-oss] Solution 1: deinstallation of patterns-openSUSE-minimal_base-11.4-6.9.1.x86_64 Solution 2: do not install samba-3.5.7-1.17.1.x86_64 Solution 3: break samba by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c):
http://forums.opensuse.org/english/get-technical-help-here/applications/456931-pacemaker-python-dependency-problem-minimal-opensuse-11-4-a.html and http://forums.opensuse.org/english/get-technical-help-here/applications/456054-python-development-pattern-opensuse-11-4-a.html I would follow the suggested solution 1. Passing to Coolo as he might know a better approach or might make other use of this report.
Ludwig maintains minimal pattern - once samba-client is no longer recommended, it doesn't need to be blocked by the minimal pattern. But solution 1 is just the right, you might get some more recommended packages then though.
So do you want to to uninstall patterns-openSUSE-minimal_base?
put rants about the minimal pattern in bug 669498 *** This bug has been marked as a duplicate of bug 669498 ***