dev-python/pycryptodome is a fork of discontinued dev-python/pycrypto. Since the latter is dead since 2014, it'd be reasonable to replace its uses with the former. As usual, the packages are partially compatible and block one another. What to do: 1. If the package works both with pycrypto and pycryptodome, and does not use pkg_resources or any other magic to enforce a particular package, you can just add ||-dep like: || ( dev-python/pycryptodome[${PYTHON_USEDEP}] dev-python/pycrypto[${PYTHON_USEDEP}] ) 2. If the code works both with pycrypto and pycryptodome but pkg_resources enforce pycrypto, send a trivial patch upstream to switch to pycryptodome and then we can switch as well. 3. If the code does not work with pycryptodome, I'm afraid you'll end up having to prepare a bigger patch that updates the code to use the new APIs.
commit 82c3d61152a5527a0f68869918c92ee2d0e46b51 Author: Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> Date: Mon Mar 6 14:10:09 2017 +0100 app-forensics/volatility: version bump, allow building against pycryptodome Bug: https://bugs.gentoo.org/show_bug.cgi?id=599056 Bug: https://bugs.gentoo.org/show_bug.cgi?id=611582 Package-Manager: Portage-2.3.3, Repoman-2.3.1
I see no keyword request for the remainder of the architectures. Only amd64 and x86 have keywords now. If you want to end the migration this year, you might want to start that up now.
(In reply to Jeroen Roovers from comment #2) > If you want to end the migration this year end => finish
620458 depends on this bug
So FWICS potr->poezio are the only blockers. Plus cleanup of bittornado and s3ql.
(In reply to Michał Górny from comment #5) > So FWICS potr->poezio are the only blockers. Plus cleanup of bittornado and > s3ql. Done, I think.
