https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-emulation/cloud-init-22.2-r1 installs files into unexpected paths. Discovered on: amd64 (internal ref: ci)
Created attachment 783836 [details] build.log build log and emerge --info
ci has reproduced this issue with version 22.2.2 - Updating summary.
ci has reproduced this issue with version 22.4 - Updating summary.
gcc14_tinderbox has reproduced this issue with version 23.4 - Updating summary.
ci has reproduced this issue with version 24.2 - Updating summary.
ci has reproduced this issue with version 24.2-r1 - Updating summary.
ci has reproduced this issue with version 24.4 - Updating summary.
ci has reproduced this issue with version 24.4-r3 - Updating summary.
tinderbox-stable has reproduced this issue in a STABLE environment with version 23.4
tinderbox-stable has reproduced this issue in a STABLE environment with version 24.2
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e41c5c3ca4cb468f2fa85f2c48f08f1541b1d32f commit e41c5c3ca4cb468f2fa85f2c48f08f1541b1d32f Author: Sam James <sam@gentoo.org> AuthorDate: 2025-03-31 17:04:31 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-03-31 17:05:45 +0000 app-emulation/cloud-init: port to python-single-r1 The package isn't suitable for PEP517, as it installs data files and it simply happens to be written in Python, rather than intending to be imported and so on. Unfortunately, for the remaining PEP517 holdouts, there's little pressure upstream for them to port to a proper build system yet, as while setuptools deprecated the `setup.py` entrypoint some time ago, there's no removal in sight yet, so the only pressing side is on Gentoo's where we want to cleanup distutils-r1's support for that. It was arguably a mistake to really have these packages use distutils-r1 in the first place. The obvious workaround for now is to invoke setup.py manually w/ python-single-r1, and punt the question until setuptools removal of the entrypoint looks closer (at which time, other distros will be putting pressure on upstreams too). Of course, if at the time of such a setuptools change, the package is still not fixed, then we'd have to remove it. (The same issues apply to bug #922160 which isn't fixed by this, but hopefully won't be an actual problem until that aforementioned removal in setuptools itself of the other bits.) Bug: https://bugs.gentoo.org/922160 Closes: https://bugs.gentoo.org/850964 Closes: https://bugs.gentoo.org/909872 Closes: https://bugs.gentoo.org/952196 Signed-off-by: Sam James <sam@gentoo.org> app-emulation/cloud-init/cloud-init-24.4-r4.ebuild | 124 +++++++++++++++++++++ app-emulation/cloud-init/cloud-init-9999.ebuild | 91 +++++++++------ 2 files changed, 178 insertions(+), 37 deletions(-)
