=== markusfluer1 is now known as markusfluer === JanC is now known as Guest31516 === JanC_ is now known as JanC === chihchun_afk is now known as chihchun [06:57] PR snapd#2921 closed: releasing package snapd version 2.22.6 [07:03] PR snapd#2922 opened: many: merge 2.22.6 back into master [07:36] <_prasen_> https://github.com/mectors/sensortag [07:36] <_prasen_> hi [07:36] <_prasen_> while building this snapcraft filw [07:37] <_prasen_> i get a error of property does not match the schema [07:39] <_prasen_> Issues while validating snapcraft.yaml: The 'parts/move/filesets/sensortag-in' property does not match the required schema: 'bin/sensortag-in' is not of type 'array' [08:21] PR snapd#2893 closed: tests: bail out if core snap is not installed [08:21] PR snapd#2917 closed: osutil: remove duplicate build_id from other branch [08:37] hi [08:37] _prasen_: probably outdated repo, snapcraft is changing over time [08:44] <_prasen_> how do i fix this? [08:44] <_prasen_> should it be of type string? [08:44] <_prasen_> is this a problem of vim? [08:47] _prasen_: no, this is not related to vim [08:47] _prasen_: I don't know, sorry, just waking up after long evening work [08:48] _prasen_: I'd suggest yu ask mectors to correct this repository [08:48] <_prasen_> hahahhahaha [08:48] <_prasen_> i am like starting my day [08:48] <_prasen_> though its well past noon [08:48] <_prasen_> working with yaml for first time [08:49] <_prasen_> so saw that there could be errors due to ansi indent [08:49] <_prasen_> zyaga: will do that [08:49] <_prasen_> zyga* [08:49] <_prasen_> zyga: ty _/\_ === chihchun is now known as chihchun_afk [08:51] _prasen_: good luck :) [08:54] mvo: do you think you could do a 2nd review of https://github.com/snapcore/snapd/pull/2848 [08:54] PR snapd#2848: cmd/snap-update-ns: add compare function for mount entries [08:54] mvo: it's been out for 9 days and I'd like to push forward === chihchun_afk is now known as chihchun [09:29] PR snapd#2477 closed: interfaces/builtin: first cut at repowerd interface [10:45] PR snapd#2818 closed: Allow specifying another store via commandline option for the download command === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [10:57] PR snapd#2847 closed: tests: enable docker test [11:01] uhm [11:01] what am i doing wrong? [11:01] https://travis-ci.org/snapcore/snapcraft/jobs/204522771 [11:04] ogra_: i know you are not the right person but, do you know who's the snapcraft/store guy here for this ^? [11:04] mvo: you too ^ [11:05] ppisati, fgimenez [11:05] fgimenez: ^ [11:05] he's the master of tests :) [11:05] ppisati: sergiusens is usually the goto person for snapraft* but let me have a look [11:05] yeah, it's more like 'it explodes while trying to download a snap' [11:06] ppisati: this looks like the store was giving a connection reset during the tests [11:06] ppisati: so a simple retry, sometimes we have these problems (store or cdn, one of those) [11:06] ppisati: I can restart the job for you if you want [11:06] PR snapd#2848 closed: cmd/snap-update-ns: add compare function for mount entries [11:07] mvo: can i do it myself? so i won't bother anyone next time [11:08] ppisati: I'm not sure, it may well be that you can't and only people with certain privs in the snapcore group can. I restarted it now [11:08] mvo: ta === chihchun_afk is now known as chihchun [11:15] jdstrand: Easy one, maybe: snapd#2855 [11:15] PR snapd#2855: interfaces/builtin: add intel realsense udev rules into camera interface [11:18] PR snapd#2836 closed: release: assume higher version of supported distros will still work [11:21] PR snapd#2857 closed: interfaces/builtin: add /boot/uboot/config.txt access to core-support [11:27] PR snapd#2817 closed: many: switch channels on refresh if needed [11:45] <_prasen_> working behind corporate proxy, while running snapcraft a part needs npm to install a sdk. to pass the proxy variables to npm we need to set proxy and https-proxy var's in .npmrc file [11:46] <_prasen_> and for npm install we have to pass the flags : --without-ssl , --insecure [11:46] <_prasen_> how do i tell snapcraft to take these flags [11:58] PR snapd#2839 closed: debian/tests: map snapd deb pockets to core snap channels for autopkgtest [12:06] ogra_, ppisati hey :) for snapcraft-related issues about tests and CI elopio is the right person to ask [12:06] thanks [12:13] PR snapd#2923 opened: cmd/snap-update-ns: add function for sorting mount entries [12:32] PR snapd#2870 closed: tests: failover test for rc.local crash === chihchun is now known as chihchun_afk [12:38] niemeyer: ack [12:39] morphis: hey, is there a slot implementation of upower-observe? [12:40] jdstrand: o/ [12:41] hey zyga :) [12:41] ppisati: looks like your test is green now [12:44] jdstrand: yes, we added that recently [12:45] morphis: right. I mean, do you have a snap that slots upower-observe [12:45] yes we do [12:46] jdstrand: but not yet in stable [12:46] snap install --candidate upower [12:46] morphis: great, thanks! [12:47] jdstrand: any specific reason you're asking for or just for reference? [12:49] morphis: I am preparing a PR to mediate socket(PF_NETLINK, ...) and saw that upower uses udev, and I need to add 'socket PF_NETLINK - NETLINK_KOBJECT_UEVENT' to its PermanentSlot policy and want to test that it is enough [12:50] ah ok [12:54] morphis: there are a few slots that you guys wrote that I've made adjustments to and will ping you in the PR [12:55] jdstrand: thanks [13:03] jdstrand: did you see that error I reported for zesty yesterday? [13:04] PR snapd#2922 closed: many: merge 2.22.6 back into master [13:04] zyga: I did. I commented in the bug [13:04] jdstrand: it's not an urgent thing but I'd like to fix it as zesty freezes and it breaks all the tests [13:04] jdstrand: thank you! [13:05] jdstrand: I'll try the kernel that jj recommended [13:27] PR snapd#2833 closed: many: allow core refresh.schedule setting [13:28] PR snapd#2810 closed: snap: use snap-confine from the core snap [13:28] PR snapd#2874 closed: kmod: added Specification for kmod security backend === chihchun_afk is now known as chihchun [13:45] PR snapd#2878 closed: data/selinux: merge SELinux policy module [13:45] 🎉 [13:46] zyga: this means that now proper snapd selinux integration can begin [13:46] since we have "official" labels for things :) [13:46] Son_Goku: :-) [13:46] Son_Goku: I'm happy to see this [13:46] Son_Goku: I'm sleepy after 2AM release last night [13:46] Son_Goku: but with the main fire out I think next week will see some releases [13:47] I'm thinking that we should regenerate the packaging from gofed [13:47] Son_Goku: though I'm on holidays since Tue [13:47] Son_Goku: all of it? [13:47] Son_Goku: for snapd or for deps? [13:47] snapd [13:47] there's been a lot of churn and I don't know what things are anymore :( [13:47] Son_Goku: we can, I think that's ok [13:48] now that the SELinux policy is merged into the repo, I can start rebasing my packaging on that [13:48] :D [13:49] zyga: do we have a file that declares what our deps are in snapd? [13:49] I'm not completely familiar with how this works in golang [13:49] Son_Goku: yes, it's called... [13:49] Son_Goku: vendor/vendor.json [13:50] ah, so it's in the vendor directory [14:18] jdstrand: I tried to push a php-based snap to the store and got this: [14:18] found errors in file output: unusual mode 'rwx-wx-wt' for entry './var/lib/php/sessions' [14:19] I didn't do anything special, and php is installed via stage-packages [14:21] mhall119: what is the name of the snap? [14:24] laravel-mhall119 [14:25] mhall119: can you request manual review in the store? [14:25] I can, but I also want to make sure this doesn't happen for every php-based snap if we can avoid it [14:25] mhall119: I understand. I will fix the review tools for that [14:26] rwx-wx-wt is unusual, but it doesn't hurt anything [14:27] jdstrand: requested [14:44] fgimenez: can you help me with some snapcraft tests? [14:46] ppisati, i can try but probably better to ask elopio, i'm not actively working on them [14:47] fgimenez: k [14:47] elopio: ^ [14:53] PR snapd#2924 opened: interfaces: specs for apparmor, seccomp, udev [14:54] PR snapd#2891 closed: interfaces/udev: added spec [14:55] PR snapd#2890 closed: interfaces/apparmor: add spec [15:00] PR snapd#2883 closed: seccomp: added Specification for seccomp backend [15:01] hey kyrofa :) i'm trying to do some tests on the nextcloud image, have a minute for some questions? [15:02] jdstrand: do you need a bug report for that unusual file permission? [15:07] jdstrand: can I add the snippet that will make the zesty regression no break all the PRs for snapd? [15:07] jdstrand: (along with a note and a bug reference) [15:07] jdstrand: note that this is just for jailmode on classic snaps so pretty isolated === gaughen_ is now known as gaughen === mup_ is now known as mup === mup_ is now known as mup [15:46] sergiusens: hey [15:46] have you made any progress on the repo refactor thing? === mup_ is now known as mup [15:54] fgimenez, ah, sorry, responded to your internal ping first, heh [15:54] kyrofa, np! thanks :) === mup_ is now known as mup [16:00] ppisati: hey! [16:01] ppisati: so https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652504?comments=all is apparently hitting one of the demos for MWC [16:01] Bug #1652504: Recent updates broke Ubuntu on Raspberry Pi 3

