Testing for x11-wm/awesome-3.4.9-r1. Re-emerged after some days. Reproducible: Always Steps to Reproduce: 1. Just emerge it 2. 3. Actual Results: make[1]: *** No rule to make target `//var/tmp/portage/portage/x11-wm/awesome-3.4.9-r1/work/awesome-3.4.9_build/all'. Stop. make: *** [all] Error 2 testuser@archtester ~ $ sudo ls -l //var/tmp/portage/portage/x11-wm/awesome-3.4.9-r1/work/awesome-3.4.9_build/ total 156 -rw-r--r-- 1 portage portage 9190 Jun 28 15:45 awesome.doxygen -rw-r--r-- 1 portage portage 13796 Jun 28 15:45 awesomerc.lua -rw-r--r-- 1 portage portage 324 Jun 28 15:45 awesome-version-internal.h -rw-r--r-- 1 portage portage 26215 Jun 28 15:45 CMakeCache.txt drwxr-xr-x 12 portage portage 4096 Jun 28 15:45 CMakeFiles -rw-r--r-- 1 portage portage 7247 Jun 28 15:45 cmake_install.cmake drwxr-xr-x 2 portage portage 4096 Jun 28 15:45 common -rw-r--r-- 1 portage portage 254 Jun 28 15:45 config.h drwxr-xr-x 3 portage portage 4096 Jun 28 15:45 lib -rw-r--r-- 1 portage portage 63468 Jun 28 15:45 Makefile drwxr-xr-x 7 portage portage 4096 Jun 28 15:45 manpages drwxr-xr-x 5 portage portage 4096 Jun 28 15:45 themes
Created attachment 278439 [details] the build log
Created attachment 278441 [details] my emerge --info
Does 3.4.10 work?
hmphhh!! >>> Emerging (1 of 1) x11-wm/awesome-3.4.9-r1 >>> Installing (1 of 1) x11-wm/awesome-3.4.9-r1 >>> Jobs: 1 of 1 complete Load avg: 2.97, 2.97, 1.98 >>> Auto-cleaning packages.. >>> Verifying ebuild manifests >>> Emerging (1 of 1) x11-wm/awesome-3.4.10 >>> Installing (1 of 1) x11-wm/awesome-3.4.10 >>> Recording x11-wm/awesome in "world" favorites file... Something broke somewhere. Seems that revdep-rebuild has caught and fixed it. Leave you to tie it off.
I pinned it. used $sudo emerge awesome. $sudo emerge =kde-base/kcron-4.6.3; build loses all. used #emerge awesome. emerged. !!!!!????! Please explain.
Has this happened with any recent versions of awesome?