Summary: | app-emulation/cloud-init: needs to use PEP517 build (DistutilsNonPEP517Build) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | bpholman5, prometheanfire |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | https://github.com/canonical/cloud-init/issues/3986 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 909855 |
Description
Michał Górny
2023-07-08 06:45:17 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. Final ping. Please note that we will not hesitate to last rite low profile packages over this. https://github.com/canonical/cloud-init/issues/3986 still isn't cared about upstream it seems Thanks for the updated comment. Upstream is actively working on PEP517 support for multiple distributions at the moment[1]. Distutils currently installs non-python code to custom path locations in cloud-init's packaging - some additional packaging changes will be required in cloud-init to add PEP517 support. https://github.com/canonical/cloud-init/issues/5027 |