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.
ci has reproduced this issue with version 1.0.2-r1 - Updating summary.
Absolutely final ping before I really start last riting stuff.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff9d5ffcb83f1044ddaabd3b6fe84986bc363411 commit ff9d5ffcb83f1044ddaabd3b6fe84986bc363411 Author: Arthur Zamarin <arthurzam@gentoo.org> AuthorDate: 2025-03-22 20:29:13 +0000 Commit: Arthur Zamarin <arthurzam@gentoo.org> CommitDate: 2025-03-22 20:32:33 +0000 app-portage/elicense: migrate to PEP517 Closes: https://bugs.gentoo.org/922210 Closes: https://bugs.gentoo.org/909884 Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org> app-portage/elicense/elicense-1.0.2-r1.ebuild | 36 --------------------------- app-portage/elicense/elicense-1.0.2-r2.ebuild | 24 ++++++++++++++++++ 2 files changed, 24 insertions(+), 36 deletions(-)
