Honestly, this whole batch should be reverted. $ python3.11 -m pip check jupyter-collaboration 2.0.5 has requirement jupyter-ydoc<3.0.0,>=2.0.0, but you have jupyter-ydoc 1.0.2. $ qlist jupyter-ydoc | grep dist-info | head -1 /usr/lib/python3.12/site-packages/jupyter_ydoc-1.0.2.dist-info/RECORD ^^^^^ I blame jupyter-ydoc-1.0.2-no-node-for-version.patch that literally hardcodes the version number!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5f90591174a6d8593f9c5276a01509db7f87a24d commit 5f90591174a6d8593f9c5276a01509db7f87a24d Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2024-04-02 13:15:44 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2024-04-02 13:21:54 +0000 dev-python/jupyter-ydoc: Revert "revive with version 2.0.1." Reverting the whole batch. The package was added with hardcoded *wrong* version number in the patch, no reply to the bug from the committer. Reverts: 4ce335aa6e799fa18e70b7be7a9ec90ffb96c605 Closes: https://bugs.gentoo.org/928231 Signed-off-by: Michał Górny <mgorny@gentoo.org> dev-python/jupyter-ydoc/Manifest | 1 - .../jupyter-ydoc-1.0.2-no-node-for-version.patch | 30 -------------- dev-python/jupyter-ydoc/jupyter-ydoc-2.0.1.ebuild | 48 ---------------------- dev-python/jupyter-ydoc/metadata.xml | 13 ------ 4 files changed, 92 deletions(-)
(In reply to Michał Górny from comment #0) > Honestly, this whole batch should be reverted. > > $ python3.11 -m pip check > jupyter-collaboration 2.0.5 has requirement jupyter-ydoc<3.0.0,>=2.0.0, but > you have jupyter-ydoc 1.0.2. > $ qlist jupyter-ydoc | grep dist-info | head -1 > /usr/lib/python3.12/site-packages/jupyter_ydoc-1.0.2.dist-info/RECORD > ^^^^^ > > I blame jupyter-ydoc-1.0.2-no-node-for-version.patch that literally > hardcodes the version number! You are right. I have seen various runtime issues after it is package. I guess the versioned dependencies are the root cause.