[16:01] ppisati: I'm not sure they need video output (checking with them), but they've just passed this bug to me [16:04] ppisati: ok, it's not critical, they're just giving us a heads up [16:04] PR snapd#2925 opened: [WIP] interfaces: migrate existing intarfaces to use new kmod and seccomp spec === mup_ is now known as mup [16:10] lool: i thought ryan fixed that already [16:11] ppisati: do yo know where the fix is? [16:11] lool: actually, it doesn't break video, your board won't boot at all [16:11] lool: wait wait [16:11] lool: that bug, was because ryan's image didn't have the correct address for the dtb [16:11] ok [16:12] lool: if you are hitting that bug, your board won't boot at all [16:12] lool: but you mention a problem with video output [16:12] ppisati: that's what they said [16:12] I'm proxying here [16:13] lool: ok, if you want to loop me in any conversation [16:13] ppisati: so the workaround/fix is to correct DTB addr and we'll land that soon and can be applied manually in the mean time? [16:13] lool: i can test if that bug was fixed in the meantme [16:13] ppisati: we're on their slack [16:13] I've invited folks here [16:13] lool: let me reinstall the image, so i can check what's the status [16:14] ppisati: thanks man [16:23] PR snapcraft#1158 closed: packaging: snapcraft as a snap === mup_ is now known as mup === mup_ is now known as mup [16:29] @ppisati hi there, @lool passed on the word that we had trouble with video after updating our ryan's pi3 image to kernel 4.4.0-1042-raspi2 [16:29] mdye: No such command! [16:30] bad slack habits :) [16:31] mdye: Hey! [16:31] lool: ahoy! [16:31] mdye: fb or mir? [16:32] ppisati: ^ mdye is setting up a jetson tx1 + pi3 boards demo for MWC; he's also a really awesome guy :-) [16:32] ha, thx [16:33] ppisati: so the jist is we build a pi3 image from ryan's base in a chroot; I use FLASH_KERNEL_SKIP=1 to get kernel updates installed successfully in the chroot [16:33] mdye: ok [16:33] the config.txt on the updated pi3 has device_tree_address=0x100 and device_tree_end=0x8000 (which I think are the original addresses from earlier images) [16:35] the result is a system that will boot the kernel, but the kernel command line "console=tty1" isn't applied such that the console never outputs messages after uboot hands control over to the kernel [16:37] mdye: uhm, that is weird [16:37] mdye: is you did a dist-upgrade, you should get a new firmware too [16:37] *if [16:37] mdye: that would move the dtb address around, and your board wouldn't boot then [16:37] mdye: i'm reinstalling an image to check, hold on [16:38] ok, thx === mup_ is now known as mup [16:43] PR snapd#2861 closed: [WIP] interface hooks: expose attrs to the interface API, snapctl enhancements (step #4) [16:43] PR snapd#2896 closed: httputil: copy some headers over redirects [16:43] PR snapd#2925 closed: [WIP] interfaces: migrate existing interfaces to use new kmod and seccomp spec === mup_ is now known as mup [16:55] Bug #1667359 opened: After a reboot store was not accessible [16:57] PR snapd#2923 closed: cmd/snap-update-ns: add function for sorting mount entries [16:59] jdstrand: hey === mup_ is now known as mup [17:04] Bug #1667385 opened: devmode flag disappears after disabling+re-enabling a snap [17:05] jdstrand: can you please have a look at https://github.com/snapcore/snapd/pull/2827 [17:05] PR snapd#2827: cmd: add helpers for mounting / unmounting [17:06] jdstrand: I think it is good to land now [17:06] jdstrand: and I waaaaant it to land :) === mup_ is now known as mup [17:08] jdstrand: the new patches are: https://github.com/snapcore/snapd/pull/2827/commits/6573f698a22db592006cf6af7d5284cf66a891e4 and https://github.com/snapcore/snapd/pull/2827/commits/9e24bee9f0cb94aef73c23667fd80364db66d3bb [17:08] PR snapd#2827: cmd: add helpers for mounting / unmounting === mup_ is now known as mup === mup_ is now known as mup [17:14] PR snapd#2872 closed: tests: do not use core for "All snaps up to date" check [17:14] Hi - question about ubuntu Core. I have a working machine in KVM, and when I want to ssh into it, it asks key passphrase. When I enter it correctly, it asks users password, which I don't know... any ideas? [17:14] slunatecqo, you uploaded your SSH public key to your SSO account, etc.? [17:15] kyrofa: yes - the key is set up - after I enter its passphrase it asks for user password [17:15] slunatecqo: is the 'it' ssh? ssh -vvv may help see if it rejected your key, if so [17:15] slunatecqo, which implies to me the key you're using doesn't match up to a key authorized on the device [17:16] slunatecqo, indeed, try nacc's advice [17:17] zyga: I'll add it to the list. not sure it will be today, but will be able to first thing next week (off tomorrow) [17:17] nacc: yeah... thats it.. the passphrase should be blank, but for some reason ssh says "debug2: no passphrase given, try next key" [17:21] jdstrand: I'm off next week [17:21] jdstrand: if you can I'd appreciate it, the diff is tiny [17:21] * zyga back to other things [17:21] slunatecqo: it means that it tried your ssh key (which was encrypted) but they it tried password auth [17:22] slunatecqo: the key associated with your account is not the key you've used [17:22] zyga: yeah. I understand.... thanks === chihchun is now known as chihchun_afk [17:29] PR snapd#2873 closed: tests: several improvements to the nested suite [17:30] PR snapd#2926 opened: cmd/snap-update-ns: move test data and helpers to new module [17:31] Ok - one more. I just installed docker in fresh UbuntuCore. running any container gives me "container command XXXX could not be invoked" [17:32] slunatecqo: not sure about that, what is your environment? [17:33] environment? [17:33] I am running ubuntu-core-16-amd64.img using qemu-KVM [17:33] mmm [17:33] slunatecqo: can you please report that [17:33] slunatecqo: I'm sure people will want to look at it and fix it [17:35] where? launchpad bugs? [17:35] slunatecqo: yes please, on launchpad.net/snappy [17:41] Bug #1667408 opened: docker container command XXXX could not be invoked [17:41] slunatecqo, lool might have some thoughts if he's around [17:42] kyrofa: is it ok to ask directly him? on some IRCs it is not... [17:42] slunatecqo: which docker is this? [17:42] slunatecqo: 1.13? [17:42] slunatecqo, I sorta did ;) [17:42] slunatecqo: 1.13 is known broken unfortunately [17:42] lool: Docker version 1.11.2, build v1.11.2-snap-38fd0d3 [17:43] slunatecqo, not the best to directly ping people for generic questions, but in this case I know lool is The Docker Guy [17:43] kyrofa: thank you :-) [17:43] slunatecqo: are you on classic or on core? [17:44] KVM image from here https://developer.ubuntu.com/core/get-started [17:44] lool: so I guess core :D [17:44] Yes [17:46] slunatecqo: how are you installing and running? [17:47] slunatecqo: my whole knowledge is recap-ed in https://docs.google.com/document/d/1JHa6tkuR9PtpnAVVmAJIAKuyKBy8E9ZkvG5Wbc6HZSY/edit#heading=h.j2sflymhgsj8 [17:47] which might be slightly out of date [17:47] it's also possible that some regressions occurred [17:47] https://bugs.launchpad.net/snappy/+bug/1667408 here is the bug reported [17:47] Bug #1667408: docker container command XXXX could not be invoked [17:47] basically just snap install docker [17:48] ah - that will be it... the image is armhf? [17:49] no... doesnt solve the problem.. [17:53] lool: have to leave now for few minutes. Could you write ideas to the bug on launchpad? [18:09] slunatecqo: I suggest you open a bug against github.com/docker/docker and link it back on Launchpad [18:09] slunatecqo: docker is directly publishing the snap [18:10] slunatecqo: I wont have time to debug this this week and am travelling the next 2.5 weeks [18:10] is there any way to determine when the next refresh check is scheduled? [18:11] slunatecqo: I dont have a clean Core environment handy, but I did give this a try on classic and it worked there: http://paste.ubuntu.com/24054379/ [18:11] slunatecqo: so it's probably specific to core [18:31] PR snapd#2927 opened: cmd: add .indent.pro file to the tree [18:56] pmcgowan: hey, there are some controls for that coming [18:56] pmcgowan: it's mostly implemented [18:56] pmcgowan: but not released yet [18:56] Bug #1606674 changed: Unable to drive Adruino over USB from Arduino IDE snap

