[00:45] PR snapd#11849 opened: tests: enable centos-9 === not_phunyguy is now known as phunyguy [06:36] morning [07:07] PR snapd#11850 opened: overlord,snap: add support for per-snap storage on ubuntu-save [07:32] hi all [07:45] hey [08:17] PR snapd#11851 opened: spread: drop openSUSE Leap 15.2 [08:27] PR snapd#11329 closed: o/assertstate: auto aliases for apps that exist [08:27] PR snapd#11829 closed: o/state: use more detailed NoStateError in state [09:17] PR snapd#11770 closed: wrappers: write journald config files for quota groups with journal quotas (3/n) [09:32] PR snapd#11843 closed: interfaces/builtin: remove the name=org.freedesktop.DBus restriction in cups-control AppArmor rules [09:54] PR snapcraft#3778 opened: extensions: Add environment variables for runtime [10:44] PR snapcraft#3771 closed: extensions: do not fail during installation [11:51] mborzecki: the snapd.apparmor service is disable in arch (according to our spread tests); is this expected? [12:03] mardy: yes, it needs to be enabled manually [12:03] same as the snapd.service, iow the policy is that none of the services get enabled/started by default when you install a new package [12:05] mborzecki: mmm... but then is https://github.com/snapcore/snapd/pull/11842 wrong? Or do I just need to manually enable it in the spread tests? I wonder if users will know that they have to enable it... [12:05] PR #11842: o/ifacestate: warn if the snapd.apparmor service is disabled [12:07] mardy: spread tests should already be doing that on arch, and the users are supposed to follow https://wiki.archlinux.org/title/Snap#Installation which mentions that both services need to be enabled/started [12:13] mborzecki: I see that the spread tests enable only the apparmor.service, not the one shipped by snapd. And indeed they fail: https://github.com/snapcore/snapd/runs/6771954604?check_suite_focus=true [12:17] mborzecki: I added a commit to that PR [12:21] mardy: ok, thanks1 [12:21] * mardy: ok, thanks! [13:03] PR snapd#11852 opened: cmd/snap-repair: fix snap-repair tests silently failing === leftyfb_ is now known as leftyfb [14:23] PR snapd#11851 closed: spread: drop openSUSE Leap 15.2 [15:49] here's an intersting one... 22.04 and today a 65MB storage device just showed up in my task bar (because it shows mounts/storage devices). [15:49] /var/lib/snapd/snaps/core20_1434.snap (deleted) on /media/leftyfb/disk type squashfs (ro,nosuid,nodev,relatime,errors=continue,uhelper=udisks2) [15:49] what's that all about? [15:50] an interesting thing investigating it, it's got a /boot/androidboot directory, though it's empty [15:51] my core20 snap is no version 1518. Is this some sort of orpan? [15:51] orphan* [15:51] my core20 snap is on version 1518. Is this some sort of orphan? [16:43] PR snapd#11852 closed: cmd/snap-repair: fix snap-repair tests silently failing [17:09] PR snapcraft#3779 opened: meta: handle version git [18:29] PR snapcraft#3780 opened: cli: reset the logger before running legacy === diddledani_ is now known as diddledani === cjp256_ is now known as cjp256 === hardwire_ is now known as hardwire [20:15] PR snapcraft#3780 closed: cli: reset the logger before running legacy