portage 2.2.24: backtrace during emerge --sync (after proper sync, before updates) Looks different, so filing another bug... sent 1.00M bytes received 119.91M bytes 792.84K bytes/sec total size is 395.11M speedup is 3.27 === Sync completed for gentoo Traceback (most recent call last): File "/usr/lib/python-exec/python2.7/emerge", line 50, in <module> retval = emerge_main() File "/usr/lib64/python2.7/site-packages/_emerge/main.py", line 1161, in emerge_main return run_action(emerge_config) File "/usr/lib64/python2.7/site-packages/_emerge/actions.py", line 3101, in run_action return action_sync(emerge_config) File "/usr/lib64/python2.7/site-packages/_emerge/actions.py", line 1976, in action_sync retvals = syncer.auto_sync(options={'return-messages': False}) File "/usr/lib64/python2.7/site-packages/portage/emaint/modules/sync/sync.py", line 98, in auto_sync emaint_opts=options) File "/usr/lib64/python2.7/site-packages/portage/emaint/modules/sync/sync.py", line 232, in _sync sync_scheduler.wait() File "/usr/lib64/python2.7/site-packages/_emerge/AsynchronousTask.py", line 54, in wait self._wait() File "/usr/lib64/python2.7/site-packages/portage/util/_async/AsyncScheduler.py", line 81, in _wait self._event_loop.iteration() File "/usr/lib64/python2.7/site-packages/portage/util/_eventloop/EventLoop.py", line 270, in iteration if not x.callback(f, event, *x.args): File "/usr/lib64/python2.7/site-packages/_emerge/PipeReader.py", line 80, in _output_handler self.wait() File "/usr/lib64/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait self._wait_hook() File "/usr/lib64/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/python2.7/site-packages/portage/util/_async/AsyncFunction.py", line 58, in _async_func_reader_exit self.wait() File "/usr/lib64/python2.7/site-packages/_emerge/AsynchronousTask.py", line 57, in wait self._wait_hook() File "/usr/lib64/python2.7/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook self._exit_listener_stack.pop()(self) File "/usr/lib64/python2.7/site-packages/portage/sync/controller.py", line 373, in _sync_task_exit self.sync_callback(self.sync_task) File "/usr/lib64/python2.7/site-packages/portage/sync/controller.py", line 331, in _sync_callback exitcode, message, updatecache_flg = proc.result ValueError: need more than 2 values to unpack FEATURES="assume-digests binpkg-logs compress-build-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms split-log strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
Just as side note, this is using a "handmade" profile, and one of the atoms in "packages" just got pkgmoved and still needs to be fixed in the profile. Oddity worth noting. https://gitweb.gentoo.org/dev/dilfridge.git/tree/profiles/uni-regensburg
OK this may have been related to * a repos.conf file with type "laymansync" * and layman accidentally getting downgraded to stable... Closing as invalid, is gone after updating layman to ~arch
*** This bug has been marked as a duplicate of bug 567932 ***