with the introduction of samba-4.0 and above the smbclient use flag used to pull in the samba client was changed to a client use flag in the new versions. Because of this, gnome-control-center and gvfs both have logic in their ebuilds which is meant to handle both new and old samba versions with their smbclient or client use flags as appropriate. The ebuild line in gvfs that handles this logic is: samba? ( || ( >=net-fs/samba-3.4.6[smbclient] >=net-fs/samba-4[client] ) ) with samba-4.17 is already installed with client use flag enabled cave resolve gvfs causes paludis to attempt to downgrade samba to 3.6.25 If the order is reversed in the ebuild line to: samba? ( || ( >=net-fs/samba-4[client] >=net-fs/samba-3.4.6[smbclient] ) ) then paludis works as expected. The same issue can be shown in gnome-control-center. Obviously paludis is handling this logic differently than portage.
*** Bug 549576 has been marked as a duplicate of this bug. ***
Paludis has been removed from the tee.
