Richard Fish writes:
Unfortunately the Gentoo dev's have taken the rather unusual step of _breaking the tree_ due to a security problem.
Thanks for the info. I would really wish that there was some mechanism in place to make sure that the tree was never broken. The current situation is very annoying for users that update often, and also makes Portage mostly unusable for automatic server upgrades :-(.
1. Unmerge both mono-tools and gecko-sharp.
That did the trick. I'll have to remerge it later when/if the tree gets fixed... Thanks! (I see now that it was just me that didn't understand how to use --tree, which makes much of this conversation off-topic... Sorry about that!)
[1] http://bugs.gentoo.org/show_bug.cgi?id=137665
I'm thinking that a Subversion pre-commit hook to secure integrity of the Portage tree would be cool. The changes listed in the bug above would have to be committed atomically, or it wouldn't get through the integrity check. Perhaps there could be a staging area in the form of a branch where the hypothetical integrity checker wouldn't run. Ho hum, wishful thinking. -- [email protected] mailing list
