dantrell

I don't know what's causing this yet. Fixing it entirely is a bit involving and we would have to rule out hardware/network errors or any other underlying causes of corruption and after replacing all the culripts (trees included), everyone might sitll have to acquire a clean tree. In the meantime, I have replaced the manual steps in Plan B with a script that automates the process. To the best of my knowledge it works but requests may occasionaly be rate limited by GitHub (in which case you'll have to wait a hour or so before trying again).

The idea is to follow Plan A to F (D to F not recommended unless you know what you are doing to prevent undesired data loss) in order until something worked. Plan C will work 100% but restoring *all* of the missing blobs as in Plan B is the cleanest solution. If you are willing to hop on IRC and spend some time, I can walk you through it. Even better if you can get me a copy of your corrupt git repository. I'm going to see about writing a simple tool to automate the repair process shown in Plan B. This would be the best solution.

Thanks, that explains things a little. The focus has been on GNOME 3.12 and other DEs. It would be a good idea to check to see how our upower changes are impacting things (at the very least, I now know it's causing issues with cinnamon) so I will look into this as time permits.

Can you explain more about this conflict? What package wanted upower-pm-utils?

This particular issue has been resolved. The recommended method for addressing this is to try Plan A (likely too fail) and then Plan B (not likely to fail) mentioned on FL-1429.

Just for the record, this will be looked into over at FL-1429 and hopefully a proper fix will be found.

You forgot to tell them to remove/rename the existing portage directory first. :) But this issue has been propping up quite a lot lately and it should have a simpler fix. I will be looking into this and if I find a proper answer it will be documented on FL-1429, otherwise a clean reinstall of the portage tree is the way to go.

This isn't a bug for Gentoo as they don't even have the versions of the slib and guile packages that I introduced into mainline earlier today. In fact, Gentoo has a lot of these packages masked, including >=aisleriot-3.2. Anyway, this issue has been resolved. It will take a couple hours before the change hits mainline though.

I caused this, sorry. :) I'm working on this now over at FL-1421.

I could not reproduce your build failure with or without the introspection USE flag enabled. Please mask sys-power/upower-20140423 and try sys-power/upower-0.99.0-r1. If that works, then I'm going to need more information. What version of sys-deve/autoconf and sys-devel/automake do you have installed?

Actually, this was unintended. I will be taking care of it over at FL-1417.

My guess is that you just updated perl and econf for at-spi2-core failed on checking for XML::Parser. If that's the case, please run "perl-cleaner --all" then restart your world update. P.S. In the future, please share the full emerge output, not just the part you think is relevant.

You have a few things going on here. You updated perl but failed to run "perl-cleaner --all" (or --reallyall). Until you do, upower isn't the only package that will fail to compile. Please take care of that first and then see how things go. On the note of upower, because of the work I have been doing in Funtoo, upower-pm-utils is no longer needed. You can simply build upower with the deprecated USE flag and achieve the same effect. This is done for you if you are using GNOME and have enabled the mix-in. Secondly, net-analyzer/snortsam-2.70 does indeed fail to build, I will be taking care of this issue over at FL-1408.

I was thinking it was this but I wasn't sure as it should have already been unmasked. Thanks for letting us know and good to hear your world update is on the way. :)

Just to clarify, you are on the stable profile and are not using GNOME 3.12? Edit: Actually, it seems you are. Did you swiitch from the current profile to stable?

I answered this in #funtoo, but, just for the record, I would like to state that nothing critical is missing. GNOME 3.12 in Funtoo is the full experience with minimal divergence.

I'm resolving this issue as we speak. You can track my progress at FL-1395.

Since you mentioned this, I did some research and found that it would be trivial to reintegrate support for this (and luckily, much of the grunt work was already done). Your beloved background transparency in GNOME Terminal is here to stay. :) You can track my progress on this issue through FL-1373.