[06:28] <mborzecki> morning
[07:34] <mup> PR snapd#9812 closed: packaging/deb, tests/main/lxd-postrm-purge: fix purge inside containers <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/9812>
[07:45] <mborzecki> mvo: hey
[07:46] <mvo> good morning mborzecki
[08:11] <pstolowski> hello!
[08:20] <pstolowski> welcome back everyone
[08:20] <zyga> hello pawel!
[08:21] <zyga> how was your holiday break?
[08:32] <pstolowski> zyga: hi! was awesome, very relaxing
[08:32] <pstolowski> how about you?
[08:33] <mborzecki> pstolowski: hey
[08:33] <pstolowski> hey mborzecki !
[08:34] <zyga> pstolowski my break was shorter but we made it very active
[08:34] <zyga> pstolowski lots of time spent outdoors
[08:36] <pstolowski> sounds awesome
[08:40] <mvo> good morning pstolowski ! nice to have you back. hope you had a great break
[08:40] <mvo> zyga: good morning, so nice to see you too :)
[08:55] <mup> PR snapd#9776 closed: gadget: add validation for "$kernel:ref" style content <Skip spread> <UC20> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9776>
[08:55] <mup> PR snapd#9809 closed: snap: skip help output tests for go-flags v1.4.0 <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9809>
[09:00] <mup> PR snapd#9804 closed: interfaces/opengl: allow RPi MMAL video decoding <Needs security review> <Created by ogra1> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9804>
[09:07]  * ogra hugs mvo 
[09:13]  * mvo hugs ogra 
[09:14]  * ogra is on his way to replace his libreelec installs with UC20 and https://snapcraft.io/kodi-pi-standalone ... thats a big step towards it 
[10:04] <mborzecki> mvo: can you cherry pick https://github.com/snapcore/snapd/pull/9812 to 2.48 in case we do a point release?
[10:04] <mup> PR #9812: packaging/deb, tests/main/lxd-postrm-purge: fix purge inside containers <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/9812>
[10:05] <mvo> mborzecki: let me have a look
[10:15] <mup> PR snapd#9778 closed: asserts/repair.go: add "bases" and "modes" support to the repair assertion <UC20> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9778>
[10:37] <mvo> pedronis: I updated 9777 (just fyi, no real rush at this point)
[10:43] <pedronis> mvo: now I can request myself as reviewer again (mystery), I just queued it
[10:43] <mvo> pedronis: nice
[10:43] <mvo> pedronis: and yes, mystery!
[12:05] <mup> PR snapcraft#3401 closed: ci: uprev pyinstaller and switch timestamp server <Created by cjp256> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3401>
[12:10] <mup> PR snapcraft#3385 closed: yaml_utils: promote module to a package <Created by cjp256> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3385>
[14:27] <zyga> mvo, hey there
[14:28] <mvo> zyga: hey, how are you?
[14:28] <zyga> mvo, we're sorting out project planning in the team but I wanted to drop you a link for something that's coming up this sprint (2 weeks)
[14:28] <zyga> https://git.ostc-eu.org/planning/testing/-/issues/2
[14:28] <zyga> I will work on an OSTC fork but I will also upstream things
[14:29] <zyga> ostc is the open source thing I'm participating in
[14:29] <zyga> cachio, ^ FYI
[14:30] <zyga> cachio, where is your fork/branch of spread btw?
[14:30] <zyga> is it just your fork or did you rename it by any chance
[14:32] <cachio> zyga, hey
[14:33] <cachio> how are you?
[14:33] <zyga> cachio, hola, como estas
[14:33] <cachio> this is the fork https://github.com/sergiocazzolato/spread/tree/master2
[14:33] <cachio> muy bien :)
[14:33] <zyga> ah, great, your github fork
[14:33] <cachio> yes
[14:33] <zyga> I wanted to keep you in the loop of spread patches I'm planning, if any of those would be useful to you or would be relevant to include you in the design phase
[14:34] <cachio> zyga, yes
[14:34] <cachio> nice
[14:34] <cachio> thanks
[14:34] <cachio> just ping me if you need anything
[14:35] <zyga> cachio, I was thinking that if spread did support booting, at least on qemu, with a specific system image, it might be useful to organize core tests to support that, e.g. take <this> image, that's already prepared by a separate stage and just boot it to run tests
[14:35] <zyga> for us it will be the image produced in the previous stage in the pipeline
[14:36] <zyga> (and our images are small so passing them from one step to the next is not hard)
[14:36] <zyga> the ultimate goal will be to take an arm image and run it via spread muxpi backend
[14:36] <zyga> cachio, right now any feedback on the yaml example there is great
[14:37] <zyga> I don't see any of those as final, that will come when I try to upstream it
[14:37] <zyga> that's why I want to have a separate fork, to have unrelated timelines for downstream and upstream work
[14:37] <cachio> zyga, that feature makes sense for qemu
[14:38] <cachio> so far the qemu backend has many restrictions
[14:38] <cachio> which should be addressed
[14:38] <cachio> I'll take a look to the yaml
[14:44] <zyga> cachio, thanks, I'm happy to talk if you want to tweak it at this stage, I'll pick it up tomorrow
[14:44] <mvo> zyga: nice
[14:44] <zyga> cachio, (not sure if URL is final) https://git.ostc-eu.org/planning/testing/-/boards
[14:45] <mvo> zyga: I like this
[14:46] <zyga> mvo, hehe, that's just me doing my usual convincing to use what's in the forge already, and not to use exteral systems
[14:46] <zyga> too bad free gitlab is so limited, paid versions have really nice features
[14:47] <cachio> zyga, thanks for sharing
[14:49] <cachio> zyga, I think the image flag could be usefull also for other backends
[14:49] <zyga> cachio, right, it doesn't have to be local image
[14:49] <cachio> so it is not needed to update the image in the spread.yaml in case you need to test a test image in gce for example
[14:49] <zyga> not sure how the google api looks like but it's plausible to build an image that's compatible in one phase, upload it to google in another and then use that image in the third phase
[14:49] <zyga> yeah
[14:50] <zyga> I think the bigger new item is the syntax for paramteres, the definition side is I think okay but the use side is confusing
[14:50] <zyga> or at least non-obvious
[14:50] <zyga> perhaps it should just be string interpolation with ${image} or $image or something like that
[14:51] <zyga> I'll sleep on this, it's not something I'm convinced about yet
[14:52] <cachio> zyga, agree
[14:52] <cachio> need to think which is the best way to implement that
[14:56]  * cachio afk
[14:56] <zyga> cachio, if we want to use parameters "anywhere" it may be hard, as it implies that the yaml parser needs to somehow understand that
[14:56] <zyga> cachio, ok, let's chat later
[14:57] <cachio> zyga, thanks
[14:57] <cachio> I'll be back in 20
[15:08] <zyga> mvo, offtopic, we've set up mattermost IRC bridge lately and it works fairly well
[15:09] <zyga> I'm mentioning this because it lets people use (arguably) more comfortable mattermost while still being visible on IRC
[15:09] <zyga> it's per channel obviously
[15:15] <ijohnson> zyga, is that another server that you have to run, or is it like just a plugin that is enabled server side ?
[15:16] <zyga> ijohnson, it's a self-hosted service that runs but I honestly don't know the details as my colleague deployed it yesterday
[15:16] <zyga> it was generally easy with the exception of some confusing instructions early on during credentials management
[15:16] <zyga> ijohnson, it's live in #ostc if you want to look
[15:17] <ijohnson> zyga: ah I see, yeah I meant to set something like that up for myself to use only mattermost for this IRC channel, but I never got around to it yet
[15:17] <ijohnson> also happy new year zyga!
[15:17] <zyga> ijohnson, happy new year :)
[15:20] <ijohnson> :-)
[15:57] <mbeierl> can a devmode snap (ie: microstack) be updated, or do I need to remove it and lose everything in microstack and reinstall to get the latest version?
[15:58] <ijohnson> you can manually refresh devmode snaps
[15:58] <mbeierl> perfect, thanks ijohnson
[16:35] <ijohnson> pedronis: I reviewed #9803
[16:35] <mup> PR #9803: many: clarify gadget role-usage consistency checks for UC16/18 vs UC20 <Cleanup :broom:> <Run nested> <UC20> <Created by pedronis> <https://github.com/snapcore/snapd/pull/9803>
[16:37] <pedronis> ijohnson: thx, I'll work on the feedback in my morning
[16:37] <ijohnson> the feedback is pretty minimal fine for a followup if you prefer
[16:43] <pedronis> ijohnson: about supporting multi-volume setups, they would pass the checks but we still don't support gadget updates with them atm
[16:44] <ijohnson> but you could still build an image with a multi-volume gadget and not do gadget updates though right ?
[16:44] <pedronis> yes
[16:45] <ijohnson> admittedly, I didn't try to do so with your branch so perhaps there are other things missing in the stack that prevent using multi-volumes, but having just a unit test about validating a multiple volume gadget with all the ubuntu-* roles on a single volume seems useful to me
[17:11] <mup> PR snapcraft#3402 opened: cli: add missing quote key creation hint <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/3402>
[17:21] <mup> PR snapcraft#3403 opened: storeapi: remove unused MissingSnapdError <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/3403>
[18:25]  * cachio afk
[20:38] <mup> PR snapd#9815 opened: {,sec}boot: pass "key-name" to the FDE hooks <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9815>
[21:03] <mup> PR snapd#9816 opened: interfaces, wrappers: misc comment fixes, etc <Simple 😃> <Skip spread> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9816>
[22:51] <mup> PR snapcraft#3404 opened: build(deps): bump lxml from 4.5.0 to 4.6.2 <dependencies> <python> <Created by dependabot[bot]> <https://github.com/snapcore/snapcraft/pull/3404>