UbuntuIRC / 2020 /03 /02 /#snappy.txt
niansa
Initial commit
4aa5fce
[09:14] <marcustomlinson> hey guys, can snapd tell me if a particular snap has been installed and removed before?
[09:42] <mup> PR snapcraft#2954 opened: cli: enable config file for base snapcraft command <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2954>
[10:19] <ogra> sil2100, is vorlon not coming to the sprint ? i was hoping we could discuss some changes to ubuntu-image this week (i also wanted to talk to waveform about some pi-gadget breakage too, but i see he wont be here either)
[10:56] <cjwatson> ogra: he's not
[11:01] <ogra> cjwatson, yeah, just learned that in person from sil ...
[11:18] <mup> PR snapcraft#2955 opened: repo: respect http proxy for apt update <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2955>
[11:30] <mup> PR snapcraft#2794 closed: Add gnome 3 34 extension <Created by hellsworth> <Closed by hellsworth> <https://github.com/snapcore/snapcraft/pull/2794>
[11:30] <mup> PR snapcraft#2945 closed: ci: only run docker builds for cron <Created by sergiusens> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/2945>
[11:33] <mup> PR snapcraft#2956 opened: Add gnome 3 34 extension <Created by hellsworth> <https://github.com/snapcore/snapcraft/pull/2956>
[12:45] <zyga> jdstrand: hello
[12:45] <jdstrand> zyga: hey
[12:45] <zyga> jdstrand: how are you doing? :)
[12:46] <zyga> jdstrand: I'll try to progress on the session problem you highlighted this week, if I can
[12:46] <jdstrand> zyga: I'm ok. it feels real weird not being there
[12:46] <zyga> jdstrand: there are some empty-ish rooms around
[12:46] <jdstrand> I heard
[12:48] <zyga> jdstrand: not as a security review, but I was curious if https://github.com/snapcore/snapd/pull/8216 works on your system
[12:48] <mup> PR #8216: tests: add session-tool, a su / sudo replacement <Created by zyga> <https://github.com/snapcore/snapd/pull/8216>
[12:48] <zyga> can. you use it to spawn a shell as yourself
[12:48] <zyga> and run snaps (with current snapd)
[12:49] <zyga> I would like to eliminate the chance that there's something extra special about your system
[12:49] <zyga> perhaps pam_apparmor
[12:49] <zyga> or something like that
[12:50] <jdstrand> zyga: is this for the transient scope issue I had?
[12:50] <zyga> yes
[12:50] <zyga> and a lot of other tests that effectively incorrectly run code as the "test" user
[12:50] <jdstrand> zyga: so, the system in question was a default bionic desktop install in a vm
[12:50] <jdstrand> (so no pam-apparmor
[12:50] <jdstrand> )
[12:50] <zyga> aha
[12:51] <zyga> so it should work, I tested that case
[12:51] <zyga> if you want to fire it up anyway feel free but not really needed
[12:51] <jdstrand> I also don't have pam apparmor on my laptop
[12:52] <jdstrand> zyga: I'm going to finish up some reviews today. when I am about to do those, I will try out 8216 and report problems, if any. if you don't herre from me, consider it fine. is that ok?
[12:52] <zyga> jdstrand: that's great
[12:52] <zyga> I'll push forward on getting to the bottom of the problem you uncovered
[13:07] <mup> PR snapcraft#2955 closed: repo: respect http proxy for apt update <Created by cjp256> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2955>
[13:34] <jdstrand> zyga: the next time you see mvo, can you let him know that I added comments to the Frankfurt sprint doc and various meeting invites?
[13:34] <zyga> jdstrand: I will
[13:34] <jdstrand> thanks
[13:34] <zyga> jdstrand: he's here but we're in a meeting now
[13:36] <jdstrand> zyga: it isn't urgent, just want him to be aware
[14:31] <zyga> jdstrand: mvo now knows
[14:54] <jdstrand> zyga: thanks! :)
=== hggdh is now known as hggdh-msft
[15:16] <zyga> stgraber: do you think this bug is what you showed me a number of times
[15:16] <zyga> https://bugs.launchpad.net/snapd/+bug/1865503
[15:16] <mup> Bug #1865503: snapd (deb) fails to install snapd (snap) inside LXD on a buildd based image <core20> <snapd:Confirmed> <https://launchpad.net/bugs/1865503>
[15:16] <zyga> stgraber: first snap installation fails in lxd
[15:20] <stgraber> Yeah, run it again and it will succeed
[15:25] <zyga> stgraber: right, it seems to be a bug at the intersection of udev and lxd
[15:25] <zyga> stgraber: can you think of a reason why this fails, is it the sandbox lxd provides?
[15:26] <zyga> stgraber: is there a way to detect LXD that's reliable
[15:26] <zyga> stgraber: so that we could perhaps fix the base udev rules to not fail
[15:26] <stgraber> /dev/lxd is usually a good bet, that or systemd-detect-virt
[15:26] <zyga> stgraber: excellent
[15:27] <zyga> stgraber: I'll run by foundations and check if this can be fixed
[15:30] <zyga> rharper: can you please join a hangout, it should be in the invite
[15:30] <rharper> y
[16:06] <mup> PR snapd#8217 opened: o/devicestate: delay the creation of mark-seeded task until asserts are loaded <Bug> <Created by stolowski> <https://github.com/snapcore/snapd/pull/8217>