[01:32] <mup> PR snapd#3511 opened: tests: shellcheck improvements for unit and completion tests <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/3511>
[02:47] <mup> PR snapcraft#1375 opened: tests: allow to filter tests in docker <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1375>
[08:13] <ppisati> guys, is there a way to use a ppa in snapcraft?
[08:19] <Chipaca> ppisati: https://forum.snapcraft.io/t/how-to-add-a-custom-ppa-to-snapcraft/266/4
[08:19] <Chipaca> ppisati: short version: no
[08:19] <Chipaca> ppisati: longer version: mmmm... no
[08:19] <Chipaca> :-p
[08:24]  * ppisati cries in a corner...
[08:35] <mvo> Chipaca: fwiw, I think I found the issue with the cannot update namespace error we talked about yesterday
[08:36] <mvo> Chipaca: I think the hardest part is fixing the tests :/
[08:36] <mvo> Chipaca: anyway, I'm on it
[08:36] <mvo> I think
[08:37]  * Chipaca hugs mvo
[08:37]  * Chipaca hugs ppisati too
[08:37]  * Chipaca goes back to beating streaming json chunks into submission
[08:37] <mvo> Chipaca: enjoy ! sounds like more fun than fighting tests
[08:37] <mvo> in the heat
[08:38] <Chipaca> I cannot confirm nor deny
[08:38] <Chipaca> it's actually cooler today
[08:38] <mvo> Chipaca: ha! lawyer?
[08:38] <Chipaca> overcast
[08:38] <Chipaca> mvo: :-) (also: no)
[08:38] <mvo> Chipaca: lucky you, its blazing hot here, hottest day of the year according to the forecast
[08:49] <pstolowski> fgimenez, hey, any idea about 'jq command not found' error on travis? afaict we always install this as a dependency?
[08:50] <fgimenez> pstolowski: nope, do you have a link?
[08:51] <pstolowski> fgimenez, https://travis-ci.org/snapcore/snapd/builds/244895313?utm_source=github_status&utm_medium=notification
[08:54] <fgimenez> pstolowski: it failed on ubuntu-core, you need to install the snap for it to work there, as in https://github.com/snapcore/snapd/blob/master/tests/main/auto-refresh/task.yaml#L4
[08:58] <pstolowski> fgimenez, ah, thank you. let me try that
[09:07] <mup> PR snapd#3512 opened: cmd: rework how cmd.InternalToolPath() works to ensure the right tool is used <Created by mvo5> <https://github.com/snapcore/snapd/pull/3512>
[09:21]  * Chipaca throws hands up in despair
[09:21] <Chipaca> mvo: it was going to be the hottest day, but then it changed its mind
[09:22] <Chipaca> it went with option B, thunderstorm
[09:32]  * pedronis early lunch + errands
[09:34]  * Chipaca wishes he could select on a reader and a writer
[10:14] <mvo> Chipaca: when you had the issues with snap-update-ns, did you had a reliable way to reproduce?
[10:14] <mvo> Chipaca: or was it happening at random for you? in manual testing or in spread as well?
[10:14] <Chipaca> mvo: not in spread
[10:14] <Chipaca> mvo: it'd happen when running snapd from master without installing all the bits from master, some of the time
[10:16] <Chipaca> mvo:
[10:16] <Chipaca> 017-05-24 12:02:59 <Chipaca>   - Remove security profile for snap "http" (x1) (cannot setup mount for snap "core": cannot update mount namespace of snap "core": cannot update preserve
[10:16] <Chipaca> d namespace of snap "core": cannot update snap namespace: not implemented)
[10:16] <Chipaca> 2017-05-24 12:03:22 <zyga>      Chipaca: you are using snapd from master but the rest from package
[10:16] <Chipaca> 2017-05-24 12:03:31 <zyga>      Chipaca: just buind and install snap-update-ns
[10:16] <Chipaca> 2017-05-24 12:03:35 <Chipaca>   ah ok
[10:17] <mvo> Chipaca: ta
[11:27]  * Chipaca gives up and goes for lunch
[11:46] <mup> PR snapd#3513 opened: asserts: open up and optimize Encoder to help avoiding unnecessary copying <Created by pedronis> <https://github.com/snapcore/snapd/pull/3513>
[12:18] <pedronis> it seems either there's a codecov bug or there's some code with non determinstic tests resulting in non-deterministic coverage
[12:18] <pedronis> I see coverage of interfaces/sorting.go for example going up and them depending on runs
[12:18] <pedronis> s/and them/and down/
[12:51] <mvo> jdstrand: niemeyer suggests "seccomp/bpf/*.src for the source files and "seccomp/bpf/*.bin"  for the binary files in the seccomp-bpf review. if you are happy with this as well, I will make it so. WDYT?
[13:05] <Chipaca> pedronis: standup?
[13:21] <niemeyer> mvo: Can you quickly jump back in the hangout for us to cover a detail in the bpf pr?
[13:21] <mvo> niemeyer: sure, joining
[13:26] <jdstrand> mvo: I commented in the pr a moment ago
[13:27] <jdstrand> mvo: https://github.com/snapcore/snapd/pull/3431#discussion_r123503280
[13:27] <mup> PR snapd#3431: interfaces: simplify snap-confine by just loading pre-generated bpf code <Critical> <Created by mvo5> <https://github.com/snapcore/snapd/pull/3431>
[13:30] <popey> morphis: do you know when the migration of snap-xdg-open will land? I have an app which depends on external links which breaks on non-ubuntu
[13:35] <morphis> popey: I would guess 2.28
[13:38] <niemeyer> jdstrand, mvo: Replied the reply
[13:38] <niemeyer> IRC-as-a-notification-service
[13:38] <niemeyer> IaaNS
[13:38] <jdstrand> mvo: that said, I didn't think that EnsureDirState() would be cool with a dir in there, but I see the seccomp code passes a glob that does not match 'bpf', so seems ok
[13:38] <jdstrand> hehe
[13:42] <mvo> jdstrand, niemeyer: so it would be /var/lib/snapd/seccomp/bpf/*.{src,bin}  (AIUI the original suggestion in https://github.com/snapcore/snapd/pull/3431#discussion_r123396337) *or* /var/lib/snapd/seccomp/profiles/bpf/*.{src,bin} ?
[13:42] <mup> PR snapd#3431: interfaces: simplify snap-confine by just loading pre-generated bpf code <Critical> <Created by mvo5> <https://github.com/snapcore/snapd/pull/3431>
[13:43] <niemeyer> mvo: The former, /bpf/*.src/bin
[13:43] <niemeyer> Argh
[13:43] <niemeyer> .../bpf/*.{src,bin} :)
[13:43] <mvo> niemeyer: thanks
[13:43]  * mvo will make it so
[13:43] <niemeyer> mvo: Otherwise you'd have to invent a new mechanism to not remove the old files
[13:44] <niemeyer> (as EnsureDirState takes on a single glob)
[13:44] <mvo> niemeyer: yes, was wondering about this too, I'm happy that we are in agreement)
[13:48] <popey> morphis: do you know when 2.28 will be released?
[13:48] <zyga> o/
[13:48] <morphis> popey: nope
[13:49] <zyga> o/
[13:49]  * zyga waves everyone good-bye from Spain
[13:49] <zyga> see you in Poland on Friday morning
[13:49] <morphis> zyga: safe trip!
[13:49] <zyga> morphis: sorry for being absent earlier, I forgot to notify you that I'm moving
[13:49] <morphis> zyga: np
[13:49] <zyga> morphis: thank you :)
[13:49] <morphis> popey: PR is still pending https://github.com/snapcore/snapd/pull/3260
[13:49] <mup> PR snapd#3260: cmd/snap: implement userd command as replacement for snapd-xdg-open <Created by morphis> <https://github.com/snapcore/snapd/pull/3260>
[13:51] <popey> morphis: ok, this is blocking a developer we've been talking to for some weeks now. :(
[13:51] <morphis> popey: I see
[13:52] <morphis> popey: does his snap work otherwise on other distros?
[13:52] <zyga> niemeyer, mvo, Chipaca, pedronis, fgimenez, pstolowski, cachio: see you all on Friday!!!
[13:52] <Chipaca> zyga: o/~
[13:52] <niemeyer> zyga: Have a great trip, and good luck with the move!
[13:52]  * zyga will miss spain a lot
[13:52] <popey> morphis: mostly, yes. xdg-open is the final thing blocking AIUI
[13:52] <cachio> zyga, enjoy it :)
[13:52] <zyga> niemeyer: thank you, I hope to land at home safely late after midnight
[13:52] <pstolowski> zyga, o/
[13:52] <niemeyer> morphis, popey: Will look into this today still
[13:53] <zyga> niemeyer: see you at the snandup tomorrow
[13:53] <niemeyer> zyga: o/
[13:53] <popey> it's a mail client, so it needs to do things like open file attachments
[13:53] <popey> thanks niemeyer
[13:53] <morphis> niemeyer: a code review would be nice but I need to a fix a few last things
[13:53] <niemeyer> morphis: Ah, okay, please ping me once you feel like it's ready then
[13:54] <fgimenez> zyga: enjoy and good luck! safe travels, see you soon
[13:54] <cachio> mvo, do you have the link to the snap-notify error?
[13:55] <mvo> cachio: yes, sorry, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-snappy-dev-image/yakkety/amd64/s/snapd/20170622_120316_4e91a@/log.gz
[13:55] <cachio> mvo, tx
[13:55] <mvo> cachio: I'm not sure how widespread this actually is, I think I saw it twice recently
[13:55] <cachio> ok, failing on yakkety
[13:55] <cachio> mvo, I'll take a look
[14:23] <cachio> mvo, which yakkety image do you use for the autopkgtests?
[14:24] <mvo> cachio: it comes from the machinery we use in autopkgtest, afaik it is created via buildvm-ubuntu-cloud
[14:25] <cachio> mvo, ok, tx
[14:30] <fgimenez> cachio: here are some details about how to generate images for different releases  and use them with the qemu backend https://github.com/snapcore/snapd/blob/master/HACKING.md#running-the-spread-tests
[14:30] <cachio> fgimenez, nice
[14:30] <cachio> thanks for the ingo
[14:30] <cachio> info
[14:36] <mup> PR snapd#3514 opened: wrappers: add SyslogIdentifier to the service unit files <Created by chipaca> <https://github.com/snapcore/snapd/pull/3514>
[15:09] <mvo> jdstrand: if you could have a look at the last few commits for seccomp-bpf, especially    	02a6d3f - that would be great. tests are still running but locally spread is almost finished (183/190) and happy so far
[15:09] <mvo> jdstrand: I also updated the snap-confine.rst a bit more to better reflect what its doing
[15:13] <jdstrand> mvo: sure
[15:23] <mvo> jdstrand: thanks for your comment, I don't have a strong opinion either
[15:25] <jdstrand> mvo: +1
[15:25] <mvo> fgimenez, cachio: do you have an idea why https://travis-ci.org/snapcore/snapd/builds/245474489?utm_source=github_status&utm_medium=notification fails? this is the seccomp-bpf-2.26 branch, it fails with some shellcheck errors, did we change something there recently?
[15:25] <mvo> jdstrand: \o/
[15:30] <fgimenez> mvo: no idea sorry, looking
[15:35] <mvo> fgimenez: thank you, maybe I just need to disable shellcheck for this particular file, slightly strange but I can also dig
[15:40] <fgimenez> mvo: there are a few PRs by cachio related to shellcheck up https://github.com/snapcore/snapd/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aopen%20shellcheck but nothing seems to have landed lately https://github.com/snapcore/snapd/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20shellcheck
[15:41] <mvo> fgimenez: thanks, I see what I can figure out
[17:14] <pedronis> mvo: we weren't running shellcheck at all I think until recently
[17:17] <gouchi> hi
[17:18] <gouchi> where is the source for ubuntu core for creating the db410c image ?
[17:19] <niemeyer> fginther: Didn't we move the static checks into a spread task as well?
[17:19] <niemeyer> fginther: Sorry, bad tab completion on the nick
[17:19] <gouchi> it should be here https://code.launchpad.net/~ubuntu-core-dev ?
[17:20] <nacc> gouchi: that's the code page for the ubuntu core dev team
[17:20] <nacc> gouchi: unrelated to 'ubuntu core'
[17:20] <nacc> gouchi: confusingly :)
[17:20] <gouchi> ah ok :)
[17:30] <cachio> mvo, about the error in the test snappy-notify
[17:31] <cachio> it is failinf bacasue for some reason sometimes is taking more time to start the service
[17:31] <cachio> mvo, in the test that failed here, it tool 3 seconds from the "restart into" until it was ready
[17:32] <cachio> mvo, we could retry during 5 seconds instead of make a single check
[17:32] <cachio> mvo, what do you think?
[18:02] <mvo> cachio: sounds good
[18:02] <mvo> cachio: thanks for investigating!
[18:02] <cachio> mvo, np
[18:22] <pedronis> are spread tests on linode broken atm? it seems they cannot get any machines
[18:22] <cachio> pedronis, seem to be broken
[18:23] <cachio> I cant run neither
[18:23] <cachio> Discarding linode:ubuntu-16.04-64 (Spread-33), cannot connect: cannot connect to linode:ubuntu-16.04-64 (Spread-33): ssh: handshake failed: ssh: unable to authenticate, attempted methods [password none], no supported methods remain
[18:23] <cachio> pedronis, do you see that error?
[18:24] <pedronis> yes
[18:24] <cachio> niemeyer, any idea?
[18:49] <mup> PR snapd#3515 opened: tests: fix snapd-notify when it takes more time to restart <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/3515>
[19:04] <kyrofa> niemeyer, can I have the power to make a forum post a wiki?
[19:04] <kyrofa> Or would you prefer that we ask?
[19:08] <niemeyer> kyrofa: Done.. as a general recommendation, wiki posts are generally not phrased in personal terms, otherwise even being a wiki people will end up not touching them
[19:08] <niemeyer> cachio: Yeah, on it already
[19:08] <niemeyer> cachio: Linode is broken
[19:08] <niemeyer> cachio: Their support is looking into the issue
[19:08] <kyrofa> niemeyer, thanks
[19:30] <cachio> niemeyer, thanks
[19:33] <niemeyer> mvo: I don't have news from Linode itself, but retrying seems to have worked now
[19:33] <niemeyer> https://travis-ci.org/snapcore/snapd/jobs/245873418
[19:33] <mvo> niemeyer: nice
[19:54] <mup> PR snapd#3516 opened: asserts: implement FindManyTrusted as well <Created by pedronis> <https://github.com/snapcore/snapd/pull/3516>
[20:01] <mup> PR snapd#3431 closed: interfaces: simplify snap-confine by just loading pre-generated bpf code <Critical> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3431>
[20:15] <mup> PR snapcraft#1350 closed: rust plugin: Add support for cross-compilation <Created by kalikiana> <Merged by elopio> <https://github.com/snapcore/snapcraft/pull/1350>
[20:39] <madprops> Hi
[20:39] <madprops> I have a question
[20:39] <madprops> What happens when applications installed through snappy, like Telegram, have automatic updates?
[20:39] <madprops> Their own updater
[20:40] <madprops> Does it update, and then snappy tries to update it again?
[20:40] <kyrofa> madprops, it probably depends on how the updater is written. Snaps are read-only, so they won't be able to self-update in place, for example
[20:41] <madprops> So it brakes all autoupdates
[20:41] <madprops> autoupdaters*
[20:41] <madprops> breaks*
[20:41] <madprops> something doesn't feel right about that
[20:42] <madprops> unless linux versions by convention don't come with autoupdaters
[20:43] <kyrofa> madprops, how would it work if one were to install telegram from, say, a deb?
[20:44] <madprops> Well I'm not sure but, I can tell you that in Windows I just install an exe, and autoupdaters work, they ask you for admin permissions to upgrade
[20:45] <madprops> It would be cool if snaps become like exes
[20:46] <madprops> big applications have autoupdaters ... and the other ones you just upgrade when needed (downloading a new exe)
[20:46] <kyrofa> madprops, the idea is to bring that auto-update goodness to everyone, not just those who create the infrastructure for it
[20:48] <madprops> yes that's nice too
[20:48] <madprops> something that surprised me though
[20:48] <madprops> was there there seemed to be no way to disable autoupdates, just select "good hours" to update
[20:48] <madprops> very windowslike
[20:49] <kyrofa> Yeah I'm not sure why that is either, honestly
[20:49] <niemeyer> If you open a forum topic I'm happy to provide details
[20:54] <kyrofa> Perhaps this is the thread to read: https://forum.snapcraft.io/t/disabling-automatic-refresh-for-snap-from-store/707
[20:55] <mup> PR snapd#3513 closed: asserts: open up and optimize Encoder to help avoiding unnecessary copying <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/3513>
[21:02] <niemeyer> kyrofa: Nice, it's even there already :)
[21:03] <niemeyer> forum++
[21:06] <kyrofa> niemeyer, here's a nuanced version: https://forum.snapcraft.io/t/delaying-snap-refreshes-programatically/1085
[21:39] <mup> PR snapcraft#1345 closed: deltas: Improved message returned when delta is too big <Created by gsilvapt> <Merged by elopio> <https://github.com/snapcore/snapcraft/pull/1345>
[23:52] <mup> PR snapcraft#1366 closed: cli: Add --version command <Created by sparkiegeek> <Merged by elopio> <https://github.com/snapcore/snapcraft/pull/1366>