[06:15] <mup> PR snapd#12136 closed: many: stub devicestate.Install{Finish,SetupStorageEncryption}() <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12136>
[06:30] <mup> PR snapd#12145 opened: release: snapd 2.57.3 <Squash-merge> <Created by mvo5> <https://github.com/snapcore/snapd/pull/12145>
[06:40] <mup> PR snapd#12145 closed: release: snapd 2.57.3 <Squash-merge> <Skip spread> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/12145>
[07:03] <EduGomezE> Hi! I've been working on a small PR on snapd, and many spread tests are failing, not sure why. I see that is the case for many other PRs. Is this expected or should I look into why they failed?
[08:07] <mardy> hi EduGomezE! Unfortunately we have quite a few flacky tests. Please have a look at the failed ones, and see if they seem related to your changes. You can also go to the test page, and find the "Re-run jobs" button on the top right, then select "Re-run failed jobs"
[08:08] <mardy> then if the test is flacky the failure might go away on its own.
[09:05] <EduGomezE> ok thanks, I'll look into it
[10:26] <mup> PR snapd#12143 closed: wrappers: journal namespaces did not honor journal.persistent <Squash-merge> <quota> <Created by Meulengracht> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12143>
[10:36] <mup> PR snapd#12146 opened: image: update `prepre-image` work with UC20+ style classic  models <Created by mvo5> <https://github.com/snapcore/snapd/pull/12146>
[10:41] <mup> PR snapd#12147 opened: release: snapd 2.57.3 <Created by mvo5> <https://github.com/snapcore/snapd/pull/12147>
[10:51] <mup> PR snapd#12148 opened: daemon: add `ensureStateSoon()` when calling systems POST api <Created by mvo5> <https://github.com/snapcore/snapd/pull/12148>
[11:21] <mup> PR snapd#12149 opened: i/b/power_observe: Allow daemon on classic and update udev policy <Created by valentindavid> <https://github.com/snapcore/snapd/pull/12149>
[17:27] <mup> PR snapd#12147 closed: release: snapd 2.57.3 <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12147>
[18:28] <mup> PR snapd#12150 opened: release: merge 2.57.3 changelogs <Simple 😃> <Skip spread> <Created by mvo5> <https://github.com/snapcore/snapd/pull/12150>
[18:32] <imi> how do I find out which snap package provides given file? for instance I can run dpkg -S /bin/bash to find out that this file is provided by the bash dpkg package. Is there a similar command for snap packages?
[18:40] <ogra> imi, no, and it would be pointless ... snaps are isolated from the system and from each other ... so a "dpkg -S /bin/bash" could have a ton of results 
[18:40] <ogra> ... since each snap could ship its own bash if it wanted
[18:41] <imi> dpkg -S only works for installed packages
[18:41] <imi> whereas apt-file search would search all packages disregarding whether they are installed or not
[18:41] <ogra> yes, i know 
[18:41] <ogra> and i was referring to the dpkg -S functionality 
[18:42] <imi> then most probably I have at most one snap package installed shipping /bin/bash
[18:42] <ogra> could be ... but that is only relevant to the apps inside this snap anyway
[18:43] <imi> so that means there's no way to trace back a file to the snap package it is shipped by?
[18:44] <ogra> wll, snaps are gpg signed readonly filesystem images that never get unpacked ... you can inspect them through their mount points undet /snap
[18:44] <ogra> *under
[18:45] <imi> ok so for instance how do I figure out which package this file is from?: lrwxrwxrwx 1 root root 13 szept 15 18:27 /snap/bin/joplin -> /usr/bin/snap
[18:46] <ogra> thats just an alias for whatever is defined in joplins snapcraft.yaml
[18:46] <ogra> under the "apps:" section
[18:47] <ogra> you can inspect the joplin package via /snap/joplin/current/
[18:48] <ogra> details about the command should be in /snap/joplin/current/meta/snap.yaml ... looks at "apps:" there 
[21:35] <mup> PR snapcraft#3912 closed: discovery.py: correct comment, "extensions" should say "plugins" <Created by rpjday> <Merged by cmatsuoka> <https://github.com/snapcore/snapcraft/pull/3912>