| mup | PR snapd#11483 opened: tests/main/snapd-snap: test installing the snapd snap and connecting interfaces <Test Robustness> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/11483> | 01:30 |
|---|---|---|
| mardy | mborzecki: good morning! I need some advice about selinux :-) | 06:09 |
| mardy | 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 |
| mup | PR #10676: cmd/snap-update-ns/change.go: sort needed, desired and not reused mount entries <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/10676> | 06:10 |
| mardy | it's 100% reproducible, so it's certainly due to my and Ian's changes in that PR | 06:11 |
| mardy | 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 | 06:31 |
| mborzecki | morning | 07:09 |
| mborzecki | mardy: sure, le me see | 07:09 |
| mborzecki | mardy: it isn't entirely clear why those mounts appear, was there a mimic on /usr and /var/cache? | 07:14 |
| mborzecki | aah ok, let's see appstream metadata would use /usr/share/metainfo, and /var/cache/app-info so that explains it | 07:16 |
| mborzecki | wonder why this never came up earlier | 07:16 |
| mborzecki | mardy: i'll push a patch to that branch | 07:21 |
| mardy | mborzecki: good taht you understood it, because I'm still in the dark :-) | 07:27 |
| mardy | mborzecki: I see that it can be reproduced by running "snap disconnect snap-store:appstream-metadata" and then re-running the store app | 07:27 |
| mborzecki | 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:35 |
| mborzecki | so it will trigger a mimic on /usr/share and /var/cache | 07:36 |
| mborzecki | 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:36 |
| mborzecki | mardy: still intersting that it came up only now? | 07:38 |
| mborzecki | since the mounts are now ordered differently hm | 07:38 |
| mardy | 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:39 |
| mborzecki | mardy: haha so if i push a patch that leaves pawel and miguel? 🙂 | 07:41 |
| mborzecki | 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:41 |
| mardy | mborzecki: thanks, looking forward to see what it was all about :-) | 07:57 |
| pstolowski | morning | 08:04 |
| mardy | pstolowski: hi! | 08:06 |
| mborzecki | mardy: i've pushed a patch to ian's branch | 08:34 |
| mup | Bug #1959452 changed: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 <kern-2637> <Snappy:Invalid> <linux-raspi (Ubuntu):Invalid> <https://launchpad.net/bugs/1959452> | 09:28 |
| zyga[m] | hello :-) | 09:30 |
| mup | Bug #1959452 opened: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 <kern-2637> <Snappy:Invalid> <linux-raspi (Ubuntu):Invalid> <https://launchpad.net/bugs/1959452> | 09:31 |
| mup | Bug #1959452 changed: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 <kern-2637> <Snappy:Invalid> <linux-raspi (Ubuntu):Invalid> <https://launchpad.net/bugs/1959452> | 09:34 |
| mup | Bug #1959452 opened: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 <kern-2637> <Snappy:Invalid> <linux-raspi (Ubuntu):Invalid> <https://launchpad.net/bugs/1959452> | 09:40 |
| mup | Bug #1959452 changed: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 <kern-2637> <Snappy:Invalid> <linux-raspi (Ubuntu):Invalid> <https://launchpad.net/bugs/1959452> | 09:43 |
| mup | PR core20#133 closed: hooks: mkdir /var/cups to avoid writable mimic creation for snaps using cups <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/core20/pull/133> | 10:13 |
| mup | PR core18#187 closed: hooks: mkdir /var/cups to avoid writable mimic creation for snaps using cups <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/core18/pull/187> | 10:14 |
| mup | PR core#129 closed: hooks: mkdir /var/cups to avoid writable mimic creation for snaps using cups <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/core/pull/129> | 10:15 |
| mup | PR snapd#11439 closed: run-checks: replace linters w/ golangci <Created by MiguelPires> <Closed by MiguelPires> <https://github.com/snapcore/snapd/pull/11439> | 14:08 |
| mup | PR snapd#11473 closed: tests: validate tests tools just on google and qemu backends <Simple 😃> <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/11473> | 15:14 |
| mup | PR snapd#11484 opened: interfaces/mount-observe: allow read on /proc/1/mount* files <Simple 😃> <Created by jdstrand> <https://github.com/snapcore/snapd/pull/11484> | 20:40 |
| mup | PR snapd#11484 closed: interfaces/mount-observe: allow read on /proc/1/mount* files <Simple 😃> <Created by jdstrand> <Closed by jdstrand> <https://github.com/snapcore/snapd/pull/11484> | 21:30 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!