=== chihchun_afk is now known as chihchun === rumble is now known as grumble [07:25] PR snapd#3532 opened: Support snap title field (localized short name) [07:30] good morning [07:34] PR snapd#3529 closed: interfaces: allow snaps to use the timedatectl utility [08:14] PR snapd#3533 opened: tests: extend find-private test to cover more cases [08:15] PR snapcraft#1382 opened: rust: Make libc configurable === chihchun is now known as chihchun_afk [08:53] PR snapd#3534 opened: tests: shellcheck improvements for tests/main tasks - first set of tests === JamieBen_ is now known as JamieBennett [08:58] ppisati, https://bugs.launchpad.net/raspbian/+bug/1646961 ... that affects our raspi2 kernel too, perhaps we could ship the patch ? [08:58] Bug #1646961: brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [09:15] ogra_: i assigned it to me, i'll give it a look ASAP [09:16] * ogra_ hugs ppisati [09:16] mainly cosmetic ... (i dont think it has any technical influence) === fnordahl_ is now known as fnordahl === ahasenac` is now known as ahasenack === ahasenack is now known as Guest52111 [11:48] PR snapcraft#1383 opened: autotools: Enable cross-compilation support === didrocks1 is now known as didrocks [12:36] jdstrand: silly question, in artful for seccomp_get_syscall_from_name("socket") on i386 I get -101 which AIUI is a way by libseccomp to say "it's complicated". is there a way to get from there to the real syscall or is that the wrong way to get a systemcall number from a name [12:55] jdstrand: nevermind, I think i figured it out, reading the libseccomp was instructive enough [13:07] mvo: ah, good. is there a particular problem you are seeing? [13:09] jdstrand: the problem is in 3535, I see a build failure in artful because in the tests I try to resolve a syscall by name and get a negative number [13:09] PR snapd#3535 opened: snap-seccomp: fix snap-seccomp tests in artful === heber_ is now known as heber === shadeslayer_ is now known as shadeslayer [13:43] mvo: oh, wow. I think socket will be the only one of these that are weird and I suspect it is related to socketcall === rharper` is now known as rharper [13:51] PR snapcraft#1384 opened: Support yaml merge tags [13:55] jdstrand: exactly, it is socket/socketcall when the bpf is generated [14:00] mvo: ok 'cool'. yeah, that is the only syscall I've seen that is weird like that [14:16] jdstrand: HELLO [14:48] Chipaca: hi! === heber is now known as heber_lunch [15:09] jdstrand: :-) === kwmonroe_ is now known as kwmonroe === nacc_ is now known as nacc === heber_lunch is now known as heber === dpb1_ is now known as dpb1 [15:51] PR snapcraft#1335 closed: errors: Descriptive error message for bad parts named with uppercase … === Guest52111 is now known as ahasenack [16:14] PR snapd#3528 closed: Use RFC3339 time format for refresh times [16:21] niemeyer, 2017-06-27 09:59:37 Cannot allocate linode:ubuntu-16.04-64: cannot boot linode:ubuntu-16.04-64 (Spread-60): linode disk /dev/sda not ready to boot. Please contact support. [16:21] niemeyer, this is happening today in linode [16:25] cachio: Thanks, reported [16:25] niemeyer, yaw [16:57] PR snapd#3527 closed: hooks: support for revert hook [16:58] what's the best/proper way to unset snap config? i've been telling people to do it by setting to null, e.g. `snap set kube-apiserver runtime-config=null` [16:59] which worked for me before, but i guess someone hit a bug with that [17:05] PR snapd#3523 closed: tests: fix for create-key task to avoid rng-tools service ramains alive [17:12] PR snapd#3535 closed: snap-seccomp: fix snap-seccomp tests in artful === wxl_ is now known as wxl [23:59] Bug #1697880 changed: Add "search" as an alias for "find" in snap command