Getting the following output when attempting : emerge @world -r * (u'ebuild', u'/', u'dev-python/scientificpython-2.9.1', u'merge') Reissuing the command I get : emerge: It seems we have nothing to resume... @system does not have a problem with -r. Posting emerge-info for portage 2.1.11.62 Reproducible: Always
Created attachment 345836 [details] emerge-info Violated size restrictions on post, so I'm attaching
*Note* dev-python/scientificpython-2.9.1 is only an example as all listed packages for @world rebuild are denoted with the pre-specified syntax... sorry I was pruning my post, until I realized it was my emerge-info. Also I couldn't dump : emerge @world -r >> failed.world.resume file either at least the >> operation. Let me know if you need any other output or config files. Thanks
I was able to fix this updating x11-libs/gdk-pixbuf. With my libspectre-0.2.7 bug 466292 , it was pointed out to me that libpng1.5 needed app-text/ghostscript-gpl-9.06 rebuilt. So staring at my unusual output, it stated that x11-libs/gdk-pixbuf-2.26.5 needed libpng1.4 (should have posted that). It didn't occur to me that the errata could be related to a pixelbuffer. So when running revdep-rebuild showed that there was an update for gdk-pixbuf from 2.26.5 - 2.28.0, voi'la, no more errata on @world -r resume. BUT Portage didn't pickup the gdk-pixbuff update and wanted to rebuild 2.26.5 and even complained about requiring libpng1.4. Revdep-rebuild pointed out the update looking for libpng1.5 consistency....not sure why emerge failed, maybe metadata sync inconsistency.
