This package still uses the legacy eclass code paths. These paths are deprecated and pose a significant maintenance cost. Please update the package to use PEP517 build mode. For more information, please see the Python Guide, particularly; https://projects.gentoo.org/python/guide/migration.html#migrating-to-pep-517-builds
[Adding this comment en-masse, sorry for the noise, but it's important.) 1. Please take particular care to check file diffs before/after, possibly using `iwdevtools`. Keep a particular eye out for e.g. config files now missing from /etc and instead being in /usr/lib/python*/site-packages, etc. 2. Please make sure to do the migration in a new revision in ~arch, partly because of 1.
Final ping. Please note that we will not hesitate to last rite low profile packages over this.
Sorry about this. I did try it before and it seemed totally broken. I was hoping upstream would do something, but it's half dead. Looking at it again though, it seems find once I remove the existing phase functions. I just have to fix the locales.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3d8894b413deb3beb5e0470abedee674ff1852a1 commit 3d8894b413deb3beb5e0470abedee674ff1852a1 Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2024-03-09 15:15:39 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2024-03-09 15:15:58 +0000 app-emulation/fs-uae-launcher: Bump to 3.1.70, drop 3.1.68, migrate to PEP517 Closes: https://bugs.gentoo.org/909874 Signed-off-by: James Le Cuirot <chewi@gentoo.org> app-emulation/fs-uae-launcher/Manifest | 2 +- ...ncher-3.1.68.ebuild => fs-uae-launcher-3.1.70.ebuild} | 16 +++++----------- 2 files changed, 6 insertions(+), 12 deletions(-)