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
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6dc01f35dd8efcd50dcc9a7dd12e7483c280d020 commit 6dc01f35dd8efcd50dcc9a7dd12e7483c280d020 Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2023-07-08 14:27:51 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2023-07-08 14:29:14 +0000 app-portage/elogv: 0.8.0 + start using DISTUTILS_USE_PEP517 Closes: https://bugs.gentoo.org/909885 Signed-off-by: Sebastian Pipping <sping@gentoo.org> app-portage/elogv/Manifest | 1 + app-portage/elogv/elogv-0.8.0.ebuild | 56 ++++++++++++++++++++++++++++++++++++ 2 files changed, 57 insertions(+)
[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.
