My usual "emerge -auDvN world" yesterdau failed over a bunch of slot
conflict for various dev-qt packages (appeared to be related to :0/30 vs
:0/30.30). However, in process of trying various options to at least
get something emerged, I have ended up getting, for most (but not all)
invocations of emerge, something like:
Total: 114 packages (61 upgrades, 5 new, 48 reinstalls), Size of
downloads: 997,745 KiB
Conflict: 1 block (all satisfied)
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.9/emerge", line 51, in <module>
retval = emerge_main()
File "/usr/lib/python3.9/site-packages/_emerge/main.py", line 1328, in
emerge_main
return run_action(emerge_config)
File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 3954,
in run_action
retval = action_build(emerge_config, spinner=spinner)
File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 468,
in action_build
mydepgraph.display_problems()
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
10485, in display_problems
self._compute_abi_rebuild_info()
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 923,
in _compute_abi_rebuild_info
if dep.parent.installed:
AttributeError: 'SetArg' object has no attribute 'installed'
That one was for a full world update, but I've also gotten it for single
packages. Some single package invocations worked, such as updating
portage itself from 3.0.30-r3 (stable) to 3.0.30-r4 (~amd64) but the
newer version has the same failures.
I've done a bit of searching, but haven't been able to find anything
relevant. This failure doesn't seem related to any particular conflict,
as it appears immediately after what looks like a normal list of
packages to be upgraded or reinstalled.
Thanks for any suggestions about which fine manual I should read, or
which version of portage might work any better.
Jack
conflict for various dev-qt packages (appeared to be related to :0/30 vs
:0/30.30). However, in process of trying various options to at least
get something emerged, I have ended up getting, for most (but not all)
invocations of emerge, something like:
Total: 114 packages (61 upgrades, 5 new, 48 reinstalls), Size of
downloads: 997,745 KiB
Conflict: 1 block (all satisfied)
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.9/emerge", line 51, in <module>
retval = emerge_main()
File "/usr/lib/python3.9/site-packages/_emerge/main.py", line 1328, in
emerge_main
return run_action(emerge_config)
File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 3954,
in run_action
retval = action_build(emerge_config, spinner=spinner)
File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 468,
in action_build
mydepgraph.display_problems()
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
10485, in display_problems
self._compute_abi_rebuild_info()
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 923,
in _compute_abi_rebuild_info
if dep.parent.installed:
AttributeError: 'SetArg' object has no attribute 'installed'
That one was for a full world update, but I've also gotten it for single
packages. Some single package invocations worked, such as updating
portage itself from 3.0.30-r3 (stable) to 3.0.30-r4 (~amd64) but the
newer version has the same failures.
I've done a bit of searching, but haven't been able to find anything
relevant. This failure doesn't seem related to any particular conflict,
as it appears immediately after what looks like a normal list of
packages to be upgraded or reinstalled.
Thanks for any suggestions about which fine manual I should read, or
which version of portage might work any better.
Jack