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 closed via the following commit(s):
Author: Michał Górny <firstname.lastname@example.org>
AuthorDate: 2020-08-22 09:47:30 +0000
Commit: Michał Górny <email@example.com>
CommitDate: 2020-08-22 09:51:41 +0000
sci-visualization/fityk: Eradicate python3.6
Signed-off-by: Michał Górny <firstname.lastname@example.org>
sci-visualization/fityk/fityk-1.3.1.ebuild | 45 ++----------------------------
1 file changed, 2 insertions(+), 43 deletions(-)
I emerge --sync'ed yesterday (08/28) and I'm still seeing the "package masked, removal in 30 days" notice.
M. Gorny's commit on 08/22 looks like it was possible to disable Python support in this application and sidestep the issue (even if at the cost of libfityk Python bindings).
Is this package still going to disappear from portage on 08/22 +30 days?
I'm sorry, I must've forgotten to remove it from the list after updating the ebuild. Will unmask it in a few minutes.