UbuntuIRC / 2022 /06 /10 /#cloud-init.txt
niansa
Initial commit
4aa5fce
=== gschanuel3 is now known as gschanuel
=== gschanuel4 is now known as gschanuel
=== gschanuel1 is now known as gschanuel
=== gschanuel2 is now known as gschanuel
=== gschanuel8 is now known as gschanuel
[06:31] <sam_> hi folks, I tried to file a bug on launchpad but I got an "oops! [...]", so I figured I'd bring it up here for now. It looks like the installation method for init scripts and additional bits (non-Python files at all) isn't compatible with PEP517, so PEP517 installs are broken right now
[06:31] <sam_> we had https://bugs.gentoo.org/850628 in gentoo and ended up realising what the problem was (cc holmanb)
[06:31] <sam_> unfortunately I don't have a good fix
[06:31] <sam_> obviously downstream, in gentoo, we can just install the files manually, but in general, PEP517 with the wheel spec doesn't have a good way of installing data files
[06:31] <sam_> it's a point of much irritation
=== hexa- is now known as h
=== h is now known as hexa
[14:28] <holmanb> sam_: Thanks for the ping and downstream fix! I'll file the launchpad bug. I'll admit I'm not familiar with PEP 517. The log in 850628 doesn't appear to contain error messages or anything indicating this issue. Am I missing the manifestation of this bug in the log?
[16:42] <holmanb> sam_: fyi https://bugs.launchpad.net/cloud-init/+bug/1978328
[16:42] <ubottu> Launchpad bug 1978328 in cloud-init "setup.py is not PEP517 compliant" [Undecided, New]