netkit-base has been removed from the default profile in favor of iputils, in fact an 'emerge -u --deep world' correctly install the new iputils but without deleting netkit-base. So after doing the update an 'epm -q -f /bin/ping' shows that the binary belongs to netkit-base AND iputils. To fix that I've got to do 'emerge unmerge netkit-base ; emerge iputils'. Clearly when some replacement are made in profiles old packages must be handled some way. Bye Reproducible: Always Steps to Reproduce: 1. emerge -u --deep world 2. epm -q -f /bin/ping 3. Actual Results: box root # emerge -pv -u --deep world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild N ] net-misc/iputils-020927 -doc box root # emerge -u --deep world box root # epm -q -f /bin/ping netkit-base-0.17-r6 iputils-020927
I'll be posting an updated netkit-base that no longer provides conflicting packages soon.
Just committed -r8 to ~x86 - please test. I'd like to mark it stable as soon as possible, but need testers first.
I've noticed that unmerging iputils cause some files to remain on the host, for example /etc/init.d/inetd and /usr/man/man3/daemon.3.gz. In order to avoid this kind of problems (also the conflict described in this bug) wouldn't be advisable to create a script that check consistency of installed binaries against portage db (like double entries) and file not owned by any package?
By the way I've just tested -r8, looks fine to me.
inetd and daemon things are only provided by netkit-base, not iputils. iputils doesn't provide any inetd functionality, but most people should use xinetd instead anyway. (netkit-base is still in the tree for people who want old-style inetd). Thanks, closing bug.
