After syncing twice using emerge-webrsync && emerge -avuDN world, talloc-2.0.7 wants to merge, but the stable Samba package requires <talloc-2.0.5. I suppose [ebuild U ] sys-libs/talloc-2.0.7 [2.0.1-r2] USE="python%* -compat (-doc%) (-static-libs%*) (-swig%)" 363 kB [blocks B ] <sys-libs/talloc-2.0.5 ("<sys-libs/talloc-2.0.5" is blocking sys-libs/talloc-2.0.7) Total: 4 packages (3 upgrades, 1 reinstall), Size of downloads: 3,007 kB Conflict: 1 block (1 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (sys-libs/talloc-2.0.7::gentoo, ebuild scheduled for merge) pulled in by sys-libs/talloc required by @selected sys-libs/talloc required by (net-fs/samba-3.5.11::gentoo, installed) Reproducible: Always Steps to Reproduce: 1. emerge-webrsync 2. emerge -avuDN world (happens only if you have samba installed!) Actual Results: Blocking Expected Results: No blocking
this is on stable amd64
I had the exact same block a shown by Milton Yates. The only difference for me was the update sequence: i.e. emerge --sync && emerge -uDNa @world My workaround was to unmerge tallaoc (emerge -C talloc) followed by emerge --oneshot talloc This sequence worked and talloc-2.0.7 was merged correctly. However, after that I was looking at the various ebuilds for talloc and see something that (to me) looks suspicious. In /usr/portage/sys-libs/talloc/talloc-2.0.7.ebuild I see the line: RDEPEND="!!<sys-libs/talloc-2.0.5" It seems to me that line should be: RDEPEND="!!<sys-libs/talloc-2.0.7" Just a wild guess on my part though as I have no idea what that particular RDEPEND is meant to do. I.e. I don't know why that RDEPEND is even there and don't know what effect the !! has.
*** This bug has been marked as a duplicate of bug 387509 ***
*** This bug has been marked as a duplicate of bug 366523 ***
