14:02:22 #startmeeting Fedora IoT Working Group Meeting 14:02:22 Meeting started Wed Jan 8 14:02:22 2020 UTC. 14:02:22 This meeting is logged and archived in a public location. 14:02:22 The chair is pbrobinson. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:02:22 The meeting name has been set to 'fedora_iot_working_group_meeting' 14:02:22 #chair pwhalen pbrobinson bcotton jsmith 14:02:22 Current chairs: bcotton jsmith pbrobinson pwhalen 14:02:22 #topic roll call 14:02:47 * pwhalen is here 14:03:04 * puiterwijk is here 14:04:54 * bcotton is here 14:05:42 #topic 1) ==== Working Group process and admin ==== 14:06:14 any one have anything for WG? 14:06:43 * pwhalen has nothing 14:08:53 #topic 2) ==== Fedora Rawhide AKA F-32 ==== 14:09:43 puiterwijk: how's your f32 bits going? 14:10:24 I'm right now testing a fix that would allow ignition and clevis to not prevent booting without wired network but also still work with wired. 14:10:40 (reliably) 14:11:47 excellent, happy to test as well when you're ready 14:11:48 Also testing provisioning with that, and just adding tests to that codebase so we can start to make that available hopefully by end of week 14:12:35 awesome sauce 14:13:01 * jsmith joins late... 14:13:46 anyone seeing any issues in f32? 14:15:21 it seems mostly fine with my testing 14:15:52 I've got a bunch of bits to do 14:16:59 anyone with anything else? 14:17:01 I need to check installations a bit more, but the images looked ok, podman working 14:20:16 yea, same, still trying to catch up post shut down 14:20:17 #topic 3) ==== Fedora 31 ==== 14:20:42 I need to do a new compose to deal with some random libxml2 issue 14:20:50 with layered packages 14:21:16 which is not something we particularly encourage but ¯\_(ツ)_/¯ 14:22:59 I tested the latest, which was Fedora-IoT-31-20191230, didnt hit any issues with the images. upgrade only offers 1226 14:23:14 31.20191226 14:23:49 ie upgrade on an existing f31 system 14:24:12 yea, I think it's the right content though, I'm not sure what happens with these random "get the previous composes date in the current one" issue 14:24:33 ah, ok.. yea that might be it. 14:24:48 but not hitting anything else 14:24:52 I think I'll promote this one out to stable and then kick off another compose 14:25:37 pbrobinson: I think that that's related to the ostree summary file being generated by something that's not the compose process, but I'd need to check that 14:27:11 puiterwijk: what outside of the compose process would generate the summary file out of interest? 14:27:45 pbrobinson: That's the funny part, I don't know right now. Many things can trigger their generation, and I think the compose process doesn't 14:28:20 heh, fun indeed 14:28:21 pbrobinson: the ostree sync-to-master-mirror process generates them, but it should only do so in the destination 14:28:54 puiterwijk: thanks, I'll ask about it at some point, don't need to deal with it now 14:29:28 #info latest compose being promoted today, new compose happening once that's done 14:29:40 #info next compose will have the 5.4.x kernel 14:29:45 #topic 4) ==== Open Floor ==== 14:31:30 anyone with anything for open floor 14:31:36 * jsmith has nothing 14:32:06 * pwhalen has nothing else 14:33:01 thank you all 14:33:01 #endmeeting