The packages are stuck on py3.6 which means they will be pain once we switch to 3.7. Please test them on 3.7 *and* 3.8 (so we don't to revisit this in a few months), and update PYTHON_COMPAT appropriately. If it doesn't work, please either fix it, remove Python or issue last rites. Please consider this urgent.
The bug has been referenced in the following commit(s):
Author: Michał Górny <email@example.com>
AuthorDate: 2020-04-19 19:43:23 +0000
Commit: Michał Górny <firstname.lastname@example.org>
CommitDate: 2020-04-19 19:57:54 +0000
package.mask: Last rite media-sound/beets
Signed-off-by: Michał Górny <email@example.com>
profiles/package.mask | 6 ++++++
1 file changed, 6 insertions(+)
Created attachment 633880 [details]
ebuild for beets-1.4.9
This is a working ebuild for the current version of beets. It uses python3_7, python3_8 fails because dev-python/jellyfish is not (yet) ready for python3_8.
I think it would be sad if beets would drop out of portage.
I use media-sound/beets and would like to help maintain / upgrade the ebuild,
the project is alive and support up to python3.8.
Maybe proxy-maintain this can ease the upgrade.
I have been working on this ebuild + 9999,
it has tests and I would like some reviews.
*** Bug 721976 has been marked as a duplicate of this bug. ***
The bug has been closed via the following commit(s):
Author: Guillaume Seren <firstname.lastname@example.org>
AuthorDate: 2020-04-25 17:31:10 +0000
Commit: Joonas Niilola <email@example.com>
CommitDate: 2020-06-01 12:28:16 +0000
media-sound/beets: cleanup ebuild
Signed-off-by: Guillaume Seren <firstname.lastname@example.org>
Signed-off-by: Joonas Niilola <email@example.com>
media-sound/beets/beets-1.4.9-r1.ebuild | 179 +++++++++++++++++++-------------
1 file changed, 107 insertions(+), 72 deletions(-)