[01:30] PR snapd#11483 opened: tests/main/snapd-snap: test installing the snapd snap and connecting interfaces [06:09] mborzecki: good morning! I need some advice about selinux :-) [06:10] mborzecki: it's about https://github.com/snapcore/snapd/pull/10676, the Fedora tests are failing on this line: https://github.com/snapcore/snapd/blob/master/tests/main/selinux-clean/task.yaml#L119 [06:10] PR #10676: cmd/snap-update-ns/change.go: sort needed, desired and not reused mount entries [06:11] it's 100% reproducible, so it's certainly due to my and Ian's changes in that PR [06:31] looking at the logs, the selinux warnings happen after (or during): taskrunner.go:439: DEBUG: Running task 430 on Do: Disconnect snap-store:appstream-metadata from core:appstream-metadata [07:09] morning [07:09] mardy: sure, le me see [07:14] mardy: it isn't entirely clear why those mounts appear, was there a mimic on /usr and /var/cache? [07:16] aah ok, let's see appstream metadata would use /usr/share/metainfo, and /var/cache/app-info so that explains it [07:16] wonder why this never came up earlier [07:21] mardy: i'll push a patch to that branch [07:27] mborzecki: good taht you understood it, because I'm still in the dark :-) [07:27] mborzecki: I see that it can be reproduced by running "snap disconnect snap-store:appstream-metadata" and then re-running the store app [07:35] mardy: yeah, that interface sets up a bind mount from /var/lib/snapd/hostfs/{usr/share/metainfo,var/cache/app-info} into the snap layout [07:36] so it will trigger a mimic on /usr/share and /var/cache [07:36] mardy: also that's only because the cores do not ship those directories, perhaps they could and we could avoid some complications we have now [07:38] mardy: still intersting that it came up only now? [07:38] since the mounts are now ordered differently hm [07:39] mborzecki: I see. But then I wonder if it isn't better to push it as a separate PR, otherwise it will be hard to find people to review it (since on that PR, I guess that me and Ian cannot vote anymore, since we both contributed to it) :-) [07:41] mardy: haha so if i push a patch that leaves pawel and miguel? 🙂 [07:41] mardy: so the test is passing now, i'll try to look around a bit more in the debug shell though, confirm that things make sense [07:57] mborzecki: thanks, looking forward to see what it was all about :-) [08:04] morning [08:06] pstolowski: hi! [08:34] mardy: i've pushed a patch to ian's branch [09:28] Bug #1959452 changed: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64

[09:30] hello :-) [09:31] Bug #1959452 opened: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64

[09:34] Bug #1959452 changed: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64

[09:40] Bug #1959452 opened: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64

[09:43] Bug #1959452 changed: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64

[10:13] PR core20#133 closed: hooks: mkdir /var/cups to avoid writable mimic creation for snaps using cups [10:14] PR core18#187 closed: hooks: mkdir /var/cups to avoid writable mimic creation for snaps using cups [10:15] PR core#129 closed: hooks: mkdir /var/cups to avoid writable mimic creation for snaps using cups [14:08] PR snapd#11439 closed: run-checks: replace linters w/ golangci [15:14] PR snapd#11473 closed: tests: validate tests tools just on google and qemu backends [20:40] PR snapd#11484 opened: interfaces/mount-observe: allow read on /proc/1/mount* files [21:30] PR snapd#11484 closed: interfaces/mount-observe: allow read on /proc/1/mount* files