Samba depends on: >=sys-libs/ntdb-1.0 and ntdb depends on: !!<net-fs/samba-4.1.7 which means that samba-4.1.17 cannot be installed due to hard block Reproducible: Always
If you unmerge your currently-installed samba-3.x then you can continue and get samba-4.1.17... though I'm not yet certain that this needs to be a hard blocker as it is now. It certainly makes the upgrade path a bit ugly. Can the maintainer confirm that samba-3 REALLY must not exist on the system when ntdb is built?
I don't think I have samba-3 and still get the block: [ebuild N ] sys-libs/ntdb-1.0-r1::gentoo USE="python" PYTHON_TARGETS="python2_7" 776 KiB [ebuild U ] net-fs/samba-4.1.17::gentoo [4.0.25::gentoo] USE="client cups fam -acl -addns -ads -aio -avahi -cluster -dmapi -gnutls -iprint -ldap -quota (-selinux) -syslog -systemd% {-test} -winbind (-swat%)" PYTHON_TARGETS="python2_7" 19,079 KiB [blocks B ] <net-fs/samba-4.1.7 ("<net-fs/samba-4.1.7" is hard blocking sys-libs/ntdb-1.0-r1)
Replace "samba-3" with "any samba older than 4.1.7" in my previous comments
Samba gets pulled in as a dependancy, I have emerge -C'ed both samba and ntdb, yet samba fails to install due to the blocker? Kind of confusing as to how to fix it.
manually installing with -1 ntdb followed by samba seems to work.
Same here
I can confirm that the suggestion by Olliver Schinagl worked for me and hope this workaround can help others too until we have a better solution. emerge -C net-fs/samba # removes net-fs/samba-3.6.25 emerge net-fs/samba # installs net-fs/samba-4.2.9
Same issue for me with Samba 3.6.25 installed. emerge -1a ntdb simply results in a failed emerge (ntdb-1.0-r1 will not install when Samba is <net-fs/samba-4.1.7). The following worked for me: emerge -C net-fs/samba # removes net-fs/samba-3.6.25 emerge net-fs/samba # installs net-fs/samba-4.2.9
Samba team: is there a real reason for this hard blocker? Is there a reason samba-3 cannot be installed at the time ntdb is built/installed? I "softened" the blocker on a test box from !! to !, so it can autoresolve, and I saw no noticeable problems. Either there is a specific reason for the hard block and we can close this bug INVALID, or there is no reason and the blocker should be softened so that manual unmerging isn't required. Thanks!
with permission from PolyC and no arguments from the rest of the team I have softened the blocker to allow portage to auto-resolve. Seems pretty odd to block on old versions of samba but not actually dep on samba. I installed ntdb no problem with samba 3.6.25 installed. This blocker doesn't appear necessary at all honestly, might want to check it out and tighten it down or drop it.
Package removed.
