cifs-utils has this dependency:

    libwbclient.so.0()(64bit)  

Does samba4 not provide this library anymore?

[root@stockage tmp]# ldd usr/bin/getcifsacl 
	linux-vdso.so.1 =>  (0x00007fff5fdff000)
	libwbclient.so.0 => not found
	librt.so.1 => /lib64/librt.so.1 (0x00007f18f3079000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f18f2ce6000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f18f2ac9000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f18f3492000)

samba4 doesn't provides libwbclient.so.0 but it seems not to be needed by mount.cifs. Maybe the cifs-utils package should be splitted to provides mount.cifs in a different package?

You need to decide if you want samba4 or samba. If you need libwbclient, then you have to remove samba4 package first cause they conflict with the Samba packages!

As Samba and Samba4 provide the same binaries the conflict is by intention. I hope that helps :)

Shouldn't the samba4 packages also provide libwbclient, just like the samba3 ones do?

Moving this to a samba4 bug. The problem seems to be the provides/requires dependencies in the samba4 packages. In RHEL6, cifs-utils requires this capability:

    libwbclient.so.0()(64bit)  

...samba3 provides this via the samba-winbind-clients package.samba4-libs-4.0.0-55.el6.rc4.x86_64 also seems to provide this capability, but the library is under /usr/lib64/samba and the package capabilities aren't quite right. It provides:

    libwbclient.so.0(SAMBA_4.0.0RC4)(64bit)  
    libwbclient.so.0(WBCLIENT_0.10)(64bit)  
    libwbclient.so.0(WBCLIENT_0.9)(64bit)  

I think it needs to also provide the above capability, and probably add a symlink to this library or something under %{_libdir}.

Jeff, we filter out libwbclient from samba4 packages to avoid problems. libwbclient implements a protocol and needs to be the exact same version as the samba winbind package or it will not be able to talk to each other.

samba and samba4-libs need to coexist for openchange:

Please see:

https://bugzilla.redhat.com/show_bug.cgi?id=861892

(In reply to Andreas Schneider from comment #7)
> Jeff, we filter out libwbclient from samba4 packages to avoid problems.
> libwbclient implements a protocol and needs to be the exact same version as
> the samba winbind package or it will not be able to talk to each other.
> 
> samba and samba4-libs need to coexist for openchange:
> 
> Please see:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=861892

sigh...and that in and of itself is a problem. Either samba4 is a drop-in replacement for samba3, or it isn't. This mess where you have users installing pieces of both is just crazy.

AFAICT, cifs-utils needs to be able to use either one depending on which version of winbind is running. I'm not sure what the solution is given the needs of openchange, but the current state is clearly broken for cifs-utils.

The question is why is samba4-common installed?

yum remove samba4-common
yum install cifs-utils

and everything should work just fine.

(In reply to Andreas Schneider from comment #10)
> The question is why is samba4-common installed?
> 
> yum remove samba4-common
> yum install cifs-utils
> 
> and everything should work just fine.

...unless you want to run samba4 on the machine and be able to mount cifs shares onto it.

This is not supported. Samba4 is a tech preview in combination with IPA (AD Trust support) and not meant as a replacement for Samba3 in RHEL 6.4.

Edouard, if you want cifs-utils, you need to install samba (version 3). cifs-utils with samba4 packages installed is not supported. We are sorry for that but it is not possible to change that at the moment. We will have this fixed in RHEL7.


Here is the package list in alphabetical order which marks conflicts in the 
other field or tells you the components which need it.

Samba                  | Samba4                 | Other
-----------------------+------------------------+----------------------------
                       |                        |
 libsmbclient          |                        | (KDE, Gnome)
 libsmbclient-devel    |                        |
 samba                 | samba4                 | >>> CONFLICT <<<
 samba-client          | samba4-client          | >>> CONFLICT <<<
 samba-common          | samba4-common          | >>> CONFLICT <<<
 samba-doc             |                        |
                       | samba4-dc              |
                       | samba4-dc-libs         |
                       | samba4-devel           | (Requires all other pkgs)
 samba-domainjoin-gui  |                        |
                       | samba4-libs            | (OpenChange, evolution-mapi)
                       | samba4-pidl            |
                       | samba4-python          | (IPA Trust)
 samba-swat            | samba4-swat            | >>> CONFLICT <<<
 samba-winbind         | samba4-winbind         | >>> CONFLICT <<<
 samba-winbind-clients | samba4-winbind-clients | >>> CONFLICT <<<
 samba-winbind-devel   |                        |
 samba-winbind-krb5-loc| samba4-winbind-krb5-loc| >>> CONFLICT <<< *
                       |                        |
 samba-debuginfo       | samba4-debuginfo       | >>> CONFLICT <<<

 * samba-winbind-krb5-loc = samba-winbind-krb5-locator
   samba4-winbind-krb5-loc = samba4-winbind-krb5-locator

My point was just that mount.cifs can work with samba4 or 3, it only depends on kernel cifs driver. Am I wrong? In fact I don't care about libwbclient, I never say I need it, no need for mounting samba shares, that why I spoke about having mount.cifs binary in a separate package. Sorry for my english.

Correct, mount.cifs will work without libwbclient, but cifs-utils contains a lot more than just mount.cifs.

I'm not inclined to split up the cifs-utils package just to work around broken dependencies in the samba4 packages, which are considered tech-preview anyway. That said, you're welcome to open a support case and request that if you feel you really need it.

ok no need, have made my own mount.cifs package. Thanks anyway.