Copying the ebuild and just renaming from anjuta-3.28.0.ebuild to anjuta-3.34.0.ebuild as well as changing PYTHON_COMPAT from python2_7 to python3_7 seems to work fine. I can still run gtkpod, although neither seems to be a very active project. I'll be glad to attach the ebuild, but it's just a rename and one character edit. Other edits might be appropriate, such as increased minimum versions of deps, but I didn't look any deeper.
Looks like this has been done. Should I just close as fixed, or should it refer to the commit?
The bug has been closed via the following commit(s):
Author: Mart Raudsepp <email@example.com>
AuthorDate: 2020-06-12 21:52:43 +0000
Commit: Mart Raudsepp <firstname.lastname@example.org>
CommitDate: 2020-06-12 22:15:33 +0000
dev-util/anjuta: bump to 3.34.0
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <email@example.com>
dev-util/anjuta/Manifest | 1 +
dev-util/anjuta/anjuta-3.34.0.ebuild | 148 +++++++++++++++++++++++++++++++++++
2 files changed, 149 insertions(+)
Note that the bump does NOT add python3 compatibility, because it simply crashes when python loader plugin is actually loaded with py3.7. 3.8 complains about missing symbols on load (probably not linking to python3-embed properly). But python2.7 seems to work (at least as long as you don't load the plugin multiple times per anjuta session).
So you might want to file a new bug about py3 support and ideally help investigate too :)
Alternatively it feels like something that might want to grow a python USE flag or just unconditionally disable it for now, but the upstream build system doesn't seem to support that well without patching.