[03:43] <PhoenixMage> When you're running a snap build on launchpad and the source website goes down after 40 min
[06:53] <zyga-suse> good morning
[06:53] <zyga-suse> mvo: around? :-)
[06:53] <mvo> hey zyga-suse - good morning
[06:54] <zyga-suse> mvo: welcome back, how were your holidays?
[06:54] <mvo> zyga-suse: very nice, thank you!
[06:54] <zyga-suse> mvo: we have some odd failures in xenial-proposed
[06:54] <mvo> zyga-suse: how are things here?
[06:54] <zyga-suse> mvo: I'll be right back, let me just get some coffee
[06:55] <mvo> zyga-suse: sure
[06:55] <zyga-suse> mvo: lots of things in flight :)
[06:55] <zyga-suse> mvo: I'll tell you in a moment
[06:55] <mvo> zyga-suse: do you have links for me with the failures?
[06:55] <mvo> zyga-suse: ok
[06:55] <mvo> zyga-suse: get your coffee :)
[07:02] <zyga-ubuntu> mvo: http://people.canonical.com/~ubuntu-archive/pending-sru.html
[07:02] <zyga-ubuntu> oh, looks better than last week
[07:03] <zyga-ubuntu> there were armfh failures and a few others
[07:03] <zyga-ubuntu> but now I see
[07:03] <zyga-ubuntu>  Missing build dependencies: libseccomp-dev (>= 2.1.1-1ubuntu1~trusty4)
[07:03] <zyga-ubuntu> mvo: we also have https://bugs.launchpad.net/snappy/+bug/1707474
[07:04] <zyga-ubuntu> and this one affects everyone, not just ubuntu
[07:04] <zyga-ubuntu> mvo: I wanted to try out a simple fix
[07:04] <zyga-ubuntu> + we have a tonne of reviews to do
[07:05] <zyga-ubuntu> mvo: is 2.27 tagged yet?
[07:06] <mvo> zyga-ubuntu: yeah, the build issue in xfsprogs is annoying
[07:06] <zyga-ubuntu> mvo: I wanted to cherry pick a few fixes for arch (and probably one more for everyone on 32 bit systems)
[07:09] <zyga-ubuntu> mvo: I also found a reliable way to show that reexec is just broken in debian
[07:09] <zyga-ubuntu> mvo: there's a spread reproducing this (but I cannot merge it because it breaks regular tests for unrelated reason)
[07:09] <zyga-ubuntu> mvo: so one thing I would consider adding to to 2.27 fixup pipe
[07:10] <zyga-ubuntu> mvo: so all in all, it looks like a busy monday
[07:13] <zyga-ubuntu> pstolowski: good morning
[07:13] <pstolowski> zyga-ubuntu, hey!
[07:16] <mvo> zyga-ubuntu: indeed, meh
[07:17] <mvo> zyga-ubuntu: thanks for the update! looking at the spread tests issues now
[07:18] <pstolowski> hi mvo!
[07:19] <zyga-ubuntu> mvo: https://github.com/snapcore/snapd/pull/3635 that's the one I meant
[07:19] <mvo> zyga-ubuntu: great, looking
[07:20] <zyga-ubuntu> mvo: so your hunch about installing core along with the 1st snap was right
[07:20] <mvo> zyga-ubuntu: just looking at the test, nice, thank you! the interessting question is if there is anything we can do :/
[07:25] <mvo> zyga-ubuntu: the pending sru looks tame unless I miss something? the dependency-wait for ppc64/arm/ppc is harmless, we have the same for 2.25 etc, trusty is special here
[07:25] <zyga-suse> mvo: the pending SRU looks good, last week it was a bunch of test failures, maybe they got re-triggered
[07:25] <mvo> zyga-suse: probably
[07:25] <zyga-suse> mvo: I talked to apw about them before and he re-triggered them once again because of internal connectivity errors in launchpad
[07:26] <mvo> zyga-suse: did you had a chance to look at the failure in debian yet? if core is implicitely downloaded?
[07:26] <mvo> zyga-suse: thank you
[07:26] <zyga-suse> yes, I did, core is downloaded implicitly
[07:26] <zyga-suse> mvo: then things break on the configure hook
[07:26] <zyga-suse> mvo: I was pondering disabling that for now
[07:26] <zyga-suse> mvo: to buy us time for 2.28 to land the configure hook with http proxy config option
[07:26] <mvo> zyga-suse: did we restart into the new snapd at this point?
[07:27] <zyga-suse> mvo: not sure, I spent most of last week on lots of little tasks
[07:27] <zyga-suse> mvo: just get that PR and fire it up in linode (edit workers)
[07:27] <zyga-suse> mvo: it's more reliable than my memory at this stage
[07:27] <mvo> zyga-suse: sure, thank you
[07:27] <zyga-suse> mvo, mwhudson: looked at updating debian but we have two forks to adjust
[07:27] <mvo> zyga-suse: indeed
[07:27] <zyga-suse> mvo: and it's unclear if we want to package those forks in debian or wait for them to merge
[07:27] <mwhudson> hi hi
[07:28] <zyga-suse> hey hey :)
[07:28] <mwhudson> i think we could probably make a case for continuing to bundle the secomp stuff, that's pretty special and specific to snappy, right?
[07:28] <ashwind> Looking for a build for https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/bluez/commit/?h=bluez/5.44
[07:29] <pstolowski> 2nd review needed for trivial #3659 and #3661 (note, the latter is against 2.27)
[07:29] <zyga-suse> ashwind: I think morphis knows about those
[07:29] <mvo> mwhudson: it is, I will look at the details though. iirc all changes to seccomp-golang are to build on trusty, if that is not needed, the upstream source can be used
[07:29] <mwhudson> mvo: oh ok
[07:30] <mwhudson> we're only targetting stretch at a well, stretch
[07:30] <mwhudson> so perhaps this problem can be fixed with sed :)
[07:30] <morphis> ashwind: that version of bluez is available on the store
[07:30] <zyga-ubuntu> pstolowski: that latter one has tests failing
[07:30] <mvo> mwhudson: the x/net/ stuff is only for tests, I will push my stuff upstream, but the code review process is a bit of a PITA to setup, I had issues with getting an account on their gerrit
[07:30] <mwhudson> mvo: might it make sense for me to push it to get started?
[07:31] <morphis> ashwind: at minimum it should be able in the edge channel
[07:31] <mvo> mwhudson: I may actually just kill x/net in favour of kernel based tests.
[07:31] <mwhudson> mvo: ok
[07:31] <mvo> mwhudson: aha, indeed, that would be nice, I will dig out my diff
[07:32] <pstolowski> zyga-ubuntu, yes i know,but it's completely unrelated to the change
[07:34] <zyga-ubuntu> pstolowski: restarted tests
[07:34] <ashwind> thx
[07:35] <pstolowski> zyga-ubuntu, thanks
[07:49] <mvo> pstolowski: good morning to you as well, sorry, overlooked your message earlier :)
[07:49] <mvo> pstolowski: 3661 has an interessting failure that might be worth exploring
[07:52] <mvo> zyga-suse: is 3649 something that needs further work? it got two +1 now and I wonder if I can merge it
[07:56]  * zyga-suse looks
[07:57] <zyga-suse> mvo: it is good, I will update it to drop the patches once they land
[07:57] <zyga-suse> mvo: let's land it now thought
[07:57] <zyga-suse> *though
[08:03] <morphis> ogra_: was there any change in config.txt necessary to get BT working with Ubuntu Core on the pi?
[08:09] <morphis> zyga-suse: you still owe me another review-round from last week :-)
[08:09] <zyga-suse> indeed, reviews will be 90% of my day
[08:09]  * zyga-suse eats breakfast now
[08:09] <zyga-suse> stress is eating me alive here, darn government forms that don't work
[08:13] <pstolowski> mvo, ah indeed, i didn't check all logs and missed that one. the failures I saw were about upgrade/basic
[08:30] <pstolowski> aha, it is upgrade/basic failing because of unregistered hook. looking
[08:31] <pstolowski> zyga-ubuntu, having fun with registering your company?
[08:32] <zyga-suse> pstolowski: yes, ZUS ZUA form is silly
[08:32] <pstolowski> hehe
[08:32] <zyga-suse> just resolved it by talking to a consulant
[08:32] <zyga-suse> you can either select mandatory thing or optional thing
[08:32] <zyga-suse> but the wording is confusing so it seems you have to check both boxes
[08:32] <zyga-suse> and the error message given is utterly confusing
[08:33] <zyga-suse> pstolowski: that's *the* bug I was talking about earlier
[08:33] <pstolowski> fill it on paper. no errors ;)
[08:33] <zyga-suse> right...
[08:33] <zyga-suse> if only that was true
[08:33] <zyga-suse> that form is the equivalent of the paper form
[08:33] <zyga-suse> but you don't have to type it over and over this way
[08:34] <zyga-suse> (and I hate handwriting in forms)
[08:37] <zyga-ubuntu> darn, now I have to sign it myself
[08:46] <pstolowski> mvo, how can I run autopkgtests locally?
[08:46] <pstolowski> just building the debs is enough?
[08:48] <mvo> pstolowski: you need to install autopkgtest (the deb) - then run adt-buildvm-ubuntu-cloud to generate a test env, then run "autopkgtest . -- qemu ./path/to/the/just/created/vm"
[08:48] <mvo> pstolowski: if you are on xenial you may need the autopkgtest from xenial-backports
[08:48] <pstolowski> mvo, ack, thanks!
[08:51] <mvo> pstolowski: during the execution of the tests for the 2.27 release there was one error in https://paste.ubuntu.com/25190576/  on i386 line 579: "+ echo 'Remove hook was executed. It shouldn'\''t.'" - does that ring a bell?
[08:52] <pstolowski> mvo, these PRs I linked above fix exactly that
[08:53] <mvo> pstolowski: aha, excellent
[08:53] <mvo> pstolowski: 3661 is the one?
[08:53] <mvo> pstolowski: or a different one?
[08:53] <pstolowski> mvo, yes 3661 is for 2.27. 3559 is for master
[08:54] <mvo> pstolowski: cool, thank you
[08:55] <mvo> pstolowski: this is good to go I think then, would be nice to figure out why the upgrade/basic is failing and if that is something to worry about. I will still merge the PR as the other failure is unrelated
[08:56] <pstolowski> mvo, yes I'm investigating (need to repro first)
[08:56] <mvo> pstolowski: sure :) thank you. no pressure, just wanted to put it on your radar
[09:04] <morphis> ashwind: I just got the confirmation from ogra_ that /lib/firmware/BCM43430A1.hcd exists
[09:04] <morphis> ashwind: which core image did you take and which version of kernel/gadget snap for the pi are you using?
[09:09] <ogra_> ashwind, try an image from either http://people.canonical.com/~ogra/snappy/all-snaps/daily/ or http://cdimage.ubuntu.com/ubuntu-core/16/edge/
[09:10] <morphis> ogra_: thanks
[09:13] <morphis> ogra_: using the edge or daily images should give you at least the patch files in /lib/firmware
[09:13] <morphis> when you install bluez in devmode then you should be able to load the patchram file with hciattach
[09:16] <morphis> ashwind: so what ogra_ and I suggest now is that you use one of the daily/edge images we produce for the pi 2/3
[09:16] <morphis> that should have all necessary firmware bits in /lib/firmware
[09:17] <morphis> the ones with a stable kernel/gadget snap does not because there are problems with updating certain things in /boot with newer snaps and unless that is fixed we can't move any of the snaps in edge/beta/candidate to stable
[09:17] <ashwind> sure let me try that
[09:23]  * zyga-suse fills in VAT-R :/
[09:30] <ogra_> ashwind, see https://bugs.launchpad.net/snappy/+bug/1674509/comments/30 (you dont need the first line)
[09:37] <zyga-suse> ok, I need to go out to get those documents signed
[09:37] <zyga-suse> mvo: I'll be working outdoors today, just mainly doing code reviews
[09:37] <zyga-suse> mvo: can you please assign me to specific PRs
[09:37] <zyga-suse> mvo: I will focus on those if you do
[09:37] <mvo> zyga-suse: sure - 3664 should be a trivial one
[09:37]  * zyga-suse starts
[09:38] <mvo> zyga-suse: also #53 on snapcore/core
[09:42] <zyga-suse> mvo: both done
[09:42] <mvo> zyga-suse: thank you
[09:42] <zyga-suse> mvo: can we do a 2.27.1 after 2.27 is out, I would like that to be in opensuse/arch/fedora as it contains fixes for various non-default locations
[09:43] <zyga-suse> mvo: and perhaps we can, by then, fix the debian bug too
[09:44] <mvo> zyga-suse: there are some test failures still, it looks like we need ~rc5, I'm going over them right now. it appears its all tests so far, no real issues with the code but I'm still in the middle of it
[09:44] <zyga-suse> rc5 is ...?
[09:44] <zyga-suse> for 2.27?
[09:44] <mvo> zyga-suse: yes, sorry. we are currently at 2.27~rc4 and have some test failures
[09:45] <zyga-suse> ah, I see
[09:45] <zyga-suse> will you use the release branch or master for rc5?
[09:45] <mvo> zyga-suse: relese branch, 2.27 was forked some days ago
[09:46] <zyga-suse> ok, shall I target my fixes there then?
[09:46] <mvo> zyga-suse: ideally, if they are small we can also cherry pick them
[09:46] <zyga-suse> yes, each fix is one patch, easy to cherry
[09:46] <zyga-suse> if you prefer I can give you hash IDs
[09:49] <mvo> zyga-suse: thats fine, just target the PR with 2.27
[09:49] <zyga-suse> sure
[09:55] <zyga-suse> mvo: done
[09:55] <zyga-suse> mvo: there's one more but it didn't land in master yet (that is #3648)
[09:57] <pstolowski> mvo, pardon my ignorance, i've never run autopkg tests manually before... there is no autpkgtest test command, only adt-run with many variants to choose from. how to properly use it with our source tree?
[09:59] <zyga-ubuntu> ondra: hey, trivial comment on https://github.com/snapcore/snapd/pull/3624
[10:02] <mvo> pstolowski: please try to install autopkgtest from xenial-backports, sudo apt install -t xenial-backports autopkgtest
[10:03] <mvo> pstolowski: iirc the version in xenial was a bit more complicated and the test env uses the new autopkgtest stuff anyway
[10:03] <pstolowski> mvo, ah, right, I forgot that backports repo needs to be forced
[10:03] <zyga-suse> the one in xenial doesn't work
[10:04] <zyga-suse> you need backports, period
[10:04] <mvo> pstolowski: good luck, adt is a bit "special" (but it got much better with the version in -backports)
[10:07] <pstolowski> mvo, this seems to be working, tests were started, thanks
[10:10] <pstolowski> I spoko too soon.. it failed on build
[10:10] <mvo> pstolowski: it will take some time. for future runs the "-U" option may be useful, it will ensure that the debs are up-to-date (no need for this run as you just created the image so its fresh). and "-s" which will give you a shell to login and investigate
[10:10] <mvo> pstolowski: oh, it failed in what way?
[10:10] <ondra> zyga-suse updated now
[10:11] <ondra> zyga-suse and installing plugin for my editor :)
[10:11] <pstolowski> mvo, a number of tests passed, and then http://pastebin.ubuntu.com/25262220/
[10:15] <mvo> pstolowski: could you please paste a bit more?
[10:15] <mvo> pstolowski: maybe the entire log
[10:16] <pstolowski> sure, let me try again
[10:18] <zyga-suse> ondra: cool
[10:18] <zyga-suse> thank you
[10:21] <pedronis> mvo: hi, this is done now, right:  https://forum.snapcraft.io/t/channels-2-0-implementation/156 ?
[10:22] <pstolowski> mvo, http://pastebin.ubuntu.com/25262279/
[10:22] <mvo> pstolowski: yes, the channels 2.0 stuff should be sorted
[10:23] <mvo> pstolowski: hm, mysterious "FAIL: cmd_interfaces_test.go:34: SnapSuite.TestInterfacesHelp" fails (see line 2449
[10:24] <zyga-ubu1tu> mvo: that is because outdated vendor.json
[10:24] <zyga-ubuntu> mvo: after specific go-flags update the help output format has changed
[10:24] <mvo> pstolowski: aha, so run ./get-deps I guess
[10:24] <mvo> zyga-ubuntu: ta!
[10:24] <zyga-ubuntu> indeed
[10:24] <pstolowski> hmm
[10:24]  * zyga-ubuntu is on the way to register VAT, ZUS and import the car into poland
[10:24] <zyga-ubuntu> so.... well
[10:25] <zyga-ubuntu> I'm online and my wife will help with all the paperwork but always "fun"
[10:26] <pstolowski> zyga-ubuntu, more fun awaiting when you declare taxes for this year early next year ;)
[10:27] <zyga-ubuntu> pstolowski: you mean JPK?
[10:27] <pstolowski> zyga-ubuntu, no. just declaring earnings from abroad, exchange rate conversion etc
[10:27] <zyga-ubuntu> is it a trait to be able to expand any three letter acronym into curse words?
[10:28] <zyga-ubuntu> pstolowski: I don't have to
[10:28] <zyga-ubuntu> pstolowski: my yearly stuff is going to be in spain
[10:28] <zyga-ubuntu> pstolowski: so I'll just have to declare that
[10:28] <pstolowski> zyga-ubuntu, ah ok, good
[10:28] <zyga-ubuntu> pstolowski: I'm not a resident this year
[10:28] <pstolowski> right
[10:28] <zyga-ubuntu> pstolowski: but next year each micro company needs to file JPK
[10:28] <zyga-ubuntu> (jednolity plik kontroli)
[10:29] <pstolowski> zyga-ubuntu, that should be no brainer with any of the online accounting services I told you about
[10:29] <zyga-ubuntu> pstolowski: I'm doing that on paper
[10:29] <zyga-ubuntu> pstolowski: then I think I don't need it
[10:30] <zyga-ubuntu> pstolowski: JPK is needed when you use software for taxes
[10:32] <zyga-ubuntu> mvo: should I expect this in 2.27?
[10:32] <zyga-ubuntu> - Setup snap "test-snapd-tools" (6) security profiles (cannot update mount namespace of snap "test-snapd-tools": cannot update preserved namespace of snap "test-snapd-tools": fork/exec /usr/lib/snapd/snap-update-ns: no such file or director
[10:32] <zyga-ubuntu> https://travis-ci.org/snapcore/snapd/builds/261760429?utm_source=github_status&utm_medium=notification
[10:39] <mvo> zyga-ubuntu: hm, where do you get this error?
[10:40] <zyga-ubuntu> mvo: on the linked PR
[10:40] <zyga-ubuntu> mvo: this is one of the backport branches
[10:40] <zyga-ubuntu> https://github.com/snapcore/snapd/pull/3666
[10:44]  * ogra_ grins ... i wonder if "Jahyahp8nei1noowohvo" in the forum was aware that he shouldnt use his password as username :P
[10:44] <zyga-ubuntu> Chipaca: I'm looking at the services PR now, would you like to look at https://github.com/snapcore/snapd/pull/3636?
[10:44] <zyga-ubuntu> morphis: and your userd PR is next
[10:45] <Chipaca> zyga-ubuntu: in a bit (got some context in-head rn)
[10:45] <mvo> zyga-ubuntu: the failure you see is interessting, I will try to reproduce
[10:46] <zyga-ubuntu> mvo: I'd like to squash merge this: https://github.com/snapcore/snapd/pull/3622
[10:46] <zyga-ubuntu> ok
[10:46] <zyga-ubuntu> Chipaca: no worries, this is not in a rush o
[10:46] <zyga-ubuntu> or anything :)
[10:46] <zyga-ubuntu> mvo: that looks like what we were fighting all 2.24.x with
[10:46] <zyga-ubuntu> mvo: uses distro package but there is no snap-update-ns there? (odd)
[10:46] <mvo> zyga-ubuntu: fine with the squash merge
[10:47] <zyga-ubuntu> mvo: is that snapd-after-reexec doing stuff on reverted core?
[10:50] <mvo> zyga-ubuntu: I think its something else, let me dig deeper
[10:54] <mvo> zyga-ubuntu: I think it is 3671 - but I wonder why this is not part of 2.27, I remember we worked on this
[10:55] <ashwind> morphis ogra_: worked as expected with the latest from http://cdimage.ubuntu.com/ubuntu-core/16/edge/ thanks
[10:56]  * zyga-ubuntu looks
[10:57] <zyga-ubuntu> mvo: not in 2.27
[10:57] <ogra_> ashwind, note that this uses all snaps from edge ... (but is the only way to get the latest gadget snap on the pi) ... you might want to "snap refresh core --stable" and ""snap refresh pi2-kernel --beta" so you arent on edge with everything (do not use the --stable pi2-kernel though, that wont have everything you need)
[10:57] <zyga-ubuntu> mvo: suggestion: merge 2.26.14 into release/2.27
[10:57] <zyga-ubuntu> it would be odd if 2.27 regressed on fixes from point releases of 2.26
[10:58] <Chipaca> zyga-ubuntu: do you have an example of how the 'contents' arg of snaptest.MockSnap is meant to be used?
[10:59] <zyga-ubuntu> Chipaca: let me look
[10:59]  * zyga-ubuntu doens't recall MockSnap
[10:59] <zyga-ubuntu> just MockInfo
[10:59] <Chipaca> zyga-ubuntu: blame says its yours, only reason i'm asking you :-)
[10:59] <Chipaca> it's*
[11:00] <zyga-ubuntu> aha
[11:00] <zyga-ubuntu> it looks like a path to a squashfs file
[11:00] <zyga-ubuntu> er
[11:00] <mvo> zyga-ubuntu: indeed, just double checked, it looks like its the only missing commit
[11:00] <zyga-ubuntu> not path
[11:00] <zyga-ubuntu> *the* file
[11:00] <ashwind> ogra_: Sounds good I'll make the changes.
[11:00] <zyga-ubuntu> mvo: great catch!
[11:00] <zyga-ubuntu> Chipaca: grepping
[11:01] <mvo> zyga-ubuntu: review for 3671 would be great :)
[11:01] <mvo> (super trivial)
[11:01] <zyga-ubuntu> Chipaca: seems like we pass an empty string there
[11:02] <zyga-ubuntu> done
[11:02] <zyga-ubuntu> Chipaca: I really don't get it
[11:02] <Chipaca> mvo: "will unsetenv the for"?
[11:02] <zyga-ubuntu> why not MockInfo then?
[11:02] <zyga-ubuntu> $SNAP :D
[11:02] <Chipaca> zyga-ubuntu: it seems to expect the _contents_ of a squashfs
[11:03] <zyga-ubuntu> Chipaca: exactly
[11:03] <Chipaca> oh wait
[11:03] <Chipaca> zyga-ubuntu: sorry, it looks like the bit that writes that out is from robert ancell
[11:04] <Chipaca> zyga-ubuntu: nm then, ty!
[11:04] <mvo> Chipaca: indeed, the docstring is slightly bad, I fix that in master
[11:04] <Chipaca> k
[11:05] <zyga-ubuntu> mvo: interesting how all my backport/ branches now fail
[11:07] <zyga-ubuntu> pstolowski: - Run install hook of "core" snap if present (internal error: no registered handlers for hook "install")
[11:07] <zyga-ubuntu> pstolowski: in https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-image/xenial/ppc64el/s/snapd/20170807_105544_ad619@/log.gz
[11:07] <zyga-ubuntu> pstolowski: do you want to collect that log?
[11:07] <mvo> zyga-ubuntu: please merge release/2.27 - that should have some fixes
[11:07] <zyga-ubuntu> mvo: ^^ I strongly feel that this is something we must fix for rc5
[11:07] <zyga-ubuntu> OK
[11:08] <mvo> zyga-ubuntu: the above one is still under investigation, I saw this this morning as well
[11:08] <zyga-ubuntu> mvo: I've been seing it for a few weeks
[11:08] <zyga-ubuntu> seeing*
[11:08] <mvo> zyga-ubuntu: ok, then definitely something we need to tackle for 2.27
[11:08] <mvo> zyga-ubuntu: but pstolowski is aware of it and investigates (context see above)
[11:09] <zyga-ubuntu> that's all we need
[11:09] <pstolowski> zyga-ubuntu, yep, as mvo says, that's the same error we discussed earlier today
[11:11] <zyga-ubuntu> janisozaur1: https://github.com/snapcore/snapd/pull/3673
[11:12] <zyga-ubuntu> janisozaur1: I'm away from my Arch system, can you please try that?
[11:13] <zyga-ubuntu> mvo: I'm still seeing lots of failures on the avahi-observe test on debian, I wonder if we are missing anything from master for that
[11:13] <zyga-ubuntu> let me check
[11:13] <zyga-ubuntu> ah
[11:13] <zyga-ubuntu> indeed!
[11:16]  * Chipaca ~> lunch (including lunch-time run)
[11:16] <zyga-ubuntu> mvo: https://github.com/snapcore/snapd/pull/3674
[11:17] <zyga-ubuntu> mvo: specifically this was missing: https://github.com/snapcore/snapd/pull/3674/files#diff-77cd38482da5f11c05ccdcfa24f61aea
[11:17] <zyga-ubuntu> mvo: but I suspect we also want other parts of that commit
[11:17] <zyga-ubuntu> ah, after merging release/2.27 those are just tests
[11:25]  * Chipaca now really off
[11:48]  * zyga-ubuntu arrives at the tax agency
[11:48] <zyga-ubuntu> ttyl
[11:56] <popey> Can someone take a moment to answer this query on stackoverflow please https://stackoverflow.com/questions/45513913/snapcraft-create-key-taking-forever-to-complete
[12:03] <niemeyer> Good mornings!
[12:04] <mvo> zyga-suse: nice catch
[12:04] <mvo> hey niemeyer, good morning!
[12:04] <niemeyer> mvo: Heya! Welcome back!
[12:17]  * zyga-ubuntu needs proof that he is not in spain
[12:17] <zyga-ubuntu> legal logic
[12:21] <niemeyer> zyga-ubuntu: :)
[12:21] <Son_Goku> mvo: morning!
[12:21] <niemeyer> zyga-ubuntu: Oh, you're actually serious?
[12:21] <mvo> Son_Goku: hello hello
[12:21] <niemeyer> Son_Goku: Heya
[12:22] <zyga-ubuntu> niemeyer: haha, yes :(
[12:22] <niemeyer> zyga-ubuntu: Okay, so I think somebody *else* needs proof that you're not in Spain :P
[12:22] <zyga-ubuntu> niemeyer: but not too terrible, 1/3 paperwork done
[12:22] <niemeyer> zyga-ubuntu: I thought you had woken up in a Spain mood ;)
[12:22] <zyga-ubuntu> niemeyer: solving one the next 1/3
[12:23] <zyga-ubuntu> niemeyer: haha, no that would be nifty but not terrible :)
[12:23] <zyga-ubuntu> niemeyer: driving around different agencies with my wife, trying to file everything
[12:25] <zyga-ubuntu> jdstrand: o/
[12:26] <mup> PR snapd#3668 closed: cmd: fix tests that assume /snap mount <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3668>
[12:27] <mup> PR snapd#3669 closed: gitignore: ignore more build artefacts <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3669>
[12:27] <mup> PR snapd#3672 closed: cmd: fix mustUnsetenv docstring (thanks to Chipaca) <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3672>
[12:27] <zyga-ubuntu> mvo: any luck with your investigation?
[12:29] <mup> PR snapd#3665 closed: cmd/snap-confine: don't share /etc/nsswitch from host <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3665>
[12:30] <zyga-ubuntu> mvo: I've merged the backports, one last PR is testing (this should fix all issues there)
[12:30] <mup> PR snapd#3666 closed: snap/snapenv: always expect /snap for $SNAP <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3666>
[12:30] <zyga-ubuntu> mvo: the last backport should fix the avahi tests
[12:31] <jdstrand> hey zyga-ubuntu :)
[12:31] <mup> PR snapd#3667 closed: cmd: mark arch as non-reexecing distro <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3667>
[12:31] <zyga-ubuntu> jdstrand: hey
[12:31] <zyga-ubuntu> jdstrand: I just requested a review on https://github.com/snapcore/snapd/pull/3662
[12:31] <mup> PR snapd#3662: interfaces: convert broadcom-asic-control to common iface <Created by zyga> <https://github.com/snapcore/snapd/pull/3662>
[12:31] <zyga-ubuntu> jdstrand: this is one of maaany such PRs that I will open
[12:32] <zyga-ubuntu> jdstrand: the context is that this will help us with the udev tagging mega-PR
[12:32] <zyga-ubuntu> jdstrand: as it will (hopefully) reduce it down to just the policy changes
[12:32] <zyga-ubuntu> jdstrand: I was thinking that for testing we could also make udev tagging non-optional
[12:32] <zyga-ubuntu> jdstrand: that is, to always construct a cgroup
[12:32] <zyga-ubuntu> jdstrand: but I would only enable this in 2.28 (2.29 more likely)
[12:33] <zyga-ubuntu> jdstrand: after we feel confident that interfaces are actually OK
[12:33] <zyga-ubuntu> jdstrand: then anything that breaks is going to be a clear indicator that udev tagging is missing
[12:33] <jdstrand> zyga-ubuntu: please don't always create a cgroup
[12:33] <jdstrand> zyga-ubuntu: you'll break docker and lxd
[12:34] <zyga-ubuntu> jdstrand: aha!
[12:34] <zyga-ubuntu> jdstrand: I dind't think about them
[12:34] <zyga-ubuntu> jdstrand: well, too bad, but I understand
[12:34] <mup> PR snapd#3674 closed: cmd,tests: fix classic confinement confusing re-execution code (#3598) <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3674>
[12:34] <cachio> mvo, access granted
[12:34] <jdstrand> I'm fine with spread tests for everything that uses a cgroup
[12:34] <zyga-ubuntu> mvo: thank you!
[12:35] <jdstrand> but that could take a while
[12:36] <jdstrand> zyga-ubuntu: so, fyi, I was fine with the big udev PR and this is actually creating extra work for me, but I understand it was unwieldy for others so will re-review them
[12:37] <zyga-ubuntu> jdstrand: noted, I wanted to do it this way while *keeping* that other PR
[12:37] <zyga-ubuntu> jdstrand: so that we actually see the problem at hand being addressed there
[12:37] <mvo> cachio: thank you - I just promoted a new 2.27~rc7 to the beta channel. could you please start with the tests and let me know if anything goes wrong? a bunch of the test failures should be identified/fixed now, but for some I'm still uncertain, the deb test in particular I need help with, I would like to reproduce those, what do I need to do?
[12:38] <zyga-ubuntu> mvo: anything on the debian core bug?
[12:38] <zyga-ubuntu> mvo: I think we will still do rc8 but I'm happy that we will have more data at hand soon
[12:39] <mvo> zyga-ubuntu: which debian core bug is that? the 2.21->2.27~ reexec failure when multiple snaps are installed and core is pulled in implicitely?
[12:39] <zyga-ubuntu> mvo: yes
[12:39] <zyga-ubuntu> well, just one really :)
[12:39] <zyga-ubuntu> but yes
[12:39] <mup> PR snapd#3673 closed: packaging/arch: drop patches merged into master <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3673>
[12:39] <mvo> zyga-ubuntu: no progress on this one
[12:39] <zyga-ubuntu> mvo: snap install hello
[12:39] <zyga-ubuntu> mvo: noted
[12:40] <mvo> zyga-ubuntu: we may need a rc8  for this and also for the issue that pstolowski is debugging
[12:40] <mvo> zyga-ubuntu: I mostly did rc7 to ensure the other issues we know about got fixed
[12:40] <zyga-ubuntu> good point
[12:41]  * zyga-ubuntu runs back into the legal hell
[12:47] <cachio> mvo, ok
[12:47] <cachio> I'll start with those
[12:48] <zyga-ubu1tu> mvo: I'm wrapping up reviews (soon) and I'll jump to debian+core issue
[12:49] <cachio> mvo, dor deb tests I just exported the env vars https://paste.ubuntu.com/25262854/ and exec the tests over the release branch
[12:49] <mvo> cachio: thanks, I try this now
[12:49] <cachio> mvo, I followed the instructions that federico wrote https://forum.snapcraft.io/t/core-snap-validation-process-at-beta-channel/1454
[12:49] <zyga-ubu1tu> cachio: hey
[12:49] <zyga-ubu1tu> cachio: can you please qucikly look at https://travis-ci.org/snapcore/snapd/builds/261774010?utm_source=github_status&utm_medium=notification
[12:49] <cachio> zyga-ubu1tu, sure
[12:49] <zyga-ubu1tu> cachio: I merged your fedora PR and now, it seems, is that fedora upgrade/basic fails
[12:50] <zyga-ubu1tu> cachio: thank you!
[12:55] <pstolowski> mvo, i think i understand what's going wrong or at least have a theory based on the logs. autopkg tests take forever, i'm not sure what's wrong with them. let's discuss on standup
[12:56] <mvo> pstolowski: ok, this is the "missing install hook" error? it seems like those are also visible in spread, no?
[12:57] <cachio> zyga-ubu1tu, any idea why it could happened? https://paste.ubuntu.com/25262885/
[12:57] <zyga-ubu1tu> looking
[12:57] <zyga-ubu1tu> cachio: maybe we have a wrng %dir entry somewhere
[12:57] <zyga-ubu1tu> in the old version of snap-confine for fedora we had a directory there
[12:58] <zyga-ubu1tu> but I think there may be an issue with it since it had mode 0000 and many tools choked on that
[12:59] <zyga-ubuntu> cachio: I will not be back for 2-3 more hours so I'm away from fedora
[12:59] <pstolowski> mvo, yes, missing install hook error
[12:59] <pstolowski> mvo, i don't think i saw it in spread tests i run locally
[13:00] <pstolowski> retyring upgrade/basic spread test again
[13:08]  * ogra notes that mvo is rebooting all my development boards in a complex remote way once again :P
[13:16] <jdstrand> mvo: hi! I have a couple of non-contentious policy PRs that would be nice for 2.27. I @mvo'd you in the PRs-- is that sufficient for your consideration? do you want a list?
[13:19] <mvo> ogra: sorry for that
[13:19] <mvo> jdstrand: just tag them as 2.27
[13:19] <ogra> mvo, only teasing you :)
[13:19] <mvo> ogra: ;)
[13:20] <mvo> ogra: the new core is full of good stuff!
[13:20] <ogra> though it would be nice if we wouldnt trigger keyboard-bell for the shutdown notification ...
[13:20] <jdstrand> mvo: hmm, I thought I tried that last week. ok, let me try again
[13:20] <ogra> with three ssh session to three devicesopen my desktop always starts a "pling" concert ... repreating once per minute
[13:21] <ogra> (and i always search my ass off to find why i get kbd bell notifications)
[13:22] <mvo> jdstrand: I was off last week, so I can't say
[13:22] <mvo> jdstrand: but happy to pull in safe things at this point
[13:23] <mvo> cachio: fwiw, I think the deb upgrade test is confued, it uses 2.26.10 for snap and 2.27~rc7 for snapd so some env is wrong
[13:23] <cachio> mvo, ok
[13:24] <zyga-ubuntu> mvo: is that the no-reexec-back problem though?
[13:24] <mvo> zyga-ubuntu: maybe related but there was no failing core install
[13:24] <jdstrand> mvo: I think I don't know how to add a tag. I can add labels. how do you add a tag?
[13:25] <jdstrand> mvo: milestone?
[13:25] <mvo> jdstrand: yeah, milestone, that is the one
[13:26] <zyga-ubuntu> aha
[13:31] <jdstrand> mvo: I ok, I milestoned 4 PRs (a couple I thought were already in there but weren't yet)
[13:32] <mvo> jdstrand: all the ones you milestoned are merged alreday, right?
[13:32] <jdstrand> mvo: oh yes
[13:32] <jdstrand> all in master
[13:32] <mvo> jdstrand: ok, I have a look after the meeting
[13:32] <mvo> jdstrand: thank you!
[13:33] <jdstrand> mvo: I'll give you the list here
[13:33] <jdstrand> mvo: thank you!
[13:33] <jdstrand> https://github.com/snapcore/snapd/pull/3637
[13:33] <mup> PR snapd#3637: interfaces/unity7: allow receiving media key events in (at least) gnome-shell <Created by jdstrand> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3637>
[13:33] <jdstrand> https://github.com/snapcore/snapd/pull/3634
[13:33] <mup> PR snapd#3634: interfaces/many, cmd/snap-confine: miscellaneous policy updates <Created by jdstrand> <Merged by jdstrand> <https://github.com/snapcore/snapd/pull/3634>
[13:33] <jdstrand> https://github.com/snapcore/snapd/pull/3591
[13:33] <mup> PR snapd#3591: interfaces/greengrass-support: adjust accesses now that have working snap <Created by jdstrand> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3591>
[13:33] <jdstrand> https://github.com/snapcore/snapd/pull/3525
[13:33] <mup> PR snapd#3525: interfaces: add password-manager-service implicit classic interface (LP: #1653769) <Created by jdstrand> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3525>
[13:34] <jdstrand> mvo: the first two was what I was initially thinking about, but I noticed the second two weren't in https://github.com/snapcore/snapd/tree/release/2.27
[13:38] <mvo> jdstrand: I check them out now and see if they are easy to cherry-pick
[13:40] <pstolowski> mvo, so regarding the re-exec in the test, see https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-image/xenial/i386/s/snapd/20170804_173931_89d2f@/log.gz
[13:40] <pstolowski> mvo, and look for: "Aug 04 17:38:01 autopkgtest snapd[27809]: 2017/08/04 17:38:01.249361 daemon.go:252: started snapd/2.26.9+git1194.g7d0e792"
[13:40] <mvo> jdstrand: meh, slightly tricky to cherry-pick - well, not tricky, just work
[13:41] <pstolowski> mvo,  and "Aug 04 17:38:25 autopkgtest /usr/lib/snapd/snapd[27992]: daemon.go:251: started snapd/2.26.14"
[13:41] <jdstrand> mvo: 3 should be. password-manager-service is potentially not. if it isn't, we should backport it cause it is important for some snaps. holler if you need me to do it
[13:44] <mvo> jdstrand: thanks, it would be great if you could branch from release/2.27 and apply your changes on top of that, so the three branches (3637 was trivial to cherry-pick)  as PRs based on release/2.27 targeting release/2.27. if you could do that, that would help me a lot
[13:44] <mvo> jdstrand: I just pushed the release/2.27 with the cherry-picks for 3637
[13:46] <jdstrand> mvo: ok
[13:51] <zyga-ubuntu> re
[13:52] <cachio> mvo, is the new rc already in beta?
[13:52] <zyga-ubuntu> the agency closes in 9 minutes, I made it :)
[13:55] <mvo> cachio: it should be, do you see ~rc7 with "snap version"?
[13:56] <mvo> cachio: maybe I found the issue with the deb test, testing that right now
[13:56] <cachio> yes, but I see it is already building on linode, do we wait until it passes?
[13:58]  * zyga-ubuntu would love a coffee now
[13:59] <mvo> cachio: yeah, if spread is already running we might as well wait for that
[13:59] <cachio> ok
[13:59] <mvo> cachio: you mean spread-cron is running currently on the beta snap, right?
[13:59] <cachio> mvo, I am still creating the images for the tests, it should be ready in few minute
[14:00] <cachio> mvo, yes, I see this https://travis-ci.org/snapcore/snapd/builds/261835067
[14:00] <cachio> mvo, it is just started
[14:01] <mvo> cachio: thank you
[14:01] <mvo> cachio: I look at the deb scenario in the meantime
[14:11] <mup> PR snapd#3670 closed: snap/snapenv: document the use of CoreSnapMountDir for SNAP <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3670>
[14:12] <zyga-ubuntu> woohoo
[14:12] <mup> PR snapd#3662 closed: interfaces: convert broadcom-asic-control to common iface <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3662>
[14:26] <Pharaoh_Atem> mvo, zyga-ubuntu: rerunning based on tip of 2.27 branch: https://copr.fedorainfracloud.org/coprs/ngompa/snapd-prerel-fedora/build/587648/
[14:26] <Pharaoh_Atem> mvo: did you forget to bump the rc to rc7?
[14:27] <Pharaoh_Atem> zyga-ubuntu: I expect this to still fail on 32-bit architectures, as I didn't see any relevant changes to fix that in the branch
[14:27] <Pharaoh_Atem> am I correct in my assessment?
[14:34] <zyga-suse> Pharaoh_Atem: not yet, still in the pipe
[14:34] <zyga-suse> Pharaoh_Atem: I will fix all of snap-seccomp issues before 2.27 RC8 tomorrow
[14:35] <zyga-suse> Pharaoh_Atem: this is not the final RC as we still have two known issues
[14:35] <zyga-suse> Pharaoh_Atem: but we wanted to see less issues after merging relevant fixes
[14:55]  * Chipaca realises he's dug himself into a rabbit hole again, and stops
[14:57] <Pharaoh_Atem> zyga-suse: okay, cool
[15:02] <cachio> zyga-suse, still could not reproduce the error in fedora
[15:02] <zyga-suse> cachio: aha, thank you
[15:06] <mup> PR snapd#3675 opened: tests: restart snapd to ensure re-exec settings are applied <Created by mvo5> <https://github.com/snapcore/snapd/pull/3675>
[15:06] <mvo> cachio: the deb version mismatch is addressed by 3675 now . but the test itself is not yet applicable, it is only relevant for the SRU verification which is currently not needed as 2.27 is not yet in xenial-proposed
[15:06] <cachio> mvo, good
[15:07] <cachio> mvo, I'll update the doc in that case
[15:07] <cachio> thanks
[15:07] <mvo> cachio: we need to make sure 2.26 goes into -updates everywhere, federico used to take care of this, lets chase it together tomorrow
[15:07] <mvo> cachio: thanks for updating the docs
[15:08] <mvo> cachio: what do I need to do to run e.g. "Execution with an image built from the beta channel with kernel from stable:" locally? any special env vars I need to set?
[15:09] <mvo> cachio: I'm keen to run the VM tests for quick turnaround
[15:10] <cachio> mvo, perfect
[15:11] <cachio> I already started pi2 and 3 tests, but will take 6 hours aprox
[15:11] <cachio> mvo, just run the amd64 and i386 if you can
[15:11] <cachio> I am gonna lunch now
[15:12] <mvo> cachio: any special vars I need to set? or just run in 2.27 branch?
[15:12] <mvo> cachio: enjoy lunch!
[15:12] <cachio> mvo, just branch 2.27
[15:13] <mvo> cachio: ta, doing that now
[15:13] <mvo> cachio: when you are back, what env do I need to set to run "Execution with an image built from the beta channel with kernel from stable:"?
[15:19] <morphis> niemeyer: ping
[15:23] <zyga-ubuntu> mvo: nice find
[15:29] <Saviq> zyga-ubuntu: hey, does this ring a bell? is this the right place to file issues like that at all? https://bugs.launchpad.net/snappy/+bug/1708703
[15:29] <mup> Bug #1708703: "enable" does not apply connected slot security policy <Snappy:New> <https://launchpad.net/bugs/1708703>
[15:30] <zyga-suse> hmmm
[15:30] <zyga-suse> Chipaca: does this ring any of your bells?
[15:30] <zyga-suse> I recall we had some enable/disable bugs
[15:30] <zyga-suse> but nothing that would explain this for me
[15:30] <Chipaca> ?
[15:30] <zyga-suse> Saviq: so after you disable + enable, is the interface connected?
[15:31] <Chipaca> that does not ring a bell, no
[15:31] <Chipaca> doesn't mean it isn't a bug :-)
[15:31] <pedronis> zyga-suse: you did something in that area, not Chipaca, Chipaca fixed flag issues
[15:31] <ogra> we had such a bug in mir in the past
[15:31]  * zyga-suse looks
[15:32] <ogra> (had to disable/enable it to make the kiosk demos work ... the docs page that described it (and linked to the bug) is gone though)
[15:32] <pedronis> they might have interacted though
[15:32] <pedronis> because some flags affect profiles
[15:38] <zyga-ubuntu> Saviq: question
[15:38] <zyga-ubuntu> do you see anything like that in logs
[15:38] <zyga-ubuntu>             task.Errorf("skipping security profiles setup for snap %q when handling snap %q: %v", affectedSnapName, affectingSnap, err)
[15:39] <zyga-ubuntu> just "skipping security profiles"
[15:42] <zyga-suse> kalikiana: thank you for checking
[15:42] <zyga-suse> kalikiana: I'll look at reproducing this next
[15:49] <kalikiana> zyga-suse: Thanks. Much appreciated!
[15:52] <matteo> zyga-suse: no zyga-fedora?
[15:52]  * ogra waits for zyga-minix ...
[15:52] <matteo> MULTICS
[15:53]  * zyga-suse wonders how is zyga in EBCDIC when interpreted as ASCII
[15:54]  * zyga-ubuntu takes a break from all of this
[15:54] <zyga-ubuntu> too many topics
[15:54] <cachio> mvo, the ones from here http://cdimage.ubuntu.com/ubuntu-core/16/stable/
[15:54] <zyga-ubuntu> head.spin
[15:54] <mvo> cachio: ta!
[15:55] <mvo> cachio: and then running against the external backend?
[15:55] <cachio> yes
[15:55] <mvo> cachio: thanks again
[15:56] <cachio> mvo, you need to do
[15:56] <cachio> sudo snap refresh
[15:56] <cachio> reboot
[15:56] <cachio> sudo snap refresh --beta core
[15:56] <cachio> and then run the tests
[15:58] <Chipaca> zyga-ubuntu: "\xa9\xa8\x87\x81".
[15:58] <Saviq> AlbertA: can you see above ↑ for what zyga-ubuntu asked about the bug you reported?
[16:00] <AlbertA> Saviq: ok, let me see
[16:03] <Chipaca> oops
[16:04] <AlbertA> zyga-ubuntu: the skipping security profiles should be vieweable in journalctl? I'm just doing sudo journalctrl -f
[16:05] <AlbertA> zyga-ubuntu: this is all I get when I do enable: http://pastebin.ubuntu.com/25263708/
[16:05] <AlbertA> this is with 2.27~rc7
[16:11]  * ahoneybun wonders if you can use snap to replace certain files
[16:12] <ahoneybun> and if you could ship a snap installed by default on the ISO
[16:14]  * niemeyer waves o/
[16:15] <zyga-ubuntu> Chipaca: :D
[16:15] <zyga-ubuntu> AlbertA: yes
[16:16] <zyga-ubuntu> ahoneybun: replace how?
[16:16] <zyga-ubuntu> ahoneybun: not yet but I bet this will come
[16:25] <ahoneybun> zyga-ubuntu: wondering if I could use it to keep our Manual update to date between releases
[16:25] <ahoneybun> could get around the SRU stuff
[16:30] <cachio> mvo, which is the out of space error you saw for the res 1
[16:30] <cachio> ?
[16:30] <cachio> I dont see that
[16:31] <mvo> cachio: if you go to  https://paste.ubuntu.com/25190950/ and search for "no space left on device" (line 464). I hope I look at the right log :)
[16:31] <mvo> cachio: meh, apparently not, which one is the right log, could you please link to that in the gdoc?
[16:32] <cachio> mvo, ok, you are talking about the exec for the rc6
[16:33] <cachio> ok, I'll talk to plars about that
[16:33] <mvo> cachio: thank you
[16:41] <zyga-ubuntu> ahoneybun: can you tell me more?
[16:51] <ahoneybun> zyga-ubuntu: well only LTS will get more releases to update our Manual but if we snap it we could just push it right away
[16:54] <niemeyer> morphis: Heya
[16:54] <niemeyer> morphis: Just now saw your earlier ping
[16:56] <zyga-ubuntu> ahoneybun: sure but I don't know which software you are talking about
[16:56] <zyga-ubuntu> ahoneybun: so if you tell me more I will try to help you out
[17:00] <ahoneybun> zyga-ubuntu: https://github.com/ahoneybun/kubuntu-manual
[17:00] <ahoneybun> it's being cloned to launchpad so I could see if that would build a snap
[17:01] <zyga-suse> let me look
[17:01] <zyga-suse> so
[17:01] <zyga-suse> you can easily ship this in a snap
[17:01] <zyga-suse> not sure what you meant about "replacing"
[17:05] <mvo> zyga-suse: I'm trying to make sense of the debian 2.21->current thing, what I see is that there is a defuct [snapctl] <defunct> child of the configure hook for core, but no denial or anything. and also strange that the process is not claimed by anything
[17:06] <zyga-suse> mvo: it's not a denial, I think this is seccomp
[17:06] <zyga-suse> mvo: and seccomp kills may not leave a trace on Debian
[17:06] <zyga-suse> not sure
[17:06] <zyga-suse> mvo: it is not claimed because its parent is bash
[17:06] <zyga-suse> mvo: and the actual process is a multi-threaded golang program
[17:06] <zyga-suse> mvo: and one of the threads died
[17:07] <zyga-suse> mvo: but the process as a whole is still alive
[17:07] <zyga-suse> mvo: do you see any other threads?
[17:07] <zyga-suse> (tasks)
[17:09] <mup> PR snapd#3676 opened: interfaces/many, cmd/snap-confine: miscellaneous policy updates (#3634) <Created by jdstrand> <https://github.com/snapcore/snapd/pull/3676>
[17:09] <mvo> zyga-suse: how do I see those?
[17:09] <mvo> zyga-suse: you mean snapctl has a thread that is still alive?
[17:10] <zyga-ubuntu> mvo: yes, that's what I suspect
[17:10] <zyga-ubuntu> mvo: I always use htop
[17:10] <zyga-ubuntu> mvo: it can show process threads separately
[17:11] <mvo> zyga-ubuntu: do you know if there is a way to figure that out, I can not gdb attach, it says it  is a zombie
[17:11] <ahoneybun> zyga-ubuntu: oh yea? https://code.launchpad.net/~ubuntu-branches/ubuntu/vivid/kubuntu-docs/vivid this is what we used to use
[17:11] <zyga-ubuntu> mvo: you can also make sure that is configured this way (it is by default) by hitting F2 (setup), going to display options and then unchecking "hide userland process threads"
[17:11] <ahoneybun> it places the files in a dir on the machine
[17:12] <mvo> zyga-ubuntu: ohhh, htop it is! it shows snapctl get service.ssh.disable as the last get
[17:12] <zyga-ubuntu> ahoneybun: snaps cannot place files in arbitrary places, so you won't be able to
[17:12] <zyga-ubuntu> mvo: perfect!
[17:12] <zyga-ubuntu> mvo: I'm sure ps has a way to show this too
[17:12] <zyga-ubuntu> just muscle memory
[17:12] <zyga-ubuntu> mvo: ps -eLf
[17:13] <zyga-ubuntu> mvo: or ps axms
[17:13] <zyga-ubuntu> mvo: what else do you see?
[17:14] <mvo> zyga-ubuntu: there we go - two threads (LWP) still alive for snapctl
[17:14] <zyga-ubuntu> mvo: right, because seccomp kills just the thread
[17:14] <zyga-ubuntu> not the whole process (darn)
[17:15] <mup> PR snapd#3677 opened: interfaces/greengrass-support: adjust accesses now that have working … <Created by jdstrand> <https://github.com/snapcore/snapd/pull/3677>
[17:15] <mvo> zyga-ubuntu: meh, I wonder if there is anything that we can do about this
[17:16] <zyga-ubuntu> mvo: I'd love to get to the bottom of this :/
[17:16] <mvo> zyga-ubuntu: I mean, let snapctl die entirely in this scenario
[17:16] <zyga-ubuntu> mvo: I'll dig into it again in the evening, now drained
[17:17] <zyga-ubuntu> mvo: not sure why it is getting killed though
[17:17] <mvo> zyga-ubuntu: its definitely that, when I manually kill the two threads the install fails as expected
[17:17] <mvo> zyga-ubuntu: yeah, figuring out why it gets killed is the next step
[17:17] <mup> PR snapd#3677 closed: interfaces/greengrass-support: adjust accesses now that have working … <Created by jdstrand> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3677>
[17:17] <mvo> zyga-ubuntu: do we have a forum topic for the debian bug already?
[17:18] <zyga-ubuntu> mvo: kind of
[17:18]  * zyga-ubuntu looks
[17:19] <mvo> zyga-ubuntu: just found an old one that is not helpful, I think I just create a new one
[17:19] <zyga-ubuntu> https://forum.snapcraft.io/t/snapd-out-of-the-box-experience-debian-9/1484
[17:19] <zyga-ubuntu> mvo: ^
[17:31] <zyga-ubuntu> mvo: ah, you created a new topic
[17:31] <zyga-ubuntu> mvo: AFAIK the seccomp behavior is expected and correct
[17:31] <zyga-ubuntu> mvo: can you share dmesg from that VM please
[17:59] <mup> PR snapd#3678 opened: Merge pull request #3525 from jdstrand/password-manager-service <Created by jdstrand> <https://github.com/snapcore/snapd/pull/3678>
[18:02] <jdstrand> mvo: ok, I created #3676, #3677 (merged by zyga) and #3678
[18:25] <ahasenack> do you guys prefer bugs against snapd filed via the forum, or launchpad? Or something else?
[18:33] <mup> PR snapd#3679 opened: Updated 'Get in touch' links to Rocket and forums <Created by Ads20000> <https://github.com/snapcore/snapd/pull/3679>
[18:36] <zyga-suse> ahasenack: I think forum is best
[18:37] <ahasenack> zyga-suse: I just found https://github.com/snapcore/snapd/ whose README says "If you have found an issue with the application, please file a bug on the bugs list on Launchpad."
[18:37] <ahasenack> with a link to https://bugs.launchpad.net/snappy/+filebug
[18:37] <ahasenack> is that old/deprecated?
[18:37] <zyga-suse> I think it's all a bit all over the place
[18:37] <zyga-suse> lauchpad.net/snapd is one place
[18:38] <zyga-suse> the forum is a good starting point
[18:38] <zyga-suse> and that README needs tweaking (PRs welcome!)
[18:40] <ahasenack> hm, no openid for the forum yet?
[18:57] <mup> Bug #1709155 opened: Better error message for unsupported kernel <Snappy:New> <https://launchpad.net/bugs/1709155>
[20:00] <mvo> zyga-ubuntu: re dmesg> nothing in there
[21:13] <superjonotron> does anybody know the correct way to use /etc/network/interfaces.d files? can this define multiple interfaces or only one at a time? I put my  usual full interfaces file into it instead of creating multiple files per interface but dns seems to break even with dhcp on different interfaces regardless of defined in the file or in /etc/resolv.conf
[21:21] <kyrofa> superjonotron, yeah having multiple dhcp doesn't seem to make dns happy
[21:21] <kyrofa> superjonotron, when I have two interfaces both using dhcp, I make sure to specify the DNS with `dns-nameservers`
[21:23] <superjonotron> kyrofa, i only set one to dhcp and the other static with the dns-nameservers defined, i basically just took what I was doing in Ubuntu 16.04 desktop and put that file into inerfaces.d/interfaces so I know the config is good, just ubuntu core seems to not like this
[21:24] <superjonotron> i've also removed the name-servers from that file and just left them in /etc/resolv.conf but same results
[21:24] <kyrofa> superjonotron, what exactly is happening-- no domains are resolving at all?
[21:25] <kyrofa> superjonotron, Ubuntu Core uses netplan I believe
[21:25] <superjonotron> kyrofa, yes no domains will resolve once I define anything in the /interfaces.d directory
[21:26] <superjonotron> kyrofa, if I don't define anything there and both are dhcp since not defined, it works fine
[21:26] <kyrofa> mwhudson, are you around? I'm not sure why Ubuntu Core is behaving differently there ^^, but I bet you do
[21:27] <mwhudson> hi
[21:28] <superjonotron> mwhudson, hello
[21:29] <superjonotron> for completeness, here is the file named "interfaces" currently in /etc/network/interfaces.d
[21:29] <superjonotron> auto lo iface lo inet loopback  auto mlan0 iface mlan0 inet dhcp  auto eth1 iface eth1 inet static         address 100.100.1.130         netmask 255.255.255.0         gateway 192.168.9.254  auto eth0 iface eth0 inet dhcp  auto docker0 iface docker0 inet static         address 172.17.0.1         netmask 255.255.0.0         gateway 192.168.9.254  dns-nameservers 4.2.2.2 8.8.8.8
[21:33] <mwhudson> superjonotron: you are not expected to use ifupdown with ubuntu core
[21:34] <mwhudson> superjonotron: but rather netplan as kyrofa says
[21:37] <superjonotron> mwhudson, looking at the docs, there doesn't seem to be much there other than it points to an actual network manager and defaults to systemd-networkd if not defined (which I expect is the default state)
[21:38] <superjonotron> mwhudons, do you know the preferred method of ubuntu core is?  finding this information in any official documentation has been so far impossible
[21:38] <mwhudson> superjonotron: the format is pretty simple though, don't the examples help?
[21:39] <mwhudson> superjonotron: there is probably not a lot of documentation on how to do this by hand, you are expected to do it via console conf
[21:39] <mwhudson> we need a way to just run the networking bits of console-conf i think
[21:41] <superjonotron> mwhudson, looking at the systemd-network seems straight forward syntaxically, just a big format change to the old interfaces file
[21:41] <mwhudson> superjonotron: yeah
[21:41] <superjonotron> mwhudson, also not sure if I need a different file per interface or can it be bundled in one?
[21:41] <mwhudson> superjonotron: you don't have to configure networkd directly either though
[21:42] <superjonotron> mwhudson, how would you have an application modify the ip address without modifying directly then?  not familiar with console conf
[21:42] <mwhudson> superjonotron: have you seen https://wiki.ubuntu.com/Netplan and https://wiki.ubuntu.com/Netplan/Design ?
[21:46] <superjonotron> mwhudson, looking through those just quickly and it still seems you need to use NetworkManager or systemd-networkd
[21:46] <mwhudson> yes but netplan does that for you
[21:50] <superjonotron> mwhudson, so based on the docs, I should be able configure my /interfaces.d/interfaces file and then run netplan ifupdown-migrate to generate this new style of networking?
[21:50] <mwhudson> superjonotron: that would be one way of doing it, yes
[21:51] <superjonotron> mwhudons, seems the easiest path rather than retooling code that is hardened for older versions of ubuntu and I know is stable.  Are there any other steps after that command required to make it take effect?
[21:58] <superjonotron> mwhudson, that method fails, "method static is not supported"  seems like a pretty broken network managing solution if it doesn't understand that.  Looks like the default configuration is actually NetworkManger which has it's own configurations to use.  How is netplan supposed to be used?  So far i'm just seeing layers of network configuration required as a opposed to a single config file
[22:06] <superjonotron> additionally, NetworkManager is defaulted in Ubuntu Core 16 but NetworkManager isn't even installed so, i don't know about this new network stuff in ubuntu core, it all seems very incomplete
[22:16] <superjonotron> anybody willing to help me figure out how to convert the well supported interfaces file format to the new netplan yaml structure?  netplan's conversion command doesn't work and i just can't seem to grasp this new netplan system
[22:25] <superjonotron> help with using netplan, anybody?
[22:31] <mwhudson> superjonotron: i think it's probably something like this: http://paste.ubuntu.com/25265918/
[22:31] <mwhudson> superjonotron: but i doubt you actually want to configure docker0 like that?
[22:33] <superjonotron> mwhudson, thanks for that.  I'm still not entirely sure where I put that file though since there's currently two files created by default on installation, 00-default-nm-renderer.yaml  00-snapd-config.yaml
[22:33] <mwhudson> superjonotron: remove both of those
[22:33] <superjonotron> mwhudson, the docker0 is just currently being read and written back so it can maintain all the network connections in one place
[22:33] <superjonotron> i will likely filter it out completely in the end
[22:36] <superjonotron> mwhudson, is there a restart command to make this take effect?
[22:36] <mwhudson> superjonotron: netplan apply
[22:38] <superjonotron> mwhudson, line 6 column 5: expected mapping
[22:39] <mwhudson> superjonotron: oh oops
[22:40] <mwhudson> superjonotron: it's nameservers: {'addresses': [...]}
[22:41] <mwhudson> not a list directly under nameservers
[22:45] <superjonotron> mwhudson, so the format would be http://paste.ubuntu.com/25266022/ ?
[22:47] <mwhudson> superjonotron: something like that
[22:48]  * mwhudson is currently feeding a baby
[22:52] <superjonotron> mwhudson, i'll keep messing with it, somethings still not right since it fails at line 6 column 6 with the same error, wish the docs were better but hopefully i'll eventually guess the right syntax
[23:14] <superjonotron> well, i'm at a loss for the format for dns servers for netplan, documentation seems to be incorrect and so i'm at a loss on figuring out ubuntu cores network configuration options
[23:14] <superjonotron> i'd almost be willing to strip away all this netplan stuff in favor of just using the tried and true interfaces file if that was an option anybody knew how to accomplish