[05:29] <mborzecki> morning
[05:31] <mborzecki> mardy: that goes through fakestore in the tests?
[05:35] <mardy> mborzecki: hi! Yes! I'm using the make_snap_installable_with_id(), and that function creates a snap who belongs to "developer1"
[05:35] <mardy> and for some reason this causes the snap to be uninstallable
[05:37] <mardy> https://github.com/mardy/snapd/blob/feature/snap-microk8s-shared-system-usernames/tests/main/system-usernames-microk8s/task.yaml#L35-L39
[05:49] <mborzecki> mardy: this is in spread?
[05:50] <mborzecki> ah, well i see the task so it must be
[05:51] <mborzecki> hm and it's done after the account key of developer1 has been acked
[05:54] <mardy> I will try to move things around. But the installation itself is done later, in the "execute" step
[05:59] <mborzecki> mardy: can you run `snap known account` and `snap known account-key` to make sure that the developer assertions are there?
[06:16]  * mardy tries soon
[06:40] <mborzecki> mardy: can you take a look at https://github.com/snapcore/snapd/pull/10465 ?
[06:59] <mardy> mborzecki: looking. Meanwhile, here's the relevant part of the output for the "snap known" commands: https://paste.ubuntu.com/p/NdYn4bYFc5/
[07:01] <mardy> mborzecki: +1
[07:12] <pstolowski> morning
[07:13] <mborzecki> pstolowski: hey
[07:14] <mardy> pstolowski: hi!
[08:03] <pedronis> hello,  https://github.com/snapcore/snapd/pull/10458 needs reviews
[08:05] <pedronis> https://github.com/snapcore/snapd/pull/10448 also needs 2nd reviews
[08:59] <mvo> pedronis: just finished an interview, will have a look
[09:32] <zyga-mbp> good morning
[13:53] <mborzecki> pedronis: is there a way to generate assertions that can be correctly encoded using assertstest package?
[13:53] <mborzecki> ha, got it
[13:53] <mborzecki> hmm hmm, i'm getting `internal error: content cannot be empty` when trying to Encode() a model generated by boottest.MakeMockUC20Model
[13:53] <mborzecki> do i need the whole store stack for this?
[13:53] <mborzecki> mvo: can you land? https://github.com/snapcore/snapd/pull/10465 this should fix lp builds
[13:54] <pedronis> mborzecki: yes, if you need to Encode them, yes
[13:54] <pedronis> mborzecki: FakeAssertion is just meant for consumption that doesn't need serializing or being put in an actual assertion database
[13:57] <pedronis> mborzecki: mvo: that log is already in 2.51 afaict
[13:58] <pedronis> at last it's on the release branch
[13:58] <pedronis> so it needs a backport
[14:04] <mvo> pedronis: +1 - thanks so much for checking
[14:10] <mvo> pedronis: I cherry picked this now
[15:14] <mborzecki> pedronis: yeah, figured as much, the pr that's up does exactly that
[15:33] <mborzecki> meh, calling seedtest's MakeSeed() in managers tests isn't such a good idea, i get the impression thtat both the managers test set up and seedtest tries to add the same snap and revision declarations
[15:33] <mborzecki> and those bits are actually working against each other
[15:42] <pedronis> mborzecki: mmh,  you should be able to control what happens, it might be that SetUp does too much for your case, but I don't think it adds snaps to the system, but it might sign assertions for them
[20:43]  * cachio_ afk