Upon resuming merge the dependency tree still contains a package which was supposed to be rebuild only after the update of another.
I started an update last night with the following excerpt:
[ebuild r U ] dev-libs/libgit2-1.3.0 [1.1.1]
[ebuild rR ~] dev-util/cargo-ebuild-0.4.0
The following packages are causing rebuilds:
(dev-libs/libgit2-1.3.0:0/1.3::local, ebuild scheduled for merge) causes rebuilds for:
(dev-util/cargo-ebuild-0.4.0:0/0::local, ebuild scheduled for merge)
What I noticed the next morning was that libgit2 had failed yet carbo-ebuild was still rebuilt.
I realize this is a very small, barely noticeable inconvenience but this could happen with packages that bring in many large programs, e.g. poppler or re2 come to mind.
*** This bug has been marked as a duplicate of bug 629952 ***