[08:36] <onetwo> does anyone have a link to how to use cloud-init for Arhc Linux please.
=== onetwo is now known as djinn12
=== djinn12 is now known as syzygy
=== syzygy is now known as onetwo
[11:34] <minimal> can someone please review #1804?
[11:41] <minimal> falcojr, blackboxsw, rharper: ^^^
[12:34] <meena> minimal: would you really need --no-color when not calling it interactively?
[12:37] <meena> minimal: you need to reformat your files with black
[12:38] <meena> and, I would also add a test that shows the other path rc-update
[12:39] <minimal> meena: the "black" issues are for existing code that I wasn't changing
[12:39] <minimal> so I assumed I shouldn't/wouldn't have to "fix" unrelated black warnings in this PR
[12:40] <minimal> meena: I added the "--nocolor" just in case at a later date any output would be logged or otherwise used
[13:06] <meena> aye
[13:20] <minimal> meena: ok, additional test added
[15:10] <meena> I did an upgrade of my FreeBSD VM, and now it's no longer recognised as NoCloud, but assumed to be OpenStack.
[15:10] <meena> I wonder what broke
[15:11] <meena> well, a bunch of stuff… 
[15:19] <minimal> meena: you interviewing for FB? "move fast and break stuff" ;-)
[16:07] <meena> minimal: to be fair, this is FreeBSD-14.0-CURRENT, and I'm using PkgBase, itself in continuous Beta…, to upgrade it
[16:17] <meena> how the heck do you use ds-identify
[16:19] <falcojr> It's a systemd generator. Not sure if non-systemd systems use it 
[16:21] <minimal> how to you get "tox" to give more output about things like "black" errors?
[16:22] <meena> FreeBSD-geom package… is… new, and was missing
[16:23] <meena> didn't realize cloud-init -lsr doesn't clean up ds-identify's stuff
[16:24] <minimal> falcojr: any complaint if I remove the "# vi" line from end of alpine.py as meena suggested?
[16:26] <falcojr> nope, sounds good 
[16:27] <falcojr> Don't actually know re black. There's also a format target that will do the black formatting. I have it integrated into my editor 
[16:28] <minimal> I just ran black manualy earlier (must have done something wrong as I'm convinced it pointed out issues in untouched parts of the file lol)
[16:52] <meena> falcojr: I've managed to change one usage of get_devicelist() from net.get_devicelist() to distros.networking.get_devicelist() but there's still a bunch left
[16:53] <meena> So I'll leave that until the refactoring
[17:24] <jrm> meena: I'll take a look.  For https://reviews.freebsd.org/D37142 we will have to wait for the maintainer.  In the meantime, what do you suggest as a sanity check at run-time?  Or, am I going to have to learn something about cloud-init and figure it out myself.
[17:28] <meena> jrm: good question 
[17:29] <meena> I don't wanna give you more work than you're already doing
[17:29] <meena> falcojr: ping ^
[17:31] <meena> what's a good sanity check that cloud-init… works
[17:36] <falcojr> Cloud-init status returns no error, logs say datasource was detected and able to retrieve metadata 
[17:38] <minimal> don't know if I'm going mad, fixed the requested change in the PR but girhub still shows "1 change requested", can't see anything to mark it as done
[17:49] <falcojr> oh, that's just a github thing. It'll say that till I approve 
[17:53] <minimal> ah ok, it's confusing
[17:54] <meena> jrm: you might have to put some files into /var/lib/cloud-init/seed? to make cloud-init status make sense: https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
[17:54] <meena> why can i not remember 
[17:55] <meena> but i think just an otherwise empty file with #cloud-config
=== VoliKoN5 is now known as VoliKoN
=== VoliKoN5 is now known as VoliKoN
[20:13] <meena> falcojr: i think I'm happy with what I'm about to push