[04:52] <zyga> Good morning
[04:52] <zyga> School day today so I will be a bit preoccupied in the next few hours
[05:02] <mborzecki> morning
[05:17] <mborzecki> https://github.com/snapcore/snapd/pull/5753/ is an easy win
[06:11] <mborzecki> mvo: hi, think we could land this? https://github.com/snapcore/snapd/pull/5753
[06:11] <mvo> mborzecki: looking
[06:11] <mborzecki> btw. this one is easy win too https://github.com/snapcore/snapd/pull/5752
[06:11] <mvo> mborzecki: yes!
[06:12] <mvo> mborzecki: 5752 failed in tests, because of grub?
[06:12] <mvo> mborzecki: in any case, approved and can land as soon as tests are happy
[06:12] <mvo> mborzecki: thank you
[06:17] <mborzecki> mvo: thanks
[06:17] <mborzecki> ok, i'm off to school
[06:18] <mvo> mborzecki: good luck
[06:44] <zyga> hey, daughter handled, now going to our son's new school a bit further away
[06:45] <zyga> I'll be operational around 10:30
[06:46] <zyga> mborzecki: request: can you do a test PR and merge zyga/fix/trespassing-v2 into your instance work to see if you can dump the workarounds? please?
[06:46] <zyga> with that, I'm off to the bus stop
[07:17] <pstolowski> mornings
[07:26] <zyga> New school looks familiar
[08:15] <mvo> a second review for 5736 would be great
[08:15] <mvo> with that I can do a new 2.35.1 release
[08:27] <zyga> I’m stuck but I’ll review it now mvo
[08:28] <zyga> Ah I already did
[08:33] <zyga> Hey John
[08:34] <Chipaca> zyga: 'sup
[08:41] <zyga> School
[08:41] <mvo> hey Chipaca !
[08:41] <zyga> New school, new class
[08:41] <Chipaca> mvo: o/!
[08:42] <zyga> Want out but $REALITY
[09:10] <mborzecki> re
[09:11] <mborzecki> zyga: let me check your branch
[09:11] <mborzecki> zyga: with mount ns mapping branch right?
[09:12] <zyga> Yes
[09:12] <zyga> With all of your instance features
[09:13] <zyga> School is over
[09:13] <zyga> I’ll be home in 15 minutes
[09:22] <mborzecki> zyga: dropped the workarounds and running with your branch now
[09:25] <thresh> is there anything wrong with the release process since this night?
[09:26] <thresh> I've got a "
[09:26] <thresh> Status
[09:26] <thresh> Manual review pending
[09:26] <thresh> gah.  for the newly uploaded nightly.
[09:26] <thresh> "Automated review not yet completed", "Task 058f17f1-e946-43d1-a783-0aa4ca04acb0 failed"
[09:27] <thresh> also, good morning.
[09:29] <popey> ^ sparkiegeek
[09:29] <mborzecki> mvo: is snap-failure expected to be used everywhere?
[09:31] <mvo> mborzecki: snap-failure? sorry, do you have some more context for me?
[09:31] <sparkiegeek> thresh, popey: good morning - can you share the name of your snap so I can take a look?
[09:32] <mborzecki> mvo: got a report from arch user, apparently snapd exiter unexpectedly and systemd tried to run snap-failure
[09:32] <popey> sparkiegeek: vlc
[09:32] <mborzecki> mvo: iirc this would only make sense if reexec is used
[09:32] <mvo> mborzecki: oh, interessting
[09:32] <mvo> mborzecki: yeah, it should not run on classic
[09:32] <mborzecki> mvo: we have this in snapd.service.in OnFailure=snapd.failure.service
[09:33] <mborzecki> mvo: so it's tried everywhere
[09:33] <mvo> mborzecki: yeah
[09:33] <sparkiegeek> popey: thanks, looking
[09:33] <mborzecki> mvo: i'll try to ask why it failed in the first place anyway :P
[09:33] <mvo> mborzecki: please do
[09:33] <niemeyer> Morning all
[09:33] <mvo> mborzecki: I added an item to my todo to fix this
[09:34] <niemeyer> mvo: Just did some edits on the UC16/18 doc
[09:34] <mvo> niemeyer: good morning!
[09:34] <mvo> niemeyer: yay, thank you
[09:34] <niemeyer> mvo: Tried to make it a bit more high-level.. not quite sure about what's the audience for the doc, and the audience may also drift :)
[09:35] <mvo> niemeyer: yeah, looks good, thanks for streamlining it
[09:36] <niemeyer> mvo: np, let's see if we can think of other interesting deltas
[09:36] <niemeyer> mvo: Thanks for putting it up as well
[09:39] <mborzecki> zyga: getting some unexpected apparmor denials
[09:40]  * mvo nods
[09:41] <mborzecki> zyga: https://paste.ubuntu.com/p/Kdk8yjbFC9/
[09:42] <mborzecki> anyone noticed that google:opensuse-42.3-64:tests/main/appstream-id is failing often? not jus the test, but afaict that particular combo
[09:45] <pstolowski> mborzecki: yes
[09:47] <zyga> mborzecki: looking
[09:47] <zyga> mborzecki: I'm at my desk, all fuss is over today
[09:47] <mborzecki> zyga: hehe, no mandatory ice cream?
[09:48] <pstolowski> mborzecki: but google:ubuntu-14.04-64:tests/main/appstream-id just now
[09:48] <pstolowski> *but also*
[09:48] <zyga> mborzecki: ice cream? no, but we did get a sandwich on the way home
[09:48] <zyga> pstolowski: I haven't seen appstream-id failures, is that new?
[09:48] <mborzecki> pstolowski: heh
[09:49] <zyga> [Mon Sep  3 09:28:38 2018] audit: type=1400 audit(1535966919.486:60): apparmor="DENIED" operation="capable" profile="snap-update-ns.test-snapd-layout" pid=17922 comm="3" capability=2  capname="dac_read_search"
[09:49] <zyga> [Mon Sep  3 09:28:39 2018] audit: type=1400 audit(1535966920.206:61): apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 profile="snap-update-ns.test-snapd-layout_foo" name="/tmp/.snap/snap/" pid=18214 comm="3" srcname="/snap/" flags="rw, rbind"
[09:49] <zyga> those two?
[09:49] <mborzecki> zyga: it does a round trip to the store, so maybe somewhere there
[09:49] <mborzecki> zyga: yes
[09:49] <zyga> so the first one is interesting dac_read_search is just taversing unreadable directories
[09:49] <pstolowski> zyga: i started noticing it today
[09:49] <zyga> we should add that to the profile, looks like an obviously missing thing
[09:49] <zyga> the second one is interesting
[09:49] <zyga> this looks like attempt to consturct a layout over all of /snap!
[09:50] <zyga> *construct
[09:50] <mvo> tests are very unreliable today, its quite annoying
[09:50] <zyga> mborzecki: can you share the mount profile, I suspect it is trying to create a directory, hits /snap/* and notices that this affects the host filesystem
[09:50] <mborzecki> zyga: the layout test?
[09:50] <zyga> mborzecki: then decides to make a mimic over /snap to avoid showing that on the host
[09:51] <zyga> mborzecki: yes, the one for layout_foo
[09:51] <mborzecki> zyga: ok, let me rerun this with spread
[09:51] <zyga> mborzecki: with --debug please
[09:51] <zyga> mborzecki: but it looks okay and expected-ish
[09:51] <zyga> mborzecki: it depends if the internal namespace has the right directories to begin with
[09:51] <zyga> mborzecki: I suspect we need to allow it to create instance directories
[09:52] <zyga> mborzecki: look at cmd/snap-update-ns/main.go:152 please
[09:52] <zyga> mborzecki: around the call to AddUnrestrictedPrefixes
[09:52] <zyga> mborzecki: I suspect that needs to include the layout variant of that
[09:52] <zyga> what is snapName for instances there?
[09:52] <zyga> is it "test-snapd-layout" or "test-snapd-layout_foo"?
[09:53] <mborzecki> zyga: _foo
[09:53] <mborzecki> test-snapd-layout_foo
[09:55] <zyga> mhm
[09:55] <zyga> interesting
[09:55] <zyga> perhaps we need the instance-less version there as well
[09:55] <zyga> that would explain why it is trying to construct a mimic
[09:55] <zyga> mborzecki: once it fails discard the mount namespace
[09:55] <zyga> mborzecki: and set SNAP_DEBUG=1
[09:55] <zyga> and run test-snapd-shell.sh /bin/true
[09:55] <zyga> or something like that
[09:55] <mborzecki> ack
[09:57] <zyga> thank you!
[09:57] <zyga> I'm preparing the PR for review
[09:57] <zyga> I'll rework comments to explain the restricted mode
[09:57] <zyga> and drop some unused code
[09:59] <mborzecki> uh, we got some meeting
[10:02] <zyga> oh?
[10:02] <zyga> now?
[10:03] <zyga> ah. I see
[10:04] <zyga> the session is full
[10:04] <zyga> :P
[10:04] <zyga> what is that?
[10:04] <zyga> some kind of joke
[10:06] <mborzecki> haha
[10:06] <mborzecki> and it doesn't work in ff
[10:06] <mborzecki> because it's '2010'
[10:06] <zyga> meeting has ended
[10:06] <zyga> what kind of crap is that?
[10:06] <zyga> why do we have to have 2000 different meeting system
[10:07] <zyga> ok
[10:07] <zyga> I'll ignore that
[10:43] <mborzecki> zyga: https://paste.ubuntu.com/p/RdyjBJ9nM7/
[10:43] <zyga> looking
[10:44] <mborzecki> zyga: https://paste.ubuntu.com/p/4MXzzC7Tc4/
[10:46] <zyga> yeah
[10:46] <zyga> we need more logging :()
[10:46] <zyga> we need to log when we decide to make a mimic and log the reason for that
[10:47] <zyga> main.go:196: DEBUG: 	 * mount (/snap/test-snapd-layout/x1/bin-very-weird-place /bin/very-weird-place none rbind,rw,x-snapd.origin=layout 0 0)
[10:47] <zyga> this is exactly what I said before
[10:47] <zyga> it's very interesting
[10:47] <zyga> because we are crating a mimic for /bin/
[10:48] <zyga> (which is expected) but then because /snap/test-snapd-layout is not in the trusted path we go on to create a mimic for /snap
[10:48] <zyga> but this is unexpected and in fact, not allowed by appamor
[10:48] <zyga> so we fail as you saw
[10:48] <zyga> thanks
[10:48] <zyga> this will require a little bit of integration
[11:06] <mvo> still need a second review for 5736
[11:12] <zyga> doing now
[11:14] <zyga> +1
[11:14] <zyga> mvo: approved
[11:17] <mvo> zyga: ta, 5754 is another simple one where it would be great to get a review
[11:21] <thresh> sparkiegeek, so what was it?
[11:22] <sparkiegeek> thresh: I re-triggered the automated review check, which then passed successfully. We've been tweaking timeouts and retry behaviour in the store, and looks like this got caught up in the transition
[11:22] <Gargoyle> Anyone able to help me out with an lxc issue - getting nothing from #lxc or #lxcontainers. Pretty sure it's related to user and group mappings but I just can't get my head round it?
[11:25] <zyga> mvo: that report is pretty old
[11:27] <mvo> zyga: it seems to be still valid though
[11:27] <zyga> yes, I'm worried that it will stay this way
[11:27] <mborzecki> zyga:  it works with this diff now https://paste.ubuntu.com/p/KYVCj2vNZc/
[11:27] <thresh> sparkiegeek, allright, thanks a lot!
[11:27] <mvo> zyga: aha, yes, that is unfortunate
[11:27] <mvo> zyga: we could try to pester sergio about it
[11:27] <zyga> mborzecki: excellent!
[11:27] <zyga> mborzecki: that's very reassuring :)
[11:28] <zyga> mborzecki: I'm almost done documenting new things, I removed all the cruft I found and I'll open a PR shortly
[11:28] <mborzecki> zyga: great, ping me for the review :P
[11:28] <zyga> I will :)
[11:29] <mborzecki> zyga: btw. could you do another pass on https://github.com/snapcore/snapd/pull/5713 ?
[11:29] <mvo> Chipaca: any concerns about 5754? iirc you added this originally
[11:30] <zyga> ouch, yes but it's pretty long so I'll do it in my review part of the day
[11:30] <Chipaca> mvo: looking
[11:30] <mborzecki> zyga: ack, thanks
[11:31] <Chipaca> mvo: snapcraft is using that exact (w/--dirty) command, though
[11:32] <Chipaca> mvo: does snapcraft still remove snapcraft.yaml if it's in snap/snapcraft.yaml?
[11:32] <Chipaca> (yes I can see how that might be inconvenient for us though)
[11:32] <Chipaca> sigh
[11:32] <Chipaca> dunno
[11:33] <Chipaca> mvo: I don't have strong opinions on this;  the command that works out the version might have been committed by me, but the whole core teem collaborated on its details
[11:33] <Chipaca> it's the perfect shed
[11:35] <mvo> Chipaca: thanks, just wanted to double check with you, I remove -dirty for now and will see what needs to be done to get it fixed in snapcraft
[11:35] <mvo> Chipaca: I think snapcraft is running the git describe --dirty either at a different time or in a different checkout :/
[11:36] <mvo> Chipaca: anyway, no worries, just wanted to double check that I don't step on toes or something :)
[11:37] <Chipaca> mvo: i've got 20 of them, step all you want
[11:37]  * Chipaca reveals why his typing is often poor
[11:44] <sil2100> zyga, mvo: I'm awayish today, but I'll get back to you for some dragonboard logs/debugging for the console-conf segfault tomorrow
[11:44] <zyga> ok
[11:46] <Chipaca> hmm, got a meeting at standup time
[11:50] <mborzecki> zyga: pushed everything to bboozzoo/parallel-install-snap-namespace-mapping-with-trespassing-fix branch in my fork
[11:50] <zyga> ok
[11:51] <zyga> note that I will not present the trespassing fix as-is, I'm making it review-friendly now
[11:51] <zyga> I pushed to my branch and the last thing on my todo list is that tmpfs checker code
[11:51] <zyga> you know, the one we changed during the live review
[11:51] <zyga> I think it may still be wrong
[12:16] <pedronis> mvo: hi, have you tried to upload snapd with the snapd type, yet?
[12:16] <mborzecki>  google:opensuse-42.3-64:tests/main/appstream-id failed again
[12:17] <cachio> mborzecki, it is failing in different systems
[12:18] <mborzecki> cachio: heh, must be mu luck then :)
[12:18] <cachio> mborzecki, I also saw some timeouts
[12:18] <mborzecki> pedronis: are you aware of any troubles store side?
[12:19] <pedronis> not atm
[12:19] <cachio> mborzecki, pedronis https://paste.ubuntu.com/p/MkVNvYRb4H/
[12:19] <cachio> I saw some of these
[12:23] <mborzecki> fwiw, searching does not seem to work locally either
[12:24] <mborzecki> wrz 03 14:23:47 galeon snapd[1848]: retry.go:52: DEBUG: The retry loop for https://api.snapcraft.io/v2/snaps/refresh finished after 4 retries, elapsed time=40.002221771s, status: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
[12:24] <mborzecki> it's hitting the retry loop
[12:28] <cachio> mborzecki, I see error no space left on device on amazon linux
[12:29] <Chipaca> mborzecki: store seems to be dying
[12:29] <mborzecki> Chipaca: death by 1000 requests
[12:29] <cachio> mborzecki, it is really weird because it is the only image I didnt update last week
[12:29] <Chipaca> mborzecki: I … hope it's more
[12:29] <Chipaca> but what do I know
[12:29]  * Chipaca goes to see a dog about lunch
[12:31] <mvo> pedronis: not yet, thats a nice idea
[12:31] <mvo> sil2100: thank you
[12:37] <ogra> $ snap find foo
[12:37] <ogra> error: unable to contact snap store
[12:37] <ogra> is the store down ?
[12:38] <ogra> ah, third try gets a response ... probably just a hiccup
[12:39] <ogra> heh ... and there is a forum post about it the second i ask ...
[12:43]  * zyga finishes writing a very long test
[12:43] <zyga> mborzecki: the test for whole thing was missing (unit test)
[12:43] <mborzecki> hm?
[12:44] <Gargoyle> OK. Someone put me out of my misery - how come one is reporting lxd version 3.4 and one is reporting 3.0.1? https://paste.ubuntu.com/p/hjvZSZvRHw/
[12:45] <mborzecki> Gargoyle: can you echo $PATH on both?
[12:49] <Gargoyle> mborzecki: https://paste.ubuntu.com/p/N67TwFTJVy/
[12:49] <ogra> Gargoyle, my guess would be you additionally have the deb installed on the first system
[12:50] <ogra> /snap/bin is only appended to the system PATH, so the deb would take precedence
[12:50] <mborzecki> Gargoyle: or what ogra wrote ^^
[12:50] <Gargoyle> Awww nuts... Good spot
[12:51] <Gargoyle> must have sneaked in before a change was made to ansible scripts. :/
[12:58] <zyga> mborzecki: https://github.com/zyga/snapd/blob/fix/trespassing-v2/cmd/snap-update-ns/change_test.go#L1795
[12:58] <pedronis> mborzecki: cachio:  yes, store issues,  https://forum.snapcraft.io/t/problem-request-failures-to-the-store/7177
[12:58] <zyga> tadam :)
[12:59] <zyga> mborzecki: question wrt pushing this
[12:59] <zyga> mborzecki: one big or split?
[12:59] <zyga> oh
[12:59] <zyga> standup!
[13:00] <Gargoyle> and now I can't re-install due to ^^^
[13:00] <Gargoyle> Time for a brew! :D
[13:04] <Raboo> Hi, does ubuntu core base images include tools for connecting to wireless networks? Or do you need a device with ethernet to download the wireless tools?
[13:06] <zyga> Chipaca: hello
[13:06] <zyga> standup?
[13:07] <Chipaca> zyga: mvo: i've got a conflicting meeting
[13:07] <Chipaca> zyga: mvo: uk travel provider thing
[13:07] <zyga> thanks!
[13:10] <mvo> Chipaca: ok, enjoy, thanks
[13:11] <Chipaca> enjoyment was not in the cards
[13:14] <ogra> it comes with the process
[13:19] <tomwardill> hello! Just to say the store team are aware of some problems with long and failing requests, and we're looking at it, updates will be here: https://forum.snapcraft.io/t/problem-request-failures-to-the-store/7177 when we have them
[13:28] <thresh> (that probably explains why snap info is slow, thanks!)
[13:32] <Chipaca> Gargoyle: sudo snap info /var/lib/snapd/cache/*  -> maybe you still have the .snap locally
[13:33] <Chipaca> Gargoyle: actually you might need to work a bit harder than that because the * won't expand
[13:33] <Chipaca> Gargoyle: sudo find /var/lib/snapd/cache -type f -print0 | xargs -0 sudo snap info
[13:51] <zyga> Brb, just a quick walk and lunch
[13:53] <niemeyer> Will need to step out to run an errand.. will be back later today.
[14:07] <didrocks> hey! I'm having snapcraft issues under CI (I guess something impacting the docker image). It seems to have started on Friday: https://travis-ci.org/ubuntu/yaru/builds
[14:07] <didrocks> for instance: https://travis-ci.org/ubuntu/yaru/builds/423938949
[14:08] <didrocks> (running "snapcraft" on the project works fine on up to date cosmic)
[14:09] <popey> diddledan: is that building using snapcraft from upstream git? Looks like it is
[14:09] <mvo> didrocks: i have the same issue with the "josm" snap it seems
[14:09] <diddledan> ello
[14:09] <popey> s/diddledan/didrocks/
[14:09] <didrocks> it's using whatever the snapcraft upstream docker image is pointing at :)
[14:09] <diddledan> didrocks: change your nick, foo! :-p
[14:10] <diddledan> I demand priority
[14:10] <didrocks> diddledan: I'm having it since 1998 ;)
[14:10] <diddledan> bah
[14:10] <popey> :D
[14:10] <didrocks> like an good old wine :p
[14:10] <diddledan> precedent, shmecedent!
[14:11] <didrocks> ;)
[14:11] <popey> have poked ev, as the snapcraft guys are on vacation today.
[14:11] <diddledan> _all_ the snapcraft guys?!
[14:11] <didrocks> thx!
[14:12] <popey> yes, they're on a beach somewhere drinking mohitos
[14:12] <popey> or something
[14:12] <diddledan> bass turds!
[14:12] <diddledan> (poo from a fish!)
[14:12]  * Chipaca expects a plugin: mojito
[14:12] <popey> hah
[14:12] <popey> getting flashbacks to seattle
[14:12] <diddledan> haha
[14:14] <diddledan> what happens in seattle stays unsaid. except Wimpress's blocked credit cards
[14:16] <diddledan> https://youtu.be/zcqxCeYkkhk?t=7
[14:23] <mvo> fwiw, 5606 needs a second review
[14:24] <mvo> (I mean, it technically has two but it changed quite a bit since the initial review from Chipaca)
[14:27] <Chipaca> mvo: looking
[14:28] <zyga> re
[14:28] <Chipaca> mvo: pedronis should probably confirm his concerns were addressed
[14:28] <Chipaca> mvo: i can then re-review if he doesn't have time to do a full pass
[14:29] <mvo> Chipaca: thanks, sounds reasonable
[14:30] <Chipaca> pedronis: does this mean you're re-reviewing, or leaving the road open for me to do so?
[14:30] <pedronis> I'm leaving the road open
[14:30] <pedronis> my original review was mostly, don't abuse context
[14:30] <Chipaca> ok
[14:31] <Chipaca> pedronis: it's the way context dresses
[14:31]  * Chipaca runs as far away as he can
[14:31] <pedronis> Chipaca: bad John, bad John
[15:16] <tomwardill> Hi, the store should be operational again, let us know if you have any other (relevant) problems :)
[15:29] <zyga> thank you tomwardill :)
[15:29] <zyga> what was the issue?
[15:30] <tomwardill> we're not entirely sure, something triggered a bit of a death spiral, then the retry built up
[15:30] <tomwardill> looking for the cause now
[15:30] <tomwardill> *retry traffic
[15:30] <popey> "death spiral" always a catchy turn of phrase, that :)
[15:34] <Gargoyle> I'm trying to re-install lxd snap (after removing old apt version). But I have lxd.service, lxd.socket and lxd-container.service in /etc/systemd/system which are all symlinked to /dev/null. What's the best way to fix this?
[15:35]  * cachio lunch
[15:35] <Gargoyle> That is, I am assuming that is why service lxd start/restart just returns an error about it being masked.
[15:36] <MattJ> er, I had issues with lxd recently too and discovered the same thing... but I think it's normal
[15:37] <MattJ> I think the snap one might be called snap.lxd or something
[15:39] <MattJ> Yeah, 'snap services' lists lxd.daemon, and I have a snap.lxd.daemon service in systemctl
[15:39] <Chipaca> Gargoyle: the ones in lxd will have different names
[15:39] <Chipaca> Gargoyle: snap.<snap name>.<app name>.service iirc
[15:40] <Chipaca> Gargoyle: snap.lxd.daemon.service, in this case
[15:40] <Chipaca> MattJ: that :-)
[15:40] <Chipaca> Gargoyle: however, 'service lxd' is not the thing to manipulate snap services
[15:41] <Chipaca> Gargoyle: 'snap start/stop/restart/logs' are snap commands to manipulate services that are snapped
[15:41] <Chipaca> and 'snap services', heh
[15:42] <Chipaca> in all of them, you can use a snap name to ask for everything in a snap, or add a service name to ask about just that one
[15:43] <Gargoyle> OK. So possibly still got some "old apt" / snap version mix-ups then. Now getting - Error: Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: connection refused
[15:44] <Gargoyle> I assumed this was because lxd wasn't running.
[15:45]  * Chipaca takes a break
[15:46] <thresh> sparkiegeek, it seems it's the same issue again with vlc #555
[15:46] <Chipaca> Gargoyle: _what_ prints that error?
[15:47] <Gargoyle> lxc list
[15:51] <Chipaca> Gargoyle: and what's "which lxc"?
[15:52] <Gargoyle> hmm. /usr/bin/lxc
[15:52] <Chipaca> Gargoyle: yeah
[15:52] <Gargoyle> I'm just going to take this AWS instance out back and shoot it in the head!
[15:52] <Chipaca> Gargoyle: lxc and lxd might come from different debs
[15:53] <Gargoyle> nvm. I'll rebuild a clean node tomorrow without the snap/apt conflicting version.
[16:03] <abeato> mvo, hey, I have noticed that there are a few very basic utils that are not included in core18: vi, ping... are those going to be add back?
[16:09] <mvo> abeato: we can add things back on a case-by-case basis, iirc edge has vim-tiny already
[16:11] <ogra> mvo, ping is definitely essential ... especially since you cant snap it (it is suid)
[16:12] <ogra> mvo, if you need to make room, drop bash !!! ;)
[16:12] <mvo> ogra: ok, let chat tomorrow, I need to run now but thats easy enough
[16:12] <ogra> mvo, perhaps a forum thread would be good to collect a list
[16:13] <ogra> (i'm sure there will be more and adding it throughout the cycle would be hit and miss for users in the end)
[16:20] <ogra> ppisati, on my pi3 systems the wlan hangs quite frequently in recent times (i sadly dont know when it started) it seems to be dying with "brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012"
[16:21] <ogra> ppisati, i found https://github.com/raspberrypi/linux/issues/1342 and https://github.com/raspberrypi/linux/issues/2453#issuecomment-396063259 upstream ... bth seemingly unsolved though :(
[16:22] <ogra> (it hung three times today and 5 times yesterday ... to give you a figure)
[16:34] <mborzecki> pedronis: finally opened a PR with common snap directories for install/remove of instance-keyed snaps https://github.com/snapcore/snapd/pull/5758 iirc i had a spread test to check if dirs are created, i'll try to dig it up and push it there as well (but that's for tomorrow)
[17:02] <zyga> hrm!
[17:04] <zyga> I may have found and edge case to an edge case
[17:04]  * zyga runs hacked spread test to examine
[17:09]  * Chipaca EODs
[17:20]  * zyga found interesting things
[17:20] <diddledan> snapd folks; question here about running postgresql which doesn't like to run as root; I said I'd get one of ya'll to pop in and comment on the possibility of running the daemon under a non-root account: https://forum.snapcraft.io/t/snapping-a-rails-app/7179/2
[17:29] <Chipaca> diddledan: https://forum.snapcraft.io/t/multiple-users-and-groups-in-snaps/1461/3?u=chipaca probably?
[17:39] <diddledan> thanks Chipaca . I've posted the link on the rails thread
[17:39] <Chipaca> diddledan: I don't know that status of that though :-)
[17:39] <Chipaca> also, I don't know what i'm doing here post-eod
[17:39] <diddledan> looks like it's not ready yet
[17:39] <Chipaca> procrastinating from home chores i'm sure
[17:59] <Son_Goku> zyga, how are we going to deal with the lack of extrausers in Fedora?
[17:59] <Son_Goku> it's not like there's a port of this functionality using sssd?
[18:00] <zyga> not sure, is it relevant?
[18:00] <Son_Goku> from what I can tell, it's kinda needed for supporting system users in snaps?
[18:00] <Son_Goku> for services and such
[18:00] <zyga> I'm not sure that's the case
[18:01] <zyga> in any case we don't have support for additional users yet
[18:01] <Son_Goku> oh okay
[18:39] <Gargoyle> aggghhhh... deb version of lxd/lxc is installed in the AWS default 18.04 image!
[18:39] <Gargoyle> That explains a lot. How can I find all it's packages and completely purge them so as not to interfere with the snap verison?
[18:50]  * zyga considers taking a bike
[18:51] <zyga> or
[18:51] <zyga> watching archer and having supper
[18:51] <zyga> or figuring out clashing symlinks
[19:19]  * Gargoyle does a little dance  \o/   \\o  o//  
[19:20] <Gargoyle> Containers launch properly using the snap version!
[19:33] <Gargoyle> Now I just need to figure out why when the script is run by the team-city agent, it doesn't think lxc is installed.