[03:43] When you're running a snap build on launchpad and the source website goes down after 40 min === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [06:53] good morning [06:53] mvo: around? :-) [06:53] hey zyga-suse - good morning [06:54] mvo: welcome back, how were your holidays? [06:54] zyga-suse: very nice, thank you! [06:54] mvo: we have some odd failures in xenial-proposed [06:54] zyga-suse: how are things here? [06:54] mvo: I'll be right back, let me just get some coffee [06:55] zyga-suse: sure [06:55] mvo: lots of things in flight :) [06:55] mvo: I'll tell you in a moment [06:55] zyga-suse: do you have links for me with the failures? [06:55] zyga-suse: ok [06:55] zyga-suse: get your coffee :) [07:02] mvo: http://people.canonical.com/~ubuntu-archive/pending-sru.html [07:02] oh, looks better than last week [07:03] there were armfh failures and a few others [07:03] but now I see [07:03] Missing build dependencies: libseccomp-dev (>= 2.1.1-1ubuntu1~trusty4) [07:03] mvo: we also have https://bugs.launchpad.net/snappy/+bug/1707474 [07:04] and this one affects everyone, not just ubuntu [07:04] mvo: I wanted to try out a simple fix [07:04] + we have a tonne of reviews to do [07:05] mvo: is 2.27 tagged yet? [07:06] zyga-ubuntu: yeah, the build issue in xfsprogs is annoying [07:06] mvo: I wanted to cherry pick a few fixes for arch (and probably one more for everyone on 32 bit systems) [07:09] mvo: I also found a reliable way to show that reexec is just broken in debian [07:09] mvo: there's a spread reproducing this (but I cannot merge it because it breaks regular tests for unrelated reason) [07:09] mvo: so one thing I would consider adding to to 2.27 fixup pipe [07:10] mvo: so all in all, it looks like a busy monday [07:13] pstolowski: good morning [07:13] zyga-ubuntu, hey! [07:16] zyga-ubuntu: indeed, meh [07:17] zyga-ubuntu: thanks for the update! looking at the spread tests issues now [07:18] hi mvo! [07:19] mvo: https://github.com/snapcore/snapd/pull/3635 that's the one I meant [07:19] zyga-ubuntu: great, looking [07:20] mvo: so your hunch about installing core along with the 1st snap was right [07:20] zyga-ubuntu: just looking at the test, nice, thank you! the interessting question is if there is anything we can do :/ [07:25] 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] mvo: the pending SRU looks good, last week it was a bunch of test failures, maybe they got re-triggered [07:25] zyga-suse: probably [07:25] mvo: I talked to apw about them before and he re-triggered them once again because of internal connectivity errors in launchpad [07:26] zyga-suse: did you had a chance to look at the failure in debian yet? if core is implicitely downloaded? [07:26] zyga-suse: thank you [07:26] yes, I did, core is downloaded implicitly [07:26] mvo: then things break on the configure hook [07:26] mvo: I was pondering disabling that for now [07:26] mvo: to buy us time for 2.28 to land the configure hook with http proxy config option [07:26] zyga-suse: did we restart into the new snapd at this point? [07:27] mvo: not sure, I spent most of last week on lots of little tasks [07:27] mvo: just get that PR and fire it up in linode (edit workers) [07:27] mvo: it's more reliable than my memory at this stage [07:27] zyga-suse: sure, thank you [07:27] mvo, mwhudson: looked at updating debian but we have two forks to adjust [07:27] zyga-suse: indeed [07:27] mvo: and it's unclear if we want to package those forks in debian or wait for them to merge [07:27] hi hi [07:28] hey hey :) [07:28] 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] Looking for a build for https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/bluez/commit/?h=bluez/5.44 [07:29] 2nd review needed for trivial #3659 and #3661 (note, the latter is against 2.27) [07:29] ashwind: I think morphis knows about those [07:29] 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] mvo: oh ok [07:30] we're only targetting stretch at a well, stretch [07:30] so perhaps this problem can be fixed with sed :) [07:30] ashwind: that version of bluez is available on the store [07:30] pstolowski: that latter one has tests failing [07:30] 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] mvo: might it make sense for me to push it to get started? [07:31] ashwind: at minimum it should be able in the edge channel [07:31] mwhudson: I may actually just kill x/net in favour of kernel based tests. [07:31] mvo: ok [07:31] mwhudson: aha, indeed, that would be nice, I will dig out my diff [07:32] zyga-ubuntu, yes i know,but it's completely unrelated to the change [07:34] pstolowski: restarted tests [07:34] thx [07:35] zyga-ubuntu, thanks [07:49] pstolowski: good morning to you as well, sorry, overlooked your message earlier :) [07:49] pstolowski: 3661 has an interessting failure that might be worth exploring [07:52] 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] mvo: it is good, I will update it to drop the patches once they land [07:57] mvo: let's land it now thought [07:57] *though === apw_ is now known as apw [08:03] ogra_: was there any change in config.txt necessary to get BT working with Ubuntu Core on the pi? [08:09] zyga-suse: you still owe me another review-round from last week :-) [08:09] indeed, reviews will be 90% of my day [08:09] * zyga-suse eats breakfast now [08:09] stress is eating me alive here, darn government forms that don't work [08:13] mvo, ah indeed, i didn't check all logs and missed that one. the failures I saw were about upgrade/basic [08:30] aha, it is upgrade/basic failing because of unregistered hook. looking [08:31] zyga-ubuntu, having fun with registering your company? [08:32] pstolowski: yes, ZUS ZUA form is silly [08:32] hehe [08:32] just resolved it by talking to a consulant [08:32] you can either select mandatory thing or optional thing [08:32] but the wording is confusing so it seems you have to check both boxes [08:32] and the error message given is utterly confusing [08:33] pstolowski: that's *the* bug I was talking about earlier [08:33] fill it on paper. no errors ;) [08:33] right... [08:33] if only that was true [08:33] that form is the equivalent of the paper form [08:33] but you don't have to type it over and over this way [08:34] (and I hate handwriting in forms) [08:37] darn, now I have to sign it myself === fnordahl_ is now known as fnordahl [08:46] mvo, how can I run autopkgtests locally? [08:46] just building the debs is enough? [08:48] 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] pstolowski: if you are on xenial you may need the autopkgtest from xenial-backports [08:48] mvo, ack, thanks! [08:51] 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] mvo, these PRs I linked above fix exactly that [08:53] pstolowski: aha, excellent [08:53] pstolowski: 3661 is the one? [08:53] pstolowski: or a different one? [08:53] mvo, yes 3661 is for 2.27. 3559 is for master [08:54] pstolowski: cool, thank you [08:55] 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] mvo, yes I'm investigating (need to repro first) [08:56] pstolowski: sure :) thank you. no pressure, just wanted to put it on your radar [09:04] ashwind: I just got the confirmation from ogra_ that /lib/firmware/BCM43430A1.hcd exists [09:04] ashwind: which core image did you take and which version of kernel/gadget snap for the pi are you using? [09:09] 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] ogra_: thanks [09:13] ogra_: using the edge or daily images should give you at least the patch files in /lib/firmware [09:13] when you install bluez in devmode then you should be able to load the patchram file with hciattach [09:16] 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] that should have all necessary firmware bits in /lib/firmware [09:17] 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] sure let me try that [09:23] * zyga-suse fills in VAT-R :/ [09:30] ashwind, see https://bugs.launchpad.net/snappy/+bug/1674509/comments/30 (you dont need the first line) [09:37] ok, I need to go out to get those documents signed [09:37] mvo: I'll be working outdoors today, just mainly doing code reviews [09:37] mvo: can you please assign me to specific PRs [09:37] mvo: I will focus on those if you do [09:37] zyga-suse: sure - 3664 should be a trivial one [09:37] * zyga-suse starts [09:38] zyga-suse: also #53 on snapcore/core [09:42] mvo: both done [09:42] zyga-suse: thank you [09:42] 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] mvo: and perhaps we can, by then, fix the debian bug too [09:44] 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] rc5 is ...? [09:44] for 2.27? [09:44] zyga-suse: yes, sorry. we are currently at 2.27~rc4 and have some test failures [09:45] ah, I see [09:45] will you use the release branch or master for rc5? [09:45] zyga-suse: relese branch, 2.27 was forked some days ago [09:46] ok, shall I target my fixes there then? [09:46] zyga-suse: ideally, if they are small we can also cherry pick them [09:46] yes, each fix is one patch, easy to cherry [09:46] if you prefer I can give you hash IDs [09:49] zyga-suse: thats fine, just target the PR with 2.27 [09:49] sure [09:55] mvo: done [09:55] mvo: there's one more but it didn't land in master yet (that is #3648) [09:57] 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] ondra: hey, trivial comment on https://github.com/snapcore/snapd/pull/3624 [10:02] pstolowski: please try to install autopkgtest from xenial-backports, sudo apt install -t xenial-backports autopkgtest [10:03] pstolowski: iirc the version in xenial was a bit more complicated and the test env uses the new autopkgtest stuff anyway [10:03] mvo, ah, right, I forgot that backports repo needs to be forced [10:03] the one in xenial doesn't work [10:04] you need backports, period [10:04] pstolowski: good luck, adt is a bit "special" (but it got much better with the version in -backports) [10:07] mvo, this seems to be working, tests were started, thanks [10:10] I spoko too soon.. it failed on build [10:10] 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] pstolowski: oh, it failed in what way? [10:10] zyga-suse updated now [10:11] zyga-suse and installing plugin for my editor :) [10:11] mvo, a number of tests passed, and then http://pastebin.ubuntu.com/25262220/ [10:15] pstolowski: could you please paste a bit more? [10:15] pstolowski: maybe the entire log [10:16] sure, let me try again [10:18] ondra: cool [10:18] thank you [10:21] mvo: hi, this is done now, right: https://forum.snapcraft.io/t/channels-2-0-implementation/156 ? [10:22] mvo, http://pastebin.ubuntu.com/25262279/ [10:22] pstolowski: yes, the channels 2.0 stuff should be sorted [10:23] pstolowski: hm, mysterious "FAIL: cmd_interfaces_test.go:34: SnapSuite.TestInterfacesHelp" fails (see line 2449 [10:24] mvo: that is because outdated vendor.json === zyga-ubu1tu is now known as zyga-ubuntu [10:24] mvo: after specific go-flags update the help output format has changed [10:24] pstolowski: aha, so run ./get-deps I guess [10:24] zyga-ubuntu: ta! [10:24] indeed [10:24] hmm [10:24] * zyga-ubuntu is on the way to register VAT, ZUS and import the car into poland [10:24] so.... well [10:25] I'm online and my wife will help with all the paperwork but always "fun" [10:26] zyga-ubuntu, more fun awaiting when you declare taxes for this year early next year ;) [10:27] pstolowski: you mean JPK? [10:27] zyga-ubuntu, no. just declaring earnings from abroad, exchange rate conversion etc [10:27] is it a trait to be able to expand any three letter acronym into curse words? [10:28] pstolowski: I don't have to [10:28] pstolowski: my yearly stuff is going to be in spain [10:28] pstolowski: so I'll just have to declare that [10:28] zyga-ubuntu, ah ok, good [10:28] pstolowski: I'm not a resident this year [10:28] right [10:28] pstolowski: but next year each micro company needs to file JPK [10:28] (jednolity plik kontroli) [10:29] zyga-ubuntu, that should be no brainer with any of the online accounting services I told you about [10:29] pstolowski: I'm doing that on paper [10:29] pstolowski: then I think I don't need it [10:30] pstolowski: JPK is needed when you use software for taxes [10:32] mvo: should I expect this in 2.27? [10:32] - 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] https://travis-ci.org/snapcore/snapd/builds/261760429?utm_source=github_status&utm_medium=notification [10:39] zyga-ubuntu: hm, where do you get this error? [10:40] mvo: on the linked PR [10:40] mvo: this is one of the backport branches [10:40] 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] Chipaca: I'm looking at the services PR now, would you like to look at https://github.com/snapcore/snapd/pull/3636? [10:44] morphis: and your userd PR is next [10:45] zyga-ubuntu: in a bit (got some context in-head rn) [10:45] zyga-ubuntu: the failure you see is interessting, I will try to reproduce [10:46] mvo: I'd like to squash merge this: https://github.com/snapcore/snapd/pull/3622 [10:46] ok [10:46] Chipaca: no worries, this is not in a rush o [10:46] or anything :) [10:46] mvo: that looks like what we were fighting all 2.24.x with [10:46] mvo: uses distro package but there is no snap-update-ns there? (odd) [10:46] zyga-ubuntu: fine with the squash merge [10:47] mvo: is that snapd-after-reexec doing stuff on reverted core? [10:50] zyga-ubuntu: I think its something else, let me dig deeper [10:54] 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] 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] mvo: not in 2.27 [10:57] 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] mvo: suggestion: merge 2.26.14 into release/2.27 [10:57] it would be odd if 2.27 regressed on fixes from point releases of 2.26 [10:58] zyga-ubuntu: do you have an example of how the 'contents' arg of snaptest.MockSnap is meant to be used? [10:59] Chipaca: let me look [10:59] * zyga-ubuntu doens't recall MockSnap [10:59] just MockInfo [10:59] zyga-ubuntu: blame says its yours, only reason i'm asking you :-) [10:59] it's* [11:00] aha [11:00] it looks like a path to a squashfs file [11:00] er [11:00] zyga-ubuntu: indeed, just double checked, it looks like its the only missing commit [11:00] not path [11:00] *the* file [11:00] ogra_: Sounds good I'll make the changes. [11:00] mvo: great catch! [11:00] Chipaca: grepping [11:01] zyga-ubuntu: review for 3671 would be great :) [11:01] (super trivial) [11:01] Chipaca: seems like we pass an empty string there [11:02] done [11:02] Chipaca: I really don't get it [11:02] mvo: "will unsetenv the for"? [11:02] why not MockInfo then? [11:02] $SNAP :D [11:02] zyga-ubuntu: it seems to expect the _contents_ of a squashfs [11:03] Chipaca: exactly [11:03] oh wait [11:03] zyga-ubuntu: sorry, it looks like the bit that writes that out is from robert ancell [11:04] zyga-ubuntu: nm then, ty! [11:04] Chipaca: indeed, the docstring is slightly bad, I fix that in master [11:04] k [11:05] mvo: interesting how all my backport/ branches now fail [11:07] pstolowski: - Run install hook of "core" snap if present (internal error: no registered handlers for hook "install") [11:07] 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] pstolowski: do you want to collect that log? [11:07] zyga-ubuntu: please merge release/2.27 - that should have some fixes [11:07] mvo: ^^ I strongly feel that this is something we must fix for rc5 [11:07] OK [11:08] zyga-ubuntu: the above one is still under investigation, I saw this this morning as well [11:08] mvo: I've been seing it for a few weeks [11:08] seeing* [11:08] zyga-ubuntu: ok, then definitely something we need to tackle for 2.27 [11:08] zyga-ubuntu: but pstolowski is aware of it and investigates (context see above) [11:09] that's all we need [11:09] zyga-ubuntu, yep, as mvo says, that's the same error we discussed earlier today [11:11] janisozaur1: https://github.com/snapcore/snapd/pull/3673 [11:12] janisozaur1: I'm away from my Arch system, can you please try that? [11:13] 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] let me check [11:13] ah [11:13] indeed! [11:16] * Chipaca ~> lunch (including lunch-time run) [11:16] mvo: https://github.com/snapcore/snapd/pull/3674 [11:17] mvo: specifically this was missing: https://github.com/snapcore/snapd/pull/3674/files#diff-77cd38482da5f11c05ccdcfa24f61aea [11:17] mvo: but I suspect we also want other parts of that commit [11:17] ah, after merging release/2.27 those are just tests [11:25] * Chipaca now really off === chihchun is now known as chihchun_afk === ogra_ is now known as ogra === mup_ is now known as mup [11:48] * zyga-ubuntu arrives at the tax agency [11:48] ttyl [11:56] 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] Good mornings! [12:04] zyga-suse: nice catch [12:04] hey niemeyer, good morning! [12:04] mvo: Heya! Welcome back! [12:17] * zyga-ubuntu needs proof that he is not in spain [12:17] legal logic [12:21] zyga-ubuntu: :) [12:21] mvo: morning! [12:21] zyga-ubuntu: Oh, you're actually serious? [12:21] Son_Goku: hello hello [12:21] Son_Goku: Heya [12:22] niemeyer: haha, yes :( [12:22] zyga-ubuntu: Okay, so I think somebody *else* needs proof that you're not in Spain :P [12:22] niemeyer: but not too terrible, 1/3 paperwork done [12:22] zyga-ubuntu: I thought you had woken up in a Spain mood ;) [12:22] niemeyer: solving one the next 1/3 [12:23] niemeyer: haha, no that would be nifty but not terrible :) [12:23] niemeyer: driving around different agencies with my wife, trying to file everything [12:25] jdstrand: o/ [12:26] PR snapd#3668 closed: cmd: fix tests that assume /snap mount [12:27] PR snapd#3669 closed: gitignore: ignore more build artefacts [12:27] PR snapd#3672 closed: cmd: fix mustUnsetenv docstring (thanks to Chipaca) [12:27] mvo: any luck with your investigation? [12:29] PR snapd#3665 closed: cmd/snap-confine: don't share /etc/nsswitch from host [12:30] mvo: I've merged the backports, one last PR is testing (this should fix all issues there) [12:30] PR snapd#3666 closed: snap/snapenv: always expect /snap for $SNAP === chihchun_afk is now known as chihchun [12:30] mvo: the last backport should fix the avahi tests [12:31] hey zyga-ubuntu :) [12:31] PR snapd#3667 closed: cmd: mark arch as non-reexecing distro [12:31] jdstrand: hey [12:31] jdstrand: I just requested a review on https://github.com/snapcore/snapd/pull/3662 [12:31] PR snapd#3662: interfaces: convert broadcom-asic-control to common iface [12:31] jdstrand: this is one of maaany such PRs that I will open [12:32] jdstrand: the context is that this will help us with the udev tagging mega-PR [12:32] jdstrand: as it will (hopefully) reduce it down to just the policy changes [12:32] jdstrand: I was thinking that for testing we could also make udev tagging non-optional [12:32] jdstrand: that is, to always construct a cgroup [12:32] jdstrand: but I would only enable this in 2.28 (2.29 more likely) [12:33] jdstrand: after we feel confident that interfaces are actually OK [12:33] jdstrand: then anything that breaks is going to be a clear indicator that udev tagging is missing [12:33] zyga-ubuntu: please don't always create a cgroup [12:33] zyga-ubuntu: you'll break docker and lxd [12:34] jdstrand: aha! [12:34] jdstrand: I dind't think about them [12:34] jdstrand: well, too bad, but I understand [12:34] PR snapd#3674 closed: cmd,tests: fix classic confinement confusing re-execution code (#3598) [12:34] mvo, access granted [12:34] I'm fine with spread tests for everything that uses a cgroup [12:34] mvo: thank you! [12:35] but that could take a while [12:36] 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] jdstrand: noted, I wanted to do it this way while *keeping* that other PR [12:37] jdstrand: so that we actually see the problem at hand being addressed there [12:37] 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] mvo: anything on the debian core bug? [12:38] mvo: I think we will still do rc8 but I'm happy that we will have more data at hand soon [12:39] 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] mvo: yes [12:39] well, just one really :) [12:39] but yes [12:39] PR snapd#3673 closed: packaging/arch: drop patches merged into master [12:39] zyga-ubuntu: no progress on this one [12:39] mvo: snap install hello [12:39] mvo: noted [12:40] zyga-ubuntu: we may need a rc8 for this and also for the issue that pstolowski is debugging [12:40] zyga-ubuntu: I mostly did rc7 to ensure the other issues we know about got fixed [12:40] good point [12:41] * zyga-ubuntu runs back into the legal hell [12:47] mvo, ok [12:47] I'll start with those [12:48] mvo: I'm wrapping up reviews (soon) and I'll jump to debian+core issue [12:49] 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] cachio: thanks, I try this now [12:49] mvo, I followed the instructions that federico wrote https://forum.snapcraft.io/t/core-snap-validation-process-at-beta-channel/1454 [12:49] cachio: hey [12:49] cachio: can you please qucikly look at https://travis-ci.org/snapcore/snapd/builds/261774010?utm_source=github_status&utm_medium=notification [12:49] zyga-ubu1tu, sure [12:49] cachio: I merged your fedora PR and now, it seems, is that fedora upgrade/basic fails [12:50] cachio: thank you! [12:55] 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] pstolowski: ok, this is the "missing install hook" error? it seems like those are also visible in spread, no? [12:57] zyga-ubu1tu, any idea why it could happened? https://paste.ubuntu.com/25262885/ [12:57] looking [12:57] cachio: maybe we have a wrng %dir entry somewhere [12:57] in the old version of snap-confine for fedora we had a directory there [12:58] but I think there may be an issue with it since it had mode 0000 and many tools choked on that === zyga-ubu1tu is now known as zyga-ubuntu [12:59] cachio: I will not be back for 2-3 more hours so I'm away from fedora [12:59] mvo, yes, missing install hook error [12:59] mvo, i don't think i saw it in spread tests i run locally [13:00]