At my thinderox I run (rarely) into a racy condition where the /usr/portage repository is changed whilst an emerge is running, yielding into something like: >>> Jobs: 277 of 318 complete Load avg: 12.1, 12.9, 12.9 >>> Jobs: 278 of 318 complete Load avg: 12.1, 12.9, 12.9 >>> Jobs: 278 of 318 complete, 1 running Load avg: 12.1, 12.9, 12.9 >>> Emerging (279 of 318) x11-misc/xdg-utils-1.1.3::gentoo >>> Jobs: 278 of 318 complete, 1 running Load avg: 12.1, 12.9, 12.9 Exception in callback AsynchronousTask.wait() handle: <Handle AsynchronousTask.wait()> Traceback (most recent call last): File "/usr/lib64/python3.5/asyncio/events.py", line 127, in _run self._callback(*self._args) File "/usr/lib64/python3.5/site-packages/_emerge/AsynchronousTask.py", line 84, in wait self._wait_hook() File "/usr/lib64/python3.5/site-packages/_emerge/AsynchronousTask.py", line 195, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/python3.5/site-packages/_emerge/EbuildBuild.py", line 68, in _start_with_metadata settings.configdict["pkg"]["SRC_URI"], = aux_get_task.future.result() File "/usr/lib64/python3.5/asyncio/futures.py", line 294, in result raise self._exception portage.exception.PortageKeyError: 'x11-misc/xdg-utils-1.1.3' In the past the emerge just finished/crashed and I could detect and act at this situation. But since few weeks the emerge doesn't finish (at least it is still running/idling after 12 hours). The command line is: emerge,14215 -b /usr/lib/python-exec/python3.5/emerge --update --newuse --changed-use --deep --changed-deps=y @system Coudl the behaviour changed so that emerge finishes?
In order to cover all cases we really need to use locking to prevent the sync from occurring while emerge is running. *** This bug has been marked as a duplicate of bug 639374 ***
