[08:19] <jchittum> jdstrand: it's a bit of a collaboration between Canonical and Docker. If this is related to the OpenSSL Vuln, the ROCKS team at Canonical is working on building, testing, and publishing the containers now. But they can lag a little while for verification
[08:19] <jchittum> but we kicked off all the build as soon as the package was published
[08:34] <rbasak> jchittum: I wonder if you need to be able prepare and QA (embargoed) images from (embargoed) security updates in advance.
[08:37] <mwhudson> jdstrand: are you going to do the go snap updates? (the issues do not sound very exciting)
[09:27] <jchittum> rbasak: we can't do that. CPC is not in the embargo groups. and we build from the public archives. building from a private PPA of a pre-released thing adds a surprising layer of copmlexity and possible issues to livecd-rootfs
[09:27] <jchittum> the tl:dr is that to build from those PPAs, we must insert, via a livecd-rootfs build hook in a private PPA, add in the credentials to whatever PPA we want to build with, and then clean it all up to ensure we don't leak credentials
[09:28] <jchittum> and it means altering build-hooks for secific packages, directly into git. launchpad-buildd itself doesn't support us calling it with a private PPA, with credentials associated with my team, etc.
[09:29] <jchittum> I'd personally love a way to be able to tell launchpad "insert this package from this PPA" and have launchpad know that the user calling for build has access and credentials
[10:19] <xypron> I am looking for a sponsor for LP #1993528
[10:19] -ubottu:#ubuntu-devel- Launchpad bug 1993528 in hart-software-services (Ubuntu) "New upstream release v2022.10" [Undecided, New] https://launchpad.net/bugs/1993528
[11:33] <jdstrand> mwhudson: I am, yes but they are not exciting. I couldn't get to it yesterday but will today
[12:05] <jdstrand> mwhudson: https://git.launchpad.net/go-snap/commit/?id=209c2be844ad07fa9a651da1fcd1630eed5b4430 https://launchpad.net/~go-snap-maintainers/+snap/go118
[12:05] -ubottu:#ubuntu-devel- Commit 209c2be in go-snap "move to go1.18.8 go1.18"
[12:18] <jdstrand> mwhudson: https://git.launchpad.net/go-snap/commit/?id=23cc6b0c63e31a2db4767c4f8983aac9aeddaea3 https://launchpad.net/~go-snap-maintainers/+snap/go119
[12:18] -ubottu:#ubuntu-devel- Commit 23cc6b0 in go-snap "move to go1.19.3 go1.19"
[13:52] <jdstrand> mwhudson: I tested 1.18/candidate (1.18.8) and 1.19/candidate (1.19.3) and they look good
[13:53] <jdstrand> mwhudson: 1.19 is ready to promote. 1.18 is waiting on riscv64
[13:53] <mwhudson> jdstrand: awesome thanks
[14:31] <jdstrand> mwhudson: I went ahead and promoted 1.19 just now
[15:28] <jdstrand> mwhudson: and now that riscv64 is done, I promoted 1.18 just now