Have you tried upgrading to the latest version of Portage 2.2? The
newest version in the tree is currently portage-2.2_rc95, while you're
still using portage-2.2_rc67. Perhaps there's a bug causing this that
was fixed in subsequent release?

Reply via email to