/srv/irclogs.ubuntu.com/2022/09/15/#snappy.txt

mupPR snapd#12136 closed: many: stub devicestate.Install{Finish,SetupStorageEncryption}() <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12136>06:15
mupPR snapd#12145 opened: release: snapd 2.57.3 <Squash-merge> <Created by mvo5> <https://github.com/snapcore/snapd/pull/12145>06:30
mupPR 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>06:40
EduGomezEHi! 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?07:03
mardyhi 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:07
mardythen if the test is flacky the failure might go away on its own.08:08
EduGomezEok thanks, I'll look into it09:05
mupPR 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:26
mupPR snapd#12146 opened: image: update `prepre-image` work with UC20+ style classic  models <Created by mvo5> <https://github.com/snapcore/snapd/pull/12146>10:36
mupPR snapd#12147 opened: release: snapd 2.57.3 <Created by mvo5> <https://github.com/snapcore/snapd/pull/12147>10:41
mupPR snapd#12148 opened: daemon: add `ensureStateSoon()` when calling systems POST api <Created by mvo5> <https://github.com/snapcore/snapd/pull/12148>10:51
mupPR 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>11:21
mupPR snapd#12147 closed: release: snapd 2.57.3 <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12147>17:27
mupPR snapd#12150 opened: release: merge 2.57.3 changelogs <Simple 😃> <Skip spread> <Created by mvo5> <https://github.com/snapcore/snapd/pull/12150>18:28
imihow 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:32
ograimi, 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 wanted18:40
imidpkg -S only works for installed packages18:41
imiwhereas apt-file search would search all packages disregarding whether they are installed or not18:41
ograyes, i know 18:41
ograand i was referring to the dpkg -S functionality 18:41
imithen most probably I have at most one snap package installed shipping /bin/bash18:42
ogracould be ... but that is only relevant to the apps inside this snap anyway18:42
imiso that means there's no way to trace back a file to the snap package it is shipped by?18:43
ograwll, snaps are gpg signed readonly filesystem images that never get unpacked ... you can inspect them through their mount points undet /snap18:44
ogra*under18:44
imiok 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/snap18:45
ograthats just an alias for whatever is defined in joplins snapcraft.yaml18:46
ograunder the "apps:" section18:46
ograyou can inspect the joplin package via /snap/joplin/current/18:47
ogradetails about the command should be in /snap/joplin/current/meta/snap.yaml ... looks at "apps:" there 18:48
mupPR snapcraft#3912 closed: discovery.py: correct comment, "extensions" should say "plugins" <Created by rpjday> <Merged by cmatsuoka> <https://github.com/snapcore/snapcraft/pull/3912>21:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!