Did portage bork itself? (SOLVED)

[devsk]

Code: Select all

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  #='/var/db update'  @='/var/db move'
  s='/var/db SLOT move'  %='binary move'  S='binary SLOT move'
  p='update /etc/portage/package.*'
/usr/portage/profiles/updates/4Q-2023.....................
/usr/portage/profiles/updates/3Q-2023....................
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-2.1.1 -> dev-python/charset-normalizer-2.1.1
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-2.1.1-r1 -> dev-python/charset-normalizer-2.1.1-r1
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-3.0.0 -> dev-python/charset-normalizer-3.0.0
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-3.0.1 -> dev-python/charset-normalizer-3.0.1
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-3.0.1 -> dev-python/charset-normalizer-3.0.1
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-3.0.1 -> dev-python/charset-normalizer-3.0.1
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-3.1.0 -> dev-python/charset-normalizer-3.1.0
!!! Cannot update binary: Destination exists.
!!! dev-python/charset_normalizer-3.1.0 -> dev-python/charset-normalizer-3.1.0
!!! Cannot update binary: Destination exists.
!!! dev-python/uri_template-1.2.0-r1 -> dev-python/uri-template-1.2.0-r1
!!! Cannot update binary: Destination exists.
!!! dev-python/uri_template-1.2.0-r1 -> dev-python/uri-template-1.2.0-r1
!!! Cannot update binary: Destination exists.
!!! dev-python/uri_template-1.2.0-r1 -> dev-python/uri-template-1.2.0-r1
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.10/emerge", line 57, in main
    retval = emerge_main()
  File "/usr/lib/python3.10/site-packages/_emerge/main.py", line 1306, in emerge_main
    return run_action(emerge_config)
  File "/usr/lib/python3.10/site-packages/_emerge/actions.py", line 3848, in run_action
    return action_sync(emerge_config)
  File "/usr/lib/python3.10/site-packages/_emerge/actions.py", line 2415, in action_sync
    success, msgs = syncer.auto_sync(options=options)
  File "/usr/lib/python3.10/site-packages/portage/emaint/modules/sync/sync.py", line 89, in auto_sync
    return self._sync(repos, return_messages, emaint_opts=options)
  File "/usr/lib/python3.10/site-packages/portage/emaint/modules/sync/sync.py", line 261, in _sync
    self._do_pkg_moves()
  File "/usr/lib/python3.10/site-packages/portage/emaint/modules/sync/sync.py", line 272, in _do_pkg_moves
    if self.emerge_config.opts.get("--package-moves") != "n" and _global_updates(
  File "/usr/lib/python3.10/site-packages/portage/_global_updates.py", line 41, in _global_updates
    return _do_global_updates(
  File "/usr/lib/python3.10/site-packages/portage/_global_updates.py", line 257, in _do_global_updates
    bindb.update_ents(repo_map, onUpdate=onUpdate)
  File "/usr/lib/python3.10/site-packages/portage/dbapi/__init__.py", line 426, in update_ents
    aux_update(cpv, metadata_updates)
  File "/usr/lib/python3.10/site-packages/portage/dbapi/bintree.py", line 284, in aux_update
    raise KeyError(cpv)
KeyError: 'dev-python/jsonschema-4.14.0'

What is this? Is python trying to move package from a name of a_b to a-b and failing?

How do I recover?

[devsk]

All emerge operations end with this error. I can not update any package.

[Goverp]

I think I had a similar result yesterday that cleared when I re-synced a couple of hours later.
This may not affect you: I sync by downloading the squashfs snapshot, definitely a non-standard way of syncing, but I did have problems because the snapshot date AFAIR Nov 7 seemed broken. The Nov 9 snapshot worked OK. As I say, it might not be what's causing your problem, but the snapshot might reflect a problem with the underlying portage tree that you synced against.

[devsk]

Code: Select all

KeyError: 'dev-python/jsonschema-4.14.0'

Does anybody know where this key is coming from? I don't have jsonschema-4.14.0 installed right now. So, why is it even looking at that version?

I am completely blocked by this. What a nightmare!!

[grknight]

This looks to have to do with binary packages, but this is only a guess.

Similar to the old Bug 571126 but this may be a regression. Might be worth filing a new bug if portage is recent.

Edit: Other related bug to initial messages: Bug 791856

[devsk]

That's a very good hint @grknight! I can archive the binary packages folder and rebuild it just with current packages and see what happens.

[devsk]

That worked! Thanks @grknight for the hint in the right direction!

[js08]

ran into the same problem today.

moving away my binpkgs solved it.