Several ebuilds have explicit sys-apps/sed dependency. It is wrong since there are at least 2 different sed providers. One is sys-apps/sed Another is sys-apps/busybox with make-symlinks USE Small embedded systems often use busybox wich provides sed. Then they catch portage's collision-protect error when pulling original sed wuth deps. I suggest creating virtual/sed pointing to sys-apps/sed by default and fixing all ebuild depending on sed. Reproducible: Always
for busybox replacements, we suggest you package.provide everything that you've manually set up busybox to replace
