Red Hat Bugzilla – Bug 836492
samba4-client and samba4-common conflict with samba-client and samba-common
Last modified: 2015-01-07 23:38:10 EST
Description of problem:
In F18 Rawhide samba4-client and samba4-common conflict
with samba-client and samba-common. This prevents
installation of Rawhide. :-(
Version-Release number of selected component (if applicable):
Steps to Reproduce:
- yum update rawhide install
- attempt rawhide install
update/install fails with samba4 and samba conflict
no conflict or obsoletes to resolve conflict
Workaround for updating seems to be to yum remove samba-common.
This was leading to a false (?) fileconflicts failure on the F17 DVD during development - see bug 820472. Am curious how this will be resolved.
Do you have any samba4 packages installed?
(In reply to comment #2)
> Do you have any samba4 packages installed?
I'm seeing this problem and I don't have any samba4 packages installed:
# rpm -qa samba\*
However, sssd wants to pull in samba4:
# repoquery --requires sssd | grep samba
# repoquery --whatprovides 'libsamba-util.so.0(SAMBA_UTIL_0.0.1)'
And as samba4-libs wants samba4-common, which conflicts with samba-common, I can't update sssd, which is a core component of Fedora that just about everyone will have.
I have several samba packages installed, but no samba4 packages.
After today's (20120704) Rawhide update, I now have
and no samba conflicts during update.
Yeah as far as I can tell this is now okay - at least
it is no longer preventing rawhide from installing.
I guess it should be fixed now with latest samba4:
* Tue Jul 03 2012 Andreas Schneider <firstname.lastname@example.org> - 2:4.0.0-125.beta2
- Change version and release number scheme.
- Remove dependency between samba4-libs and samba4-common.
- resolves: #836492
No conflicts when updating for me now, now that I've recovered from dracut-020-51 :-)
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here: