> On 13 Oct 2016, at 18:01, Daniel Quinn <gen...@danielquinn.org> wrote:
> On 13/10/16 02:36, wabe wrote:
>> Since the update process is dead slow anyway and I really don't care
> about a few minutes less ore more, I always use --backtrack=999.
> Unfortunately yes. I took your advice just now and it's still
> complaining about circular dependencies. Maybe I'm missing something,
> but how can gtk+ *depend* on gtk-engines-adwaita?
If you look in the ebuilds:
• gtk+-2.24.31-r1 depends upon x11-themes/gtk-engines-adwaita,  and
• gtk-engines-adwaita-3.20.2 depends upon >=x11-libs/gtk+-2.24.15 
If you look at the packages page for x11-libs/gtk+ , you'll see there are
some earlier versions of it in the tree that fulfils gtk-engines-adwaita's
requirement, x11-libs/gtk+-2.24.28-r1 for example.
x11-libs/gtk+-2.24.28-r1 does not seem to require gtk-engines-adwaita. 
So you should be able to `emerge -1 =x11-libs/gtk+-2.24.28-r1` and then `emerge
-1 gtk-engines-adwaita` should pull in the 3.20.2 version of it.
You can then, for good measure, update gtk+ to version 2.24.31-r1 (`emerge -1
=x11-libs/gtk+-2.24.31-r1`), I think.