Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 909926

Summary: dev-python/path-and-address: needs to use PEP517 build (DistutilsNonPEP517Build)
Product: Gentoo Linux Reporter: Michał Górny <mgorny>
Component: Current packagesAssignee: Ben Kohler <bkohler>
Status: RESOLVED FIXED    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 909855    

Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2023-07-08 06:49:52 UTC
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
Comment 1 Larry the Git Cow gentoo-dev 2023-07-08 18:43:29 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4785682b90d67f3062d084f1a07152301e8bd7be

commit 4785682b90d67f3062d084f1a07152301e8bd7be
Author:     Ben Kohler <bkohler@gentoo.org>
AuthorDate: 2023-07-08 13:13:56 +0000
Commit:     Ben Kohler <bkohler@gentoo.org>
CommitDate: 2023-07-08 18:41:40 +0000

    dev-python/path-and-address: update EAPI 7 -> 8, use PEP517 build
    
    Closes: https://bugs.gentoo.org/909926
    
    Signed-off-by: Ben Kohler <bkohler@gentoo.org>

 .../path-and-address-2.0.1-r1.ebuild                 | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-07-08 20:40:53 UTC
[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.