See tracker.
net-im/gajim: Drop pycrypto dependency, no longer supported by upstream pycrypto itself is dead. There are problems with pycryptodome and upstream doesn't actually care about pycrypto* at all.
Fixed in gajim-0.16.8-r1.
w8, it's actually not fixed. Just dependency has been removed, but still may be picked up if present on the system. See also <https://dev.gajim.org/gajim/gajim/issues/5294>. Should be solved by upstream one way or the other.
What exactly are the problems with pycryptodome?
I've done a full code inspection on gajim, and except for its references to pycrypto in dependency files, it will work just fine with pycryptodome installed. If installed using emerge, it should be fine to simply change the dependency from pycrypto to pycryptodome to migrate to pycryptodome.
When starting Gajim with pycrypdome installed instead it fails on: ERROR: start symbol translation_unit_or_empty undefined
Will look into it. Maybe I missed something.
Amadeusz, the particular issue you are experiencing seems to be introduced by dev-python/pycparser-2.18. It can be worked around by downgrading to pycparser-2.17. Then gajim starts without issue.
Daniel, thanks for testing that. I suppose it's not ideal to block dev-python/pycparser-2.18* in gajim ebuild.
This bug is obsolete, all gajim versions in the portage tree depend on pycryptodome.
