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.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=30ec7a8d13d196916b69e933f15b5c722b22fc4e commit 30ec7a8d13d196916b69e933f15b5c722b22fc4e Author: Eli Schwartz <eschwartz@gentoo.org> AuthorDate: 2024-09-10 01:02:13 +0000 Commit: Eli Schwartz <eschwartz@gentoo.org> CommitDate: 2024-09-10 01:16:29 +0000 app-crypt/gpgme: port to pep517 build We don't need setuptools unconditionally. This was probably an autoconf bug in python detection macros, though it appears it is not even run because we don't enable python via "enabled languages" as an arg to configure anyway... Closes: https://bugs.gentoo.org/909868 Closes: https://bugs.gentoo.org/923147 Signed-off-by: Eli Schwartz <eschwartz@gentoo.org> app-crypt/gpgme/gpgme-1.23.2-r2.ebuild | 232 +++++++++++++++++++++++++++++++++ 1 file changed, 232 insertions(+)