[18:56] pmcgowan: you can set schedule in a very detailed way [18:56] zyga,ok, it seems one of my systems runnign xenial isnt doing refreshes [18:57] zyga, wondering how to debug [18:57] pmcgowan: what's the version of snapd? [18:57] its got core 16.04.1 [18:57] 2.22.3 snapd [18:57] jdstrand, raw-usb doesn't seem to cover /dev/ttyUSB*, right? [18:57] pmcgowan: what does "snap info core" say? [18:58] zyga, http://pastebin.ubuntu.com/24054592/ [18:58] refresh --list shows 8 snaps [18:59] wow [18:59] don't refresh yet please [18:59] one sec [19:00] pmcgowan: can you pastebin snap changes [19:00] zyga, http://pastebin.ubuntu.com/24054598/ [19:00] not very interesting [19:01] kyrofa: correct. it allows access to /dev/bus/usb/*, not /dev/.... /dev/ttyUSB* is covered by the serial-port interface [19:01] pmcgowan: can you run journalctl -ux snapd [19:01] anything broken? [19:01] jdstrand, which again is gadget only [19:01] today, yes [19:01] jdstrand, talking about bug #1606674 here [19:01] Bug #1606674: Unable to drive Adruino over USB from Arduino IDE snap

[19:02] kyrofa: we need hotplug [19:02] zyga, yes. But I don't see that on the horizon [19:02] zyga, http://paste.ubuntu.com/24054608/ [19:02] And this has been an issue from the beginning [19:03] zyga, assume you meant -u [19:03] zyga, we need something to unblock [19:03] kyrofa: I think it is on the horizon. it was discussed as important in The Hague. best to ask JamieBennett on the priority [19:04] pmcgowan: -ux is for failures but this is good [19:04] zyga, ah, yes no matches [19:04] kyrofa: niemeyer said in The Hague that he would design hotplug and then present it for review. I don't know where that fell in the prioritization discussions after [19:04] pmcgowan: systemctl status snapd.refresh.timer [19:05] kyrofa: I think we need to work on hotplug and not to stopgaps [19:05] kyrofa: also, this should work in devmode. https://bugs.launchpad.net/snapd/+bug/1606674/comments/2 [19:05] Bug #1606674: Unable to drive Adruino over USB from Arduino IDE snap