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.
I just pushed a pull-request to update sigal to 2.0. This brings py 3.7 support, but not py 3.8, due to missing support in dependencies (mainly boto). I don't see that happening too soon, I guess py 3.8 is only happening when upstream moves from boto to boto3 (and boto3 gets py3.8 support in gentoo). Other than that, the s3 and testsuite support would have to be removed, which was considered unacceptable when I published sigal 1.3 without s3.
Ping.
(there are comments waiting on PR to be addressed)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ad45260c36ef5a6eae7758aae9e49bf00c9ee40e commit ad45260c36ef5a6eae7758aae9e49bf00c9ee40e Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-09-21 14:07:46 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-09-21 14:07:46 +0000 media-gfx/sigal: Remove last-rited pkg Closes: https://bugs.gentoo.org/718334 Signed-off-by: Michał Górny <mgorny@gentoo.org> media-gfx/sigal/Manifest | 1 - media-gfx/sigal/metadata.xml | 31 ------------------------------- media-gfx/sigal/sigal-1.3.0.ebuild | 37 ------------------------------------- profiles/package.mask | 1 - 4 files changed, 70 deletions(-)
