ahoneybunmhall119, do you have that geany snap around?00:40
ahoneybunI'm learning python and the book recommends it00:40
ahoneybunI'm trying to snap a lot of things away lol00:40
liuxgis docker supported on 16.04 core?03:30
liuxgdoes anyone know how to compile a armhf version of a snap?04:03
mhall119ahoneybun: I have an amd64 binary if you want it04:19
firstofthe300Hey guys05:03
firstofthe300I am working on my first snap package05:03
firstofthe300its a Mono app (please no flame...I didn't pick the language)05:03
firstofthe300I don't see an xbuild plugin05:04
firstofthe300anybody have an idea on how to get around that issue?05:04
mupPR snapd#1733 opened: interfaces: add lxd-support interface <Created by mvo5> <https://github.com/snapcore/snapd/pull/1733>06:49
mupPR snapd#1720 closed: interfaces: add lxd-support interface <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1720>06:57
mupPR snapd#1732 closed: many: respect dirs.SnapSnapsDir in tests <Created by zyga> <Conflict> <https://github.com/snapcore/snapd/pull/1732>06:57
mupPR snapd#1734 opened: boot: add missing udevadm mock to fix FTBFS <Created by mvo5> <https://github.com/snapcore/snapd/pull/1734>07:14
liuxglool, when I run the classic.create command on 16.04 desktop, I get the error like chroot: failed to run command '/var/lib/classic/enable.sh': No such file or directory, what could be the problem for it? http://paste.ubuntu.com/23084232/07:15
loolliuxg: is this the classic snap from edge?07:17
loolliuxg: also, you need to sudo classic.create07:18
liuxglool, yes, I installed it by using the command "sudo snap install --devmode --edge classic" on 16.0407:18
loolliuxg: oh on 16.04 desktop? I'm not sure that's supported; I guess it could work there, but there might be bugs07:19
liuxglool, in fact, I switched to root user, and I ran the command under root.07:19
liuxglool, so, do you mean that it only works for arm devices?07:20
loolliuxg: it might only work on Ubuntu Core images07:20
liuxglool, OK. I got it. thanks. After I run the classic.create, then follow by classic.shell. I can start to install the development env there, right? Sorry, I never did it before. I might need to get an arm device to have a try.07:21
loolliuxg: yes, you basically get a chroot where you can install stuff07:22
loolliuxg: it just wont start any services on boot or such07:22
liuxglool, nice. I think this could be the easist way to cross compile. Many thanks for your help!07:22
loolliuxg: pleasure07:23
mupPR snapd#1734 closed: boot: add missing udevadm mock to fix FTBFS <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1734>07:41
loolelopio, ysionneau: I tried building a snapweb snap for armhf on a rpi3 running xenial, but I failed with: http://paste.ubuntu.com/23084299/07:52
loolelopio: How had you built the amd64 one?07:52
loolI followed the README.md instructions07:53
dz0nylool: phantomjs cannot run under arm07:54
dz0nyyou have to manually compile phantomjs with specific patches07:55
looldz0ny: argh07:55
looldz0ny: oddly, we used to have builds for this, do you know which change caused this? and do you have a recipe for building phantomjs?  O:-)07:55
dz0nylool: https://github.com/ab77/beastcraft-telemetry/blob/master/grafana-armhf/README.md#build07:55
dz0nythis might help you07:55
dz0nyI was asking in mailing list of how people handle different architectures and building snaps07:57
dz0nyand no one replied07:57
dz0nythe problem is that you need totally different declaration for devices too07:57
dz0nyand snapcraft is not ready for that07:57
looldz0ny: what do you mean for "declaration for devices"?07:58
dz0nydifferent paths, libs, patches etc07:58
dz0nyin snapcraft07:58
looldz0ny: oh you mean for cross-building?07:59
dz0nyaka the snapcraft.yaml for ffmpeg on amd64 wont compile on arm07:59
loolI dont quite get the link with snapcraft; this is with the node plugin pulling deps, I dont believe snapcraft is aware of phantomjs specifically07:59
loolah there's no way to express build differences between host arches in snapcraft.yaml08:00
dz0nybecause environment is different08:00
looloutside of your own plugins / upstream build system08:00
looljustinmcp_: heya08:01
looljustinmcp_: did you by any chance poke at snapweb recently? did you manage to build it for armhf?08:02
loolelopio: nevermind, saw your https://bugs.launchpad.net/snapweb/+bug/161628008:11
mupBug #1616280: building on armhf fails because of phantomjs <snapweb:New> <https://launchpad.net/bugs/1616280>08:11
mupPR snapd#1714 closed: many: hook in start of code to fetch/check assertions when installing snap from store <Critical> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/1714>08:16
looldz0ny: unfortunately I couldn't find a corresponding libicui18n.so.48 to run the prebuilt phantomjs binary there  :-/08:20
mupPR snapd#1735 opened: tests: fixes to make the ubuntu-core-16 image usable with -keep/-reuse <Created by mvo5> <https://github.com/snapcore/snapd/pull/1735>08:26
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
liuxghas anyone successfully booted raspberry pi2? I flashhed my raspberry 2 device at the instructions at https://developer.ubuntu.com/en/snappy/start/raspberry-pi-2/ I cannot see the HDMI output09:09
ograliuxg, there should definitely be a login prompt after a while ... boot output goes to serial though09:10
liuxgogra, oh, my godness. I do not have a serial cable for it.09:11
liuxgogra, so HDMI has no output, right?09:11
ograHDMI has output09:11
ograjust no boot messages09:12
liuxgogra, I connect it to my DELL monitor, there is no message at all. do you mean, I need to buy a serial cable for it?09:12
ograoh, wait, you dont use a snappy image ?09:12
* ogra just saw the link09:12
liuxgogra, I flashed it at https://developer.ubuntu.com/en/snappy/start/raspberry-pi-2/09:13
ograright, i thought you run a snappy image ... the server image might not enable HDMI, not sure about that09:13
liuxgogra, is that the ubuntu core image? or it is a just a classic ubuntu?09:13
tvossniemeyer: o/09:13
ograthe one described on that page is ubuntu server09:14
ograhttp://people.canonical.com/~mvo/all-snaps/16/ has the experimental snappy images09:14
liuxgogra,  so, I can use the same instructions to flash the snappy image?09:14
ograliuxg, i use: xzcat all-snaps-pi2.img.xz | sudo dd of=/dev/sdc bs=32M09:15
ogra(with sdc being my SD card reader)09:15
liuxgogra, OK, many thanks for your help on this. I will flash my raspberry 2 device09:15
mupPR snapd#1736 opened: tests: port integration tests to spread <Created by mvo5> <https://github.com/snapcore/snapd/pull/1736>09:40
ograzyga, if you put that behind something like a commandline option, sure, why not09:41
ogra(the initrd change)09:42
mwhudsonmvo, zyga: Uploading snap-confine_1.0.40-1.dsc: done.10:04
sergiusensgood morning10:05
liuxgogra, I just flashed the snappy software, but I still do not see the output10:06
mvomwhudson: yay, thank you - was the git repo of any help for you?10:06
mwhudsonmvo: yes10:06
ograliuxg, how long did you wait ? the fiirst boot can take a while10:06
mwhudsonmvo: i sent a mail with details10:07
liuxgogra, I waited for more than 10 mins10:07
ograwell, then you should see something (i surely do here)10:07
liuxgogra, do you see it via the HDMI output? I connect it to the hdmi port of my DELL monitor10:08
liuxgogra, if that is the case, how can I connect to it? using the ssh?10:08
ograyes, after the boot is done i get a login prompt10:08
ogra(until that shows up it stays black though, since the boot output goes to serial, as i said)10:09
ograif you know the IP you can just "ssh ubuntu@$IP" after it booted10:10
liuxgogra, yeah, that could be problem for it. there is no more ouput, so the screen is black10:10
ograwell, all i can say is that iit works fine with the LG monitor i use here10:11
ografor both, pi2 and 310:11
liuxgogra, I do not know what is wrong here for the DELL monitor10:12
ogrado you perhaps switch the input via a menu on the monitor ?10:12
ogra*have to switch10:12
liuxgogra, yes, I did that. it is hdmi 2 port10:12
liuxgogra, anyway, I am now trying to boot it again.10:13
ograliuxg, you could try to edit cmdline.txt on the system-boot partition of the SD and add "console=tty1" or some such to the cmdline10:14
liuxgogra, if I do "console=tty1", I can still see it on the serial link, right? how to get it working on the HDMI port?10:15
ograno, tty1 should switch it to the HDMI port10:16
ogra(or might be tty0 ... i forgot ... if 1 doesnt work, try 0)10:16
liuxgogra, thanks. I will try that.10:17
liuxgogra, I just tried to login using the ssh. I connected it to my router, and it worked for me.10:18
ograah, good10:19
liuxgogra, there is no output yet :) anyway, at least, I can try sth.10:19
ograliuxg, journalctl -b should show the boot log10:21
ograthere should be a line like: "Started Getty on tty1"10:21
ograright before "Reached target Login Prompts."10:22
ograif you see that both, then i'd guess there is a hardware issue (cable, monitor setup etc)10:22
zygaslangasek: hey, thanks :)10:23
liuxgogra,  http://paste.ubuntu.com/23084694/, this is the output. do you mean we need to set it to tty0?10:23
ograno, it tells you it starts a getty so there is a login promppt ... tty1 should be fine10:23
ograubuntu@pi3:~$ ps ax|grep getty10:24
ogra 2920 ttyS0    Ss+    0:00 /sbin/agetty --keep-baud 115200 38400 9600 ttyS0 vt22010:24
ogra 2921 tty1     Ss+    0:00 /sbin/agetty --noclear tty1 linux10:24
ograif you see that, then there is definitely a login prompt ... and i'd say there is something with the cable or monitor10:24
liuxgogra, OK. I got it. I see it like http://paste.ubuntu.com/23084702/10:25
zygaslangasek: if you are around, how can I help you to accept latest SRU into xenial-updates?10:25
ogracheck the cable, check the monitor again ...10:25
ografrom a software POV everything is there10:25
liuxgogra, do you think whether I need to change it to tty0 to have a try?10:27
ograno, i doubt that will change anything ... (but you can indeed try :)  )10:28
=== hikiko is now known as hikiko|ln
zygaogra: good, I know a lot of people that could use this10:44
zygamwhudson: thanks for the release!10:44
ograzyga, https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+packages?field.name_filter=&field.status_filter=published&field.series_filter=xenial ... make a debdiff against initramfs-tools-ubuntu-core from there and show it to mvo or me10:46
ogracyphermox, why is there a subiquity in the image build PPA ^^ ?10:47
zygaogra: thanks, I'll try10:47
ogra(and what is probert )10:48
mwhudsonzyga: np10:48
ogracyphermox, note that this PPA is for image content ...10:48
mwhudsonogra: src:subiquity builds console-conf10:48
ograconsole-conf ?10:48
mwhudsonthe first boot configurator thing10:49
ogramwhudson, we dont seed subiquity ... there are more and more packages showing up in that PPA that are not inside the image10:49
mwhudsonconsole-conf and probert will be inside the image soon10:49
ograah, k10:49
ogramwhudson, but they will be SRUed once they are ready ?10:50
ogra(long term plan is to get rid of most stuff in that PPA before GA release=10:50
ograpreferably of everything ... :)10:50
mwhudsonnew packages so not much chance of regression ;-)10:51
ograwell, it adds a new feature that replaces an existing one i guess ... so there is chance of regression10:51
ograbut thats fine in the edge channel10:51
mwhudsoni'm finding that i can only boot an all-snaps image in qemu once10:51
mwhudsonif i boot it again, it can't find partitions10:52
ograusing the vvery latest image from mvo ?10:52
mwhudsonusing an image i made from bits i got out of some image from mvo last week i guess10:52
ograthere were some fixes on friday ...10:53
ogra(and also a new u-d-f iirc)10:56
mupPR snapd#1737 opened: tests: update listing test for latest stable image <Created by mvo5> <https://github.com/snapcore/snapd/pull/1737>10:58
ogramwhudson, i just did 5 reboots with that image, no issues here10:59
mwhudsonogra: ok, i'll grab the newest bits tomorrow then10:59
ogra(apart from the known "no eth0" one)10:59
mwhudsonstill from http://people.canonical.com/~mvo/all-snaps/16/ ?11:00
mwhudsontalking of the no eth0 thing...11:01
* mwhudson makes some comments on a PR11:01
=== hikiko|ln is now known as hikiko
ograi dont see that issue on rpi11:01
ograit even gets its weird enxb827ebc92b03 device name and still works11:01
cyphermoxogra: right, like mwhudson said11:06
ograyeah, all fine then11:07
mwhudsonoh god cyphermox is awake, time for bed!11:07
cyphermoxhehe :)11:07
mvoogra: do you think you could make /etc/systemd/{user,system}.conf.d/ available via the ubuntu-core snap as writable directories? this is something for the plano people that they really need urgently11:14
ogramvo, sure, why not11:15
ograjust needs to be added to writagble-paths11:15
mvoogra: and I think we need to add the dirs to the image via livecd-rootfs, it appears to be missing11:19
mupPR snapd#1737 closed: tests: update listing test for latest stable image <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1737>11:19
ogramvo, hmm, why does systemd not create them ?11:20
ogra(can it actually handle these dirs if it doesnt actually create them ?)11:21
ogra(i would expect the package to create them if it can process content from there)11:21
mupPR snapd#1738 opened: tests: the stable ubuntu-core snap has snap run support now <Created by mvo5> <https://github.com/snapcore/snapd/pull/1738>11:23
* mvo lunch11:25
liuxgogra, I just installed hello and hello-world examples into my raspberry pi 2 device, when I run the apps, I get error like "mkdir: cannot create directory '/home/ubuntu/snap/hello': Permission denied". what could be the problem for it?  http://paste.ubuntu.com/23084828/ thanks11:32
zygaliuxg: which version of snap-confine that system has?11:34
zygaliuxg: can you see any apparmor denials?11:34
liuxgzyga, if I use "sudo", it is fine http://paste.ubuntu.com/23084831/11:35
ograzyga, i guess he uses mvo's image ... so whatever was the snap-confine in the image build PPA on friday11:35
ogra(not sure why that package is still in the PPA)11:35
liuxgzyga, yes, I took the software from http://people.canonical.com/~mvo/all-snaps/16/11:36
liuxgogra, to my best understanding, we should not use the "sudo" to get it running, right?11:37
ograubuntu@pi3:~$ sudo snap install hello-world11:37
ograhello-world (stable) 6.3 from 'canonical' installed11:37
ograubuntu@pi3:~$ hello-world.env11:37
ogramkdir: cannot create directory ‘/home/ubuntu/snap/hello-world’: Permission denied11:37
ograi get the same here11:37
ograubuntu@pi3:~$ ls -l /home/ubuntu/11:38
ogratotal 411:38
ogradrwxr-xr-x 3 root root 4096 Aug 23 11:49 snap11:38
ograthat definitely workd yesterday11:38
* zyga looks11:39
liuxgogra, is there anything broken?11:39
zygaliuxg: any DAC ownership along the way?11:39
zygaliuxg: I mean anything like a root-owned directory in the way?11:39
liuxgzyga, I do not quite understand what you mean, sorry11:40
zygaliuxg: any apparmor denials?11:40
zygaliuxg: I meant to ask if anything along /home/ubuntu/snap/hello-world is owned by root11:40
zygaliuxg: can you also run the same command without sudo but with SNAP_CONFINE_DEBUG=1 set11:40
liuxgzyga, http://paste.ubuntu.com/23084841/11:41
liuxgzyga, where should I change that variable? in the command line?11:41
zygaliuxg: just an environment variable11:42
zygaexport SNAP_CONFINE_DEBUG=1 should do it11:42
zygathat may be the problem11:42
liuxgzyga, yes, this time, it is right.11:42
zygachown everything in $HOME/snap11:42
zygaliuxg: and see if this occurs again11:42
liuxgzyga, to "ubuntu" user?11:43
liuxgzyga, do I need to set the SNAP_CONFINE_DEBUG=1 to 0 again?11:46
zygaliuxg: it's just temporary, you can unset it, it doesn't hurt11:46
liuxgzyga, yes, now, it works.11:48
ograzyga, see my paste above11:48
ogra$HOME/snap is root.root11:48
zygaogra: that's not correct11:48
zygaogra: is that reproducible?11:48
ograzyga, no, and it worked yesterday11:48
liuxgzyga, is this a bug in the image?11:49
zygaI don't know yet11:49
zygacan anyone with an image rm -rf $HOME/snap and run hello world without sudo11:49
zygaand see what happens11:49
ograi never ran hello-world with sudo11:50
ograyet the dir is root owned11:50
ograthough i dont know if it was like that before i installed hello-world11:50
zygaogra: it could be snap-confine itself, it runs as root,11:50
zygaogra: can you do a quick test as I've described?11:50
ograzyga, works fine11:51
liuxgogra, after I use classic to build my snap app, where can I find the .snap file? is it in the $HOME directory somewhere?11:51
zygaogra: ok, uff, that's not bad then11:51
ograliuxg, in the dir you ran snapcraft11:51
liuxgogra, after I exit the class, I need to install it under snap instead of being in classic, right?11:52
liuxgogra, can I just do installation there like "sudo snap install *.snap" under that folder?11:52
ograliuxg, the home dir is shared between classic and non-classic ...11:52
zygaliuxg: perhaps it would work from classic, as long as you can access the socket11:52
zygaliuxg: you can give it a try11:52
ograyou should just find your snap in your home if you built it there11:52
cpaelzertrying to transition from copy to dump plugin - I haven't found a single place describing that. I formerly used copy+files to rename-and-install files that the native build system of the project didn't add. Trying to rebuild that function with dump+organize now - are there known examples for that to take a look at?11:53
cpaelzerwow that was more text than I thougth when typing :-/11:53
liuxgogra, yes, you are right. thanks11:53
cpaelzerhmm, might even work with nil plugin since I might only need organize ...11:56
cpaelzeranyway I'll trial and error through that, but if one has a nice pointer to a collection of examples using dump (other than the tomcat maven demo) that would be nice11:57
ograzyga, very weird, i cant get it into that state anymore11:58
=== chihchun is now known as chihchun_afk
ogracpaelzer, you need to add "source: ."12:04
ograand rename "files:" to "filesets:"12:04
ograat keast that worked for me12:05
cpaelzerogra: I had added source . (and similar things) but it always complained about stuff not being a directory and/or not being around at install stage12:05
cpaelzerogra: but I'll give it a try once more12:05
cpaelzerand afaik the filesets do not have the renaming part I need12:06
cpaelzerthat would be organize and that is what breaks on the "has to be in the install stage"12:06
ogracpaelzer, https://github.com/ogra1/classic-snap/blob/master/snapcraft.yaml12:07
cpaelzerhrm, really - ok :-) that seems easier12:08
ograthats the change i did to go from copy to dump12:08
ogra(ignore architecture and version)12:08
cpaelzerogra: your example is nice although IMHO it doesn't match filesets as documented in docs/snapcraft-parts.md and docs/snapcraft-syntax.md12:14
cpaelzermy issue really seems to be that the "renaming" has to be done on install stage12:14
ograwell, i was lazy :)12:15
cpaelzerogra: your example did bin/*: bin12:15
ograit worked, so i left it as is12:15
cpaelzerbin/* afaik is only the identifier and you never refer to it :-)12:15
cpaelzerI can't use that to rename12:15
ograyeah, i copy bin/* to bin/ after all12:15
ograwithout name changes12:15
cpaelzerif I'm right your line could be "foobar: bin" and still work12:16
mupPR snapd#1732 closed: many: respect dirs.SnapSnapsDir in tests <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/1732>12:17
cpaelzeryep, foo: bin does just the same12:17
cpaelzerfyi that is the way it had to be written for the copy plugin in my case https://gitlab.com/paelzer/ntpsec/blob/snapify-ntpsec/snapcraft.yaml12:23
cpaelzerTL;DR the two copy sections did: "take file from local tree and place in snap under different name"12:23
cpaelzerstill struggling to recreate that with dump and/or nil plugin12:24
ograright, not sure how you do a rename ... ask kyrofa or sergiuens12:24
cpaelzersergiusens: kyrofa: ^^12:27
kyrofacpaelzer, it depends upon the way the filesystem looks when the copy occurs12:57
mupPR snapd#1739 opened: cmd/snap: use UserDataDir and UserCommonDataDir <Created by zyga> <https://github.com/snapcore/snapd/pull/1739>12:57
kyrofacpaelzer, it was written to try and mimic `cp` as much as possible, with the exception that `foo: bin/` (note the trailing slash) will create the bin/ dir12:57
cpaelzerkyrofa: hi, I just gave up a few minutes ago and filed bug 1616459 which summarizes it much better12:58
mupBug #1616459: dump plugin not a full super-set to the now deprecated copy plugin <Snapcraft:New> <https://launchpad.net/bugs/1616459>12:58
cpaelzerkyrofa: if you could take a look there and advise that would be great12:58
kyrofaSure thing12:58
mupPR snapd#1740 opened: many: respect SnapMountDir in tests <Created by zyga> <https://github.com/snapcore/snapd/pull/1740>13:00
mupPR snapd#1741 opened: firstboot: do not use absolute /sbin/udevadm in firstboot.go <Created by mvo5> <https://github.com/snapcore/snapd/pull/1741>13:01
mupPR snapd#1741 closed: firstboot: do not use absolute /sbin/udevadm in firstboot.go <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1741>13:04
zygaslangasek: ping, what's the status of snap-confine SRU13:16
mupPR snapd#1739 closed: cmd/snap: use UserDataDir and UserCommonDataDir <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/1739>13:21
mupPR snapd#1739 closed: cmd/snap: use UserDataDir and UserCommonDataDir <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/1739>13:21
mupPR snapd#1742 opened: firstboot: properly mock udevadm <Created by mvo5> <https://github.com/snapcore/snapd/pull/1742>13:23
mupPR snapd#1742 closed: firstboot: properly mock udevadm <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1742>13:28
jcastromvo: is snap-confine released into distro at a cadence or ad-hoc? I'm asking because the juju team would like 1.0.40, which has a bugfix for allowing us to use lxd with snapped Juju.13:31
kyrofajdstrand, hey, remember the new snapd socket we discussed yesterday?13:32
kyrofajdstrand, through trial and error, it seems these are the profile changes necessary to make use of it: http://pastebin.ubuntu.com/23085069/ . Can you give me your thoughts when you're able?13:34
jdstrandkyrofa: hey, yes13:34
jdstrandkyrofa: looks totally fine except please use @{PROC} instead of /proc13:35
kyrofajdstrand, ah, wonderful! It was a few more things than I was hoping, so I'm glad it looks okay13:36
mupPR snapd#1743 opened: many: use StripGlobalRootDir and respect SnapMountDir <Created by zyga> <https://github.com/snapcore/snapd/pull/1743>13:40
kyrofaHey nessita, it looks like https://myapps.developer.ubuntu.com/dev/click-apps/register-name-dispute has been removed? Does it have a replacement by any chance? We try to point people in the right direction from snapcraft13:45
kyrofaBut doing it online, it seems all ajaxy13:45
nessitakyrofa, hum, let me check... did you ask sergiusens? I think he had some info13:46
nessitabut I can check nevertheless13:46
kyrofanessita, no, I don't believe he's around just yet13:46
nessitakyrofa, is my understanding that filing a dispute ocurrs now in the same URL as name registration https://myapps.developer.ubuntu.com/dev/click-apps/register-name/13:47
zygajdstrand: lately ad-hoc because SRU was bumpy13:47
zygajdstrand: it is supposed to be co-released with snapd13:48
nessitakyrofa, it requires a submission and then you can file the dispute13:48
zygajdstrand: the plan is to get current SRU out, then do small SRU with just a few patches for apparmor and then a big SRU with all of 1.0.40 or .4113:48
kyrofanessita, hmm. So there's no URL to which we can direct people? What do we envision happening within snapcraft?13:49
jdstrandzyga: I'm not sure what question I asked but glad to hear the answer :)13:50
jdstrandjcastro: see zyga's response to me :)13:50
nessitakyrofa, why do you say we have no URL? the URL is https://myapps.developer.ubuntu.com/dev/click-apps/register-name/ and this was arranged after a bug report, let me find it13:51
kyrofanessita, ah, so just direct people to that URL and say "try to register it again" essentially?13:51
kyrofaThat works13:52
nessitakyrofa, right13:52
mupPR snapd#1744 opened: snap: use "up to date" instead of "up-to-date" <Created by mvo5> <https://github.com/snapcore/snapd/pull/1744>13:52
kyrofanessita, okay great, thank you!13:52
nessitakyrofa, I will confirm 100% when fgallina is here13:52
nessitakyrofa, he can give you the exact URL13:53
kyrofanessita, I appreciate it :)13:53
morphisniemeyer, zyga: it would be awesome if you can comment on https://github.com/snapcore/snapd/pull/166913:54
mupPR snapd#1669: interface: add usb device support to serial-port <Created by jocave> <https://github.com/snapcore/snapd/pull/1669>13:54
morphisniemeyer, zyga: would like to get that discussion unblocked13:54
morphisjdstrand, joc_: ^^13:55
mupPR snapd#1745 opened: overlord/snapstate: respect SnapMountDir in tests <Created by zyga> <https://github.com/snapcore/snapd/pull/1745>13:56
zygajdstrand: the one to mvo about snap confine sru13:57
zygajdstrand: ahh, that was jcastro !13:58
zygasorry :)13:58
jcastrozyga: excellent, thanks!13:58
zygamorphis: looking13:59
niemeyermorphis: What's the issue there?13:59
morphisniemeyer, zyga: see jdstrand's comment14:00
niemeyermorphis: I have a meeting soon and cannot go over this whole thread right now, but can discuss a particular aspect quickly if that's helpful14:00
morphisniemeyer, zyga: more or less jdstrand wanted your sign off on this14:00
morphisto make this future ready14:00
niemeyermorphis: What is "this"?14:00
morphisthe way we're modifying the serial-port interface14:01
morphisniemeyer: its fine if you comment later today14:01
niemeyermorphis: What is the urgency of this issue?14:01
morphisniemeyer: RTM :-)14:02
niemeyermorphis: I see non-trivial topics being covered there, such as hot-plugging of devices, which we most likely cannot address for RTM14:02
niemeyeror GA, for that matter14:02
niemeyermorphis: Those will indeed require some careful design that we don't have the bandwidth for right now14:02
morphisniemeyer: hotplug etc. isn't supposed to be done with this, but jdstrand wanted the current implementation to no be broken when we add sth like hotplug in the future14:02
morphisniemeyer: we don't want to discuss hotplug, we're ok with a static implementation which joc_ implemented14:03
morphisniemeyer: jdstrand just wants your sign-off on that to make sure what we've implemented is in line with possible thoughts around a future hotplug solution14:03
niemeyermorphis: What is the urgency of this issue?  I thought we had sorted a basic serial-port that should work for now?14:04
morphisniemeyer: exactly, we have it sorted and the impl is there14:04
sergiusenskyrofa nessita yes it has been removed and I talked to cprov about it, I silently fixed it without complaining14:04
morphisbut still jdstrand wanted you or zyga to comment14:04
niemeyermorphis: Ok, so why do we need the PR?14:05
morphisso, this is the reimplementation of the zigbee interface14:05
kyrofasergiusens, ah, so is bug #1616471 already fixed?14:05
mupBug #1616471: URL for name takeover is incorrect <Snapcraft:Triaged> <https://launchpad.net/bugs/1616471>14:05
loolelopio: I've disabled the karma-phantomjs dep and the build proceeds a bit but it fails with: /tmp/tmpc2celh4b: 4: exec: /home/ubuntu/go/src/github.com/snapcore/snapweb/parts/assets/npm/bin/gulp: not found14:05
loolCommand '['/bin/sh', '/tmp/tmpc2celh4b', '/home/ubuntu/go/src/github.com/snapcore/snapweb/parts/assets/npm/bin/gulp', 'install']' returned non-zero exit status 12714:05
morphisniemeyer: which had the approach of assingning a particular device via pid/vid to the device cgroup of the snap14:05
loolelopio: despite gulp being installed for my user14:05
sergiusenskyrofa this just means you need to pay more attention during standups ;-)14:05
loolelopio: would you know how to fix this one?14:06
nessitasergiusens, fabian is about to contact you, he was not aware of the breakage, he is about to add a redirect14:06
looljustinmcp_: around?14:06
sergiusensnessita it is all fine14:06
morphisniemeyer: as in the end it still just allows access to a serial port we agreed in the discussion with jdstrand that this should be added to the serial-port interface14:06
sergiusensnessita 2.15 is in xenial-updates already, don't waste time on this14:06
niemeyermorphis: What we discussed before and is merged uses a path, not pid/vid14:06
niemeyermorphis: This is already landed14:06
niemeyermorphis: Why do we need something else right now?14:06
kyrofasergiusens, haha, that was days ago!14:07
morphisno, not what we discussed for quite a long time for USB based tty for zigbee support14:07
morphisthat is what we want to add here14:07
morphisas there are zigbee usb dongles we need to support with RTM14:07
morphisand as you said, real hotplug support is past RTM/GA we need a interim solution for that14:07
morphisand that is the PID/VID based device-cgroup thing14:08
kyrofasergiusens, anyway, sorry for not catching that. Thanks for chiming in :)14:08
niemeyermorphis: Yes, and I thougth the interim solution was already merged14:09
niemeyermorphis: Why does it not work?14:09
morphisniemeyer: it works :-)14:09
niemeyermorphis: Ok, so we don't the the PR..?14:09
niemeyerneed the14:09
morphiswe need it as the iterim solution isn't merged yet14:09
morphisso that PR is the interim solution14:09
niemeyermorphis: We're going in circles.. I'm asking what seems to be like a simple question: we have a serial-port interface today, which we discussed and I assumed it would solve your problems. Why is that code not enough for you what you need for GA?14:11
morphisniemeyer: ok, lets go over it step by step:14:12
morphiswe have serial port which allows path based access to serial nodes in the system14:12
morphisall ok, works fine14:12
morphisbut it doesn't solves the problem of hotpluged usb devices which create new tty's14:12
morphisthat is why we came up with the VID/PID attributes for the interface based approach14:13
morphiswe had that first in an interface named 'zigbee'14:13
morphisbut then in a discussion with jdstrand and joc_ we came to the conclusion that it makes more sense in the existing serial port interface14:13
morphisthat implementation is now what is in https://github.com/snapcore/snapd/pull/166914:14
mupPR snapd#1669: interface: add usb device support to serial-port <Blocked> <Created by jocave> <https://github.com/snapcore/snapd/pull/1669>14:14
morphisthat is all fine, satisfies our needs for RTM14:14
niemeyermorphis: Why do we need to support hotplugging right now?14:15
jdstrandniemeyer: to be clear. the serial-port as implemented wasn't meeting morphis' and co's needs. they had a meeting with me on how to move forward and we discussed. I said to implement it as a PR but that it would need sign-off from the interfaces team to make sure it fit with future plans. In the PR comment, I tried to give thoughts on reconciling the PR's approach with possible future plans14:15
morphisniemeyer: as we have a specific product which requires this14:15
jdstrandniemeyer: afaic, we don't need to completely flesh out the future plans, but wanted to make sure we thought about where we were going before landing what is in the PR14:16
jhobbsdoes 'snap' respect http_proxy and https_proxy?14:16
niemeyermorphis: Of course.. many things are being attributed as dependencies of a product, but this is a technical question14:17
niemeyermorphis: We didn't discuss hot-plugging of devices in the last sprint, or anytime recently.. so it's a bit of an issue to have it in the roadmap days before freeze14:17
morphisniemeyer: we're discussing this since beginng of june14:19
morphisniemeyer: see https://github.com/snapcore/snapd/pull/140514:19
niemeyermorphis: So I'm trying to get down to the details: the fact you want a specific device to work, which likely has a specific vendor ID and product ID, implies it can also have a specific path in the filesystem14:19
mupPR snapd#1405: interfaces: add zigbee-dongle interface <Reviewed> <Created by jocave> <Closed by jocave> <https://github.com/snapcore/snapd/pull/1405>14:19
ahasenackis "snappy" in ubuntu-core the same as "snap" in ubuntu?14:19
ahasenackor is snappy some older version before a rename took place?14:20
niemeyermorphis: I'm discussing that sort of issue since early last year.. I'm pointing out we do not have hot-plugging of devices in the roadmap, which I hope you can understand and agree14:20
zygaahasenack: conceptucally yes14:20
morphisniemeyer: absolutely, that is why we all agreed on having the PID/VID approach14:20
morphisto have a interim solution which covers a very specific use case14:20
niemeyermorphis: Yep, so.. VID+PID means a fixed device.. means a fixed path.. means the current serial-port interface works14:20
jdstrandniemeyer: the problem with the zigbee dongle interface was that it was too-specific. morphis can correct me, but this device is not at all common, and there may be other not at all common devices out there for products, so having an interface for every no at all common device that for all intents and purposes is a serial port seemed not the right approach14:21
morphisniemeyer: having a fixed device path requires a udev rule and we need an interface to put that in place ..14:21
niemeyermorphis: The "interim solution" is not a magic thing.. we cannot bolt down such a major feature with no design consideration14:21
niemeyerjdstrand: Yes, what I'm suggesting is not hot-plugging14:22
niemeyerjdstrand: Which is exaclty the point I'm making.. we're not going to have hot-plugging of devices on this GA14:22
* jdstrand notes this is why we wanted to have the discussion with the interfaces team before committing :)14:23
morphisniemeyer: then we can really go back and hardware the vid/pid in the interface code and name that interface 'zigbee' again14:23
jdstrandwell, it sounds like that PR might then be a springboard for a future discussion, but that leaves zigbee14:23
niemeyermorphis: Yes, and we discussed quite a bit those UDEV rules, right?14:23
niemeyermorphis: You changed the approach completely on this PR14:24
morphissure, we fixed the udev backend especially for this14:24
niemeyerjdstrand: thanks for raising this14:24
jdstrandniemeyer: note that morphis didn't do that on his own. we had a long hangout to come up with this. zigbee is a serial-port14:24
niemeyerjdstrand: zigbee _has_ a serial port14:25
jdstrandI would prefer if we are going to hardcode, perhaps we take a different approach14:25
jdstrandmaybe add a different attribute to the serial-port interface. eg, type=zigbee14:25
jdstrandthen we hardcode in the interface what that ends up as14:26
niemeyerjdstrand: Not much benefit14:26
jdstrandrather than a new interface called zigbee-dongle14:26
jdstrandI am very wary of interface clutter14:26
niemeyerjdstrand: Well, some benefit actually14:26
jdstrandzigbee just isn't used a lot, aiui (morphis please correct me)14:27
niemeyerjdstrand: It has the benefit of allowing other serial ports to be used, at the cost of not being able to tell whether a particular device is a zigbee dongle or not, and thus connect things that do not work14:27
niemeyerjdstrand: that's not super important in this case14:27
niemeyerjdstrand: (the fact it's not used a lot)14:27
jdstrandbut it also reduces clutter14:27
jdstrandand at least keeps the changes in the interface where hotplugging would happen14:27
niemeyerjdstrand: we shouldn't add or not add interfaces just based on the number of devices shipping with them.. there are other considerations which are more important on that decision making14:28
jdstranda problem with android for developers has always been that the perms were too confusing14:28
jdstrandI'm not saying it is the only consideration. I'm sayingit is a consideration on where its support lies14:28
jdstranda new interface is a bigger thing than an attribute in an existing14:29
jdstrandbut, most importantly, this zigbee dongle (again, aiui) is a serial port14:29
niemeyermorphis, jdstrand: We have a team meeting now..14:29
jdstrandand we know we want to hot plug serial ports of all kinds in the future14:29
jdstrandand we can assume there will be other serial ports like zigbee14:30
niemeyermorphis, jdstrand: Thanks for those details.. I'll go through the whole PR today, think about the possibilities given what we just discussed above, and come back to you14:30
morphisniemeyer: thanks!14:30
jdstrandso grouping these serial port things into serial-port interface makes sense to me14:30
morphisniemeyer: I am open to what ever you come up with, as long as we can support the given use case14:30
niemeyermorphis: The use case is a zigbee USB dongle, to be clear, right?14:31
morphisniemeyer: yes14:31
niemeyermorphis: Ack, thanks14:31
* ogra shakes fist at googl14:33
joc_niemeyer: note i also have the hidraw PR open which is (fairly) marked as blocked by the serial-port PR - it uses excatly the same approach just for a different device subsystem14:33
joc_just in case that provides another angle to the review14:34
joc_sergiusens: josepht: i notice that using filesets on parts in SPS doesnt work (filed a bug earlier), $variables don't get expanded, is that a known problem?14:37
* jdstrand -> errands and lunch14:46
josephtjoc_: not that I'm aware of.  We'll take a look.14:47
mupPR snapd#1746 opened: many: have AuthContext expose device store-id, serial and serial-proof signing to the store <Created by pedronis> <https://github.com/snapcore/snapd/pull/1746>14:51
mupPR snapd#1747 opened: Collect attr hooks <Created by stolowski> <https://github.com/snapcore/snapd/pull/1747>14:54
dbarthhey there, i'm trying to install a new build of snapweb in a kvm snappy instance, but it fails when looking up the snap package.yaml14:56
morphisniemeyer: please take joc_'s comment in account, the hidraw interface covers exactly the same problem14:57
dbarththe snap has a snap.yaml instead; which component(s) do i need to i need to put in sync?14:58
kyrofadbarth, try installing snapweb from edge14:59
kyrofadbarth, oh wait, are you using 15.04?14:59
dbarthyeah, old one14:59
dbarththat's probably the issue14:59
jgdxany way to do a rebuild of one part and have e.g. prime updated with the new build of that part?14:59
kyrofajgdx, you can use `snapcraft clean <part>` or even `snapcraft clean <part> -s build` if you just want to rebuild that part15:00
kyrofajgdx, then run `snapcraft` again15:00
jgdxkyrofa, neat, thanks15:01
dbarthkyrofa: i guess i'll go with mvo's latest images15:02
kyrofadbarth, what device are you using?15:02
dbarthmostly a kvm, i have a pi2 and pi3 around if that's better15:02
kyrofadbarth, no that's fine, though you know you can use snaps on normal ubuntu as well?15:03
kyrofadbarth, if you want an all-snap image though, yeah, use mvo's15:04
dbarthkyrofa: sure ;) but i'd rather stay on the kvm for now15:04
mupPR snapcraft#619 closed: Add source-checksum option <Created by tsimonq2> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/619>15:05
mupPR snapcraft#661 closed: Added a test Jenkinsfile <Created by elopio> <https://github.com/snapcore/snapcraft/pull/661>15:05
sergiusensjoc_ it is known now ;-)15:08
mupPR snapd#1748 opened: Basic support for validation assertion <Created by ralsina> <Conflict> <https://github.com/snapcore/snapd/pull/1748>15:08
joc_sergiusens: good :)15:09
joc_sergiusens: out of interest, are there any tests run which build snaps from parts in sps?15:09
sergiusensjoc_ first another question, wth is sps? :-)15:10
joc_sergiusens: hehe i was told that's the official name of the parts service thingy15:10
sergiusensjoc_ oh, I hope it isn't; SPI was a bad name already and it has been killed ;-)15:11
natefinchhey - where do I file bugs on the snap tool itself15:13
kyrofanatefinch, see the room title :)15:15
natefinchkyrofa: doh, sorry :)15:15
kyrofaErr, topic. Whatever it's called15:15
* sergiusens goes out for lunch15:16
noise][parts service is parts service, please don't call it SPS15:18
=== sverdy is now known as StephaneVerdy
iceywhy isn't snapcraft installable via snap yet?15:21
kyrofaicey, because it need access to the archives. Eventually it'll build inside lxc containers which will enable its snappification15:22
iceywoot kyrofa!15:22
mupBug #1616508 opened: snap install overwrites its own output <Snappy:New> <https://launchpad.net/bugs/1616508>15:25
joc_noise][: i stand corrected, will drop the TLA15:29
leftyfbIs there a way to use snapcraft to snap an app that uses an install.sh for it's installation?15:32
ppisati_my pull requst failed during the autopkgtest snaps with a15:33
ppisati_FAIL timed out15:33
ppisati_message repated here and there15:33
ppisati_do any of you know how to grok this>?15:33
slangasekzyga: I am not around at 3am... :)  You might have better luck getting the SRU Team member of the day to accept it? https://wiki.ubuntu.com/StableReleaseUpdates#Publishing15:35
kyrofaleftyfb, yes but you'd need to either wrap it in a build system (e.g. a Makefile that calls the install.sh) or make a local plugin that builds your part15:35
ograjdstrand, so i talked to niemeyer about the kernel snaps during our meeting, seems your warnings are prefectly right and the snapcraft team actually needs to drop all the lines from the "type: kernel" builds15:36
ograjdstrand, sergiusens is looking into that, so once it is there the kernels should just auto-land15:36
ograppisati_, FYI, i did split the makefile out of the kernel-snap trees, they now all use the same15:37
ogra(from a separate bzr tree)15:37
mupBug #1616515 opened: warn uploaders and downloaders when a package or deps has CVEs <Snapcraft:New> <Snappy:New> <https://launchpad.net/bugs/1616515>15:40
ppisati_ogra: nice!15:41
iceyis there currently a plugin / method for snapping a go package that uses gdm for dependency management?15:45
mhall119sergiusens: can you remember me how to make snapcraft look for packages from a PPA?15:52
kyrofaicey, no, you probably need a new plugin for that-- pull requests welcome!15:53
kyrofaicey, note that you can create a local plugin, by the way15:53
mupPR snapd#1749 opened: many: split public snapd REST API into separate socket <Created by kyrofa> <https://github.com/snapcore/snapd/pull/1749>15:57
kyrofajdstrand, here is that diff in PR form: https://github.com/snapcore/snapd/pull/1749/files#diff-a34e166c5b3016c122430c5884f41e9b . If you have a minute to take another look at give it a +1 I'd really appreciate it15:59
mupPR snapd#1749: many: split public snapd REST API into separate socket <Created by kyrofa> <https://github.com/snapcore/snapd/pull/1749>15:59
sergiusensmhall119 add the ppa to your host16:01
sergiusensjoc_ oh, and yes there are tests16:01
joc_sergiusens: in the snapcraft source? should i try and add one with filesets?16:03
mhall119sergiusens: that's less than ideal16:04
mhall119sergiusens: would you be opposed to me submitting a patch to snapcraft to allow additional archive sources to be added via the snapcraft.yaml?16:05
mhall119at least for stage-packages16:05
mhall119but build-packages in a cleanbuild environment too perhaps16:06
mupBug #1616507 opened: app names cannot contain underscores <Canonical Click Reviewers tools:New> <Snapcraft:Opinion> <Snappy:New> <https://launchpad.net/bugs/1616507>16:07
mupPR snapcraft#753 opened: Add the arm64 architecture to the nodejs plugin <Created by elopio> <https://github.com/snapcore/snapcraft/pull/753>16:14
mupPR snapd#1719 closed: firstboot: add firstboot assertions importing <Critical> <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/1719>16:16
zygaslangasek: noted, tank you16:17
zygathank you16:17
=== mup_ is now known as mup
=== mup_ is now known as mup
ahasenackwhere can I find snappy logs? I installed the snap I'm developing, the service is not starting, I would like to know why16:44
kyrofaahasenack, check syslog16:46
kyrofaahasenack, or use systemctl16:46
kyrofaahasenack, `systemctl status snap.<snapname>.<servicename>.service`16:46
ahasenackkyrofa: does the snap, when running a service, become a systemd job?16:47
kyrofaahasenack, indeed16:47
* ogra taps foot16:48
ahasenackkyrofa: yeah, ok, got it16:49
ahasenackcan't run squid even as root, it still tries some system call that snappy doesn't like16:49
ahasenackAug 24 13:48:17 nsn7 ubuntu-core-launcher[12191]: /snap/squid-deb-proxy/x3/usr/bin/run-squid.sh: line 24: 12198 Bad system call         $SQUID -z -N -f $CONFIG16:49
ografchown() most likely16:49
ahasenackkyrofa: is there a way to start it as non-root?16:49
kyrofaahasenack, are you familiar with snappy-debug?16:49
=== davmor2_ is now known as davmor2
kyrofaahasenack, not if it's a service, no16:49
ahasenackI don't really need it to start as root, then switch users, as it binds to a high port16:49
ahasenackit could start as nobody16:50
ograwell, there is currently no way to run it as anything else but root16:50
kyrofaahasenack, in snappy, services are run as root16:50
elopiolool: are you using cleanbuild?16:57
leftyfbi'm trying to snap rsync. But it doesn't seem to have permissions to write to my home directory16:58
leftyfb" failed: Permission denied (13)"16:59
ogradid you add the home interface ?16:59
leftyfbogra: not sure what that is17:00
ograplugs: [home, x11, network, network-bind]17:00
ogra(allows access to home, x11 and network bits)17:00
ograadd "plugs: [home]" to your app definition17:01
leftyfbogra: what about it not allowing in /tmp either? Should there be a plugin for every directory/partition/filesystem?17:01
ograwell, a snap has its own /tmp17:01
ograso /tmp is allowed ... but isnt your /tmp17:01
leftyfbogra: right, but if I want to rsync something into or from /tmp17:02
ograthats currently not possible ... you would have to fish it out from the snap dir17:02
ograwell, check with snap-debug17:07
ogratheer are surely errors in syslog and such17:07
leftyfbadding in the home plug works when rsync'ing to and from my home ... so that's good17:08
sergiusensmhall119 what would the separation of concerns be wrt how launchpad works if ppa's can be added in snapcraft.yaml? wrt allowing ppa's when doing a cleanbuild, there's a bug for that and just waiting implementation17:17
sergiusensmhall119 adding ppa's to the snapcraft.yaml language will get tricky when implementing the source engines as well; I'd rather not do that now regardless of the separation of concerns aspect with launchpad17:18
sergiusensjoc_ yes, an integration test would be ideal17:18
joc_sergiusens: the tests would pull from the real parts service? there isnt a mocked version or something17:22
mupPR snapcraft#754 opened: Use in plugin code to remove bad files <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/754>17:35
mupPR snapcraft#755 opened: Enable the static checks for the integration tests <Created by elopio> <https://github.com/snapcore/snapcraft/pull/755>17:35
mhall119sergiusens: I'm confused, what does launchpad have to do with it?17:35
sergiusensjoc_ integration tests use mocks, talk to josepht about the details17:35
sergiusensmhall119 launchpad allows selecting which PPAs to add when building17:36
sergiusensmhall119 as part of the environment setup17:36
mhall119oh, I didn't realize that17:36
mhall119but only PPAs?17:36
sergiusensmhall119 yes, well not sure if anything else is allowed, cjwatson would know best17:37
mhall119sergiusens: my plan was to append sources to whatever snapcraft currently gets17:37
sergiusensmhall119 and gpg keys?17:38
mhall119if launchpad adds PPAs to the host (chroot, container, whatever it is) that would still be used17:38
mhall119could be auto-trusted or ignored I suppose....17:38
sergiusensmhall119 would the language be clean enough for the day we need to support adding rpm sources?17:38
sergiusensmhall119 we fail on unsigned repos today, I don't feel it is a good idea to move away from that17:39
mhall119it could be, but that would require more work in the existing snapcraft cod17:39
joc_josepht: if you could give me some pointers about how to write an integration test for snapcraft to test an aspect of building a remote part that would be great :)17:39
mhall119sergiusens: so your source of trust is the fact that it's been added to the host?17:39
mhall119I suppose the packaging could include a trust keyring17:40
mhall119I wouldn't want to put the keys themselves in the snapcraft.yaml17:40
mhall119sergiusens: basically I want to get Qt 5.6 dependencies for qupzilla, and there's no way for me to do that without adding those repos to my laptop and potentially breaking lots of stuff17:41
sergiusensmhall119 for now then `lxc launch ubuntu:xenial`17:42
sergiusensand work from there17:42
mhall119yeah, but that's going to make handing the snap packaging duty over to upstream a more difficult sell17:43
sergiusensmhall119 you could build Qt from sources and provide it as a part17:43
sergiusensmhall119 also, I am not saying no, I am saying no for the time being17:44
cjwatsonmhall119: Launchpad itself will only let you configure PPAs, but there's nothing really to stop you adding other sources to snapcraft via the proxy, it's just a bit more manual17:44
mhall119I've been told that's not easy, they have a non-standard build setup that our current plugins can't handle17:44
mhall119cjwatson: the proxy?17:44
cjwatsonok, maybe I shouldn't have mentioned mostly-internal details.  do you actually need an explanation of the internals at the moment?17:44
mhall119I'd be happy with a how-to-use-them17:45
cjwatsonin that case you don't need any information about that :)17:45
josephtjoc_: There's a fake server here: https://github.com/snapcore/snapcraft/blob/master/snapcraft/tests/fake_servers.py#L3917:45
mhall119so I have an KDE Neon archie I want to pull qt dependencies from17:45
cjwatsonLP builders can only talk to the outside world via an HTTP proxy (which is only available for snap builds, not other kinds of builds), but that's configured in the http_proxy environment variable and sane stuff (including apt) will honour that17:46
cjwatsonI don't really have an opinion on how it's configured in snapcraft.yaml etc. as long as the LP configuration mechanism keeps working17:47
sergiusensmhall119 with what cjwatson says, you could get away with a custom snapcraft plugin that does something similar to what we do with the catkin one17:47
mhall119okay...but how do I use that to tell snapcraft to get packages from an archive that's not installed in the build environment?17:47
sergiusensyou would not be supported in that path forever, but it will get the job done17:47
josephtjoc_: we're using something similar for the parser tests here: https://github.com/snapcore/snapcraft/blob/master/snapcraft/tests/test_parser.py#L63317:48
mmccHi folks, I am trying to snap a very simple Makefile based project, with one twist- the Makefile is generated by running perl on a Makefile.PL. Is there an easy existing way to tell snapcraft to do that before running make? Or do I need to add a 'pre-command' to the make plugin or something?17:49
sergiusenstealeg hey, when do we get to see your plugin? :-)17:50
naccmmcc: i dont' think there is a trivial way; but you could, i think, write your own plugin (pretty easily) that inherits form the make one, and only overrides build() to call perl Makefile.PL first then super.build() ?17:50
naccmmcc: that plugin would go in parts/plugins/ in your snapcraft directory17:51
naccmmcc: and then your yaml would just refer to it17:51
mmccah ok, that's 'local plugins' then. I saw a reference to that earlier. thanks17:51
naccmmcc: yeah17:51
josephtjoc_: though the fakes might not work in this case, you can also output you're own local copy of parts.yaml to ~/.local/share/snapcraft/parts.yaml and then call build17:51
naccmmcc: there might be a better way, but that's what i've done in the past when a makefile doesn't quite conform to the generic `make; make install` template17:52
mmccnacc, thanks!17:53
naccmmcc: np, i would also consider filing a bug report/feature request. I think there might already be one (so search first), for the notion of -- use this plugin, but do this one step first :)17:54
joc_josepht: ok thanks, i'll try and put something together based on that tomorrow, the parts.yaml file should be enough as I don't see anything wrong with the contents of that when i've tried this17:54
mmccnacc: ok, I'll look. TBH I'm a little surprised that there isn't a generic 'shell' plugin, where I could put one command and then have my 'make'-based part run after it. Is that a conscious design decision?17:55
naccmmcc: probably? i'm not aware of those level of decisions :) the thing is such a plugin doesn't really make sense -- in that it'd have to take parameters which are arbitrary commands. It seems like it would become less useful (and prone for bad c&p and not using of good parts)17:56
leftyfb /snap/bin/rsync-leftyfb.rsync ... how do I get rid of that .rsync at the end?17:56
naccleftyfb: it's a naming thing, iirc17:56
Pharaoh_Atemzyga: snap-confine is on its way to stable for f2417:57
naccleftyfb: if your snap and app name are the same, it magically drops the . naming17:57
naccleftyfb: but since your snap is called rsync-leftyb, it puts it in a sort-of namespace17:57
leftyfbah, I see17:57
naccleftyfb: i think there is a feature open, or something, to allow for specifing the naming, but i don't have bug # handy17:57
leftyfbbingo, got it, thanks17:58
Pharaoh_Atemzyga: also, any luck on the patches for moving /snap?17:58
Pharaoh_Atemand it looks like someone left a comment for you to address in the review for snapd17:58
jgrimmmmcc, nacc: fwiw: https://github.com/snapcore/snapcraft/pull/72717:58
mupPR snapcraft#727: Add a new build plugin 'shell' that runs arbitrary shell commands <Created by Magical-Chicken> <https://github.com/snapcore/snapcraft/pull/727>17:58
naccjgrimm: :) thanks!17:59
jdstrandogra: re kernel and reviews tools> ack18:00
naccjgrimm: i would almost suggest to Magical-Chicken that perhaps such a plugin should only be available in devmode (based upon e.g. monsterjamp's comment from 7 days ago)18:01
naccjgrimm: i've been thinking about that more lately, there are some things that are 'sane' in the context of trying to get going, but aren't necessarily sane in a GA/stable version18:01
naccjgrimm: e.g., testing hooks? maybe the shell app i have a bug filed for (so you can debug by dropping to your snap's environment)18:01
leftyfbok, so how do I go about publishing a snap of say, rsync so others can find it just by using the name "rsync" and not -leftyfb? Can I just remove -leftyfb from the name or do I have to go through some process?18:03
naccleftyfb: you probably need to register the name, yeah18:05
leftyfbthat's it?18:05
leftyfbbah, it's reserved18:05
jdstrandkyrofa: done18:05
naccleftyfb: you'd probably need to rename your snap to 'rsync', as well18:05
naccleftyfb: yeah, i'd expect it to be :)18:05
leftyfbnacc: so we have to wait for all the original developers of applications to publish their own apps?18:07
naccleftyfb: no, but i think they reserved some common names in order to not let random folks camp on them18:12
leftyfbok, now this is kinda silly. Everything we upload gets .leftyfb added to the end of it. But I can't just upload "rsync" and have it turn out rsync.leftyfb because "rsync" is already taken. So I have to name it "rsync-leftyfb" which then also puts .leftyfb at the end of it making it "rsync-leftyfb.leftyfb".18:13
kyrofajdstrand, hey thanks!18:15
kyrofaleftyfb, name the app the same as the snap, and you can just call it rsync-leftyfb18:16
mupPR snapcraft#756 opened: Use block style for multiline YAML values <Created by josepht> <https://github.com/snapcore/snapcraft/pull/756>18:17
leftyfbkyrofa: I had that. But when I uploaded it and tried to publish it it added .leftyfb to the end of rsync-leftyfb18:17
kyrofaleftyfb, then did you try to install it from the store again? It should install as rsync-leftyfb18:18
kyrofaRegardless of the store showing the .leftyfb18:18
kyrofaleftyfb, well wait-- which series are we talking about?18:18
ograjdstrand, sergiusens with a patched snapcraft in the PPA like http://paste.ubuntu.com/23085847/ i now have end to end kernel snap builds and auto-uploads fully working18:19
leftyfbkyrofa: series?18:19
kyrofaleftyfb, when you upload the snap, which series did you select? 15.04 of 16?18:19
leftyfbkyrofa: nowhere during the snapcraft upload process or the web ui publish process did it ask for a series18:20
* ogra refreshes to the new pi2-kernel snap ... lets see if it also boots now :)18:20
kyrofaleftyfb, ah, 16 then. So yeah, did you try actually installing the one you published?18:21
leftyfbabout to18:21
leftyfbkyrofa: ok, that worked18:21
kyrofaleftyfb, in 15.04 snaps were snapname.publishername, so what you're seeing there might be a store leftover18:22
jgrimmnacc, snappy-debug mentioned here: http://askubuntu.com/questions/783979/how-do-i-debug-snaps18:23
naccjgrimm: thanks18:24
tealegsergiusens: re the plugin - I've not seen any progress on the 32bit kernel calls that would effect SBCL and CCL - I do have a version working with GNU CLisp, but that is slightly less useful because a few key libraries don't play well with CLisp.18:26
tealegsergiusens: I could certainly bring the current state to the point where I could submit a pull request.18:27
natefinchbtw, I can't run any snaps: https://bugs.launchpad.net/snapcraft/+bug/161658618:30
mupBug #1616586: all snaps report "multiple nvidia drivers detected, this is not supported." <Snapcraft:New> <https://launchpad.net/bugs/1616586>18:30
ogranatefinch, duplicated18:35
ogra(check the one i duplicated it against, there is an explanation and a workaround)18:35
newsagescomo se crea una lib snap  para poder reutilizarla entre snaps?18:36
natefinchogra: lol, bogus indeed.18:36
ograzyga, is bug 1615248 yours ?18:37
mupBug #1615248: ubuntu-core-launcher nvidia driver detection is bogus <Snappy:New> <https://launchpad.net/bugs/1615248>18:37
ograor who maintains ubuntu-core-launcher nowadays18:37
mhall119sergiusens: I know about $SNAPCRAFT_STAGE, is there another env var I can use to point to parts directories?18:39
natefinchogra: gotta say, I am not going to fiddle with any nvidia folders by hand.  Every time something mucks with my drivers, I end up spending most of a day in a command prompt trying to figure out what broke X.18:40
mhall119or a way for partA to copy files from partB into the stage/prime area?18:41
ogranatefinch, well ... dpkg -l |grep ^ii| grep nvidia-[0-9]18:41
mupPR snapcraft#755 closed: Enable the static checks for the integration tests <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/755>18:41
ogranatefinch, thats should be the only drivers in use18:41
ogra(i assume it will only return one)18:41
ograall other dirs can be deleted18:42
natefinchogra: yeah, it only returns one, and that is the one with far more files in it (the other one only has two, presumably just cruft)18:43
ograyeah, you can safely delete them18:43
jdstrandogra: to be clear, you are talking about this warning: unknown entries in snap.yaml: 'dtbs,firmware,initrd,kernel,modules' lint-snap-v2_unknown_field18:45
lazyPowerwoo first snap works \o/18:45
ograjdstrand, exactly ... i patched the image PPA snapcraft to not add them and the store just auto-approved all my builds18:46
lazyPowernext question i have, i've seen asked before but not answered, and i fear i know the ansewr. Is there a docker snap with a plug that i can use? I'm cycling towards snapping up kubernetes, and this is going to be a very complex snap18:46
jdstrandI like that solution. I don't have to do anything :)18:46
ograjdstrand, well, sergiusens does :)18:46
newsagesHow does one create a library for reuse between snaps ?18:48
tvossnewsages: you create the library and make it accessible via snapcraft parts (see https://developer.ubuntu.com/en/snappy/build-apps/snapcraft-parts/)18:52
=== caraka_ is now known as caraka
natefinchogra: btw, renaming that spurious nvidia directory does fix the problem18:58
ogranote that in the bug :)18:59
natefinchogra: I was on my way there :)18:59
tuxianoHi I installed darktable using snappy. Now I have issues opening files stored outside of my home directory (on a nfs drive). Is it somehow possible to extend the permissions of a snap app so that it can open such files.19:01
tuxianoSame problem with vlc, too.19:01
argesi'm testing snapd 2.13, which has a new interface 'kernel-module-control'. Besides installing the new package what else is required to make this interface visible? 'snap interfaces' doesn't show it, but a strings /usr/lib/snapd/snapd shows it existing in that binary19:06
ahoneybunI had a good idea mhall119 lol19:16
kyrofaarges, a snap that provides the slot, probably19:20
=== mup_ is now known as mup
argeskyrofa: i have this, but I get "has bad plugs or slots: kernel-module-control (unknown interface)" when trying to install the test package19:21
loolelopio: no I'm not19:21
kyrofaarges, it might be re-executing an older snapd from within the core snap19:22
mhall119ahoneybun: snap find --channel=beta?19:22
elopiolool: I'm having tons of different problems. I get less if I use cleanbuild.19:22
loolelopio: I think the issue is in the gulp plugin; it expects gulp is installed in its own private dir19:22
kyrofaarges, try running both the server and client with SNAP_REEXEC=019:22
argeskyrofa: ok i'll try that19:22
loolelopio: I will try this, but lxd is a bit heavy for the rpi19:23
elopiolool: while we solve the problems with snapcraft.yaml and launchpad, I quickly reverted to get the previous multiarchitecture build, so I have the 4 snaps uploaded to the store and waiting for a manual review.19:23
loolit's not heavy in itself, but it's a lot of extra io19:23
loolelopio: oh cool19:23
elopiolool: the problem is now that the snap doesn't start, saying that ubuntu-app-launch failed to execv19:24
mupBug #1616605 opened: Cannot open files from NFS drive <Snappy:New> <https://launchpad.net/bugs/1616605>19:24
elopioso I have like 3 workarounds, but none of them is easy to get finished.19:24
tuxianoJust added a bug report: https://bugs.launchpad.net/snappy/+bug/161660519:24
mupBug #1616605: Cannot open files from NFS drive <Snappy:New> <https://launchpad.net/bugs/1616605>19:24
loolelopio: OMG19:24
elopiolool: let me upload the snaps to my ftp so you can take a look.19:24
argeskyrofa: still doesn't work19:24
loolelopio: what's the startup issue?19:24
kyrofatuxiano, yes, we see that ;)19:25
kyrofaarges, dumb question, but you're sure the kernel interface is in 2.13?19:25
arges$ git tag --contains a22b514513c020673b290e3dd723d0bbe9a496ad19:27
argeskyrofa: ^^ yes19:27
argeskyrofa: sudo /lib/systemd/systemd-activate -E SNAPD_DEBUG=1 -E SNAP_REEXEC=0 -l /run/snapd.socket /usr/lib/snapd/snapd19:30
argesthat worked ^^19:30
kyrofaarges, ah, you only ran the client with SNAP_REEXEC?19:30
argeskyrofa: I wasn't passing the enviornment variable correctly into snapd, so I just manually executed like that19:31
kyrofaAh, okay19:31
argesso will I just need to wait until ubuntu-core is updated with the snapd then?19:31
arges* with snapd 2.13 that is19:32
zygaogra: perhaps, checking19:33
kyrofaarges, indeed. mvo or ogra might be able to move that along19:34
ograkyrofa, ?19:35
kyrofaogra, get the new snapd in a core snap soon19:36
mupBug #1615248 changed: ubuntu-core-launcher nvidia driver detection is bogus <Snappy Launcher:Triaged by zyga> <https://launchpad.net/bugs/1615248>19:36
kyrofaThat came out commanding, I meant to just define what "that" was :P19:36
kyrofaBut yes, ogra, do as I say19:36
elopiolool: http://paste.ubuntu.com/23086044/19:37
ograwell, we build the daily snnap from the images PPA19:37
kyrofaogra, does that automatically go to edge nowadays?19:37
ograthe edge PPA19:37
elopiolool: http://people.ubuntu.com/~elopio/snaps/19:37
loolelopio: is that with --devmode?19:37
loolelopio: thanks19:37
elopiolool: no, without.19:37
ograyes, every UTC morning :)19:37
ograkyrofa, seems snapd failed to build https://launchpad.net/~snappy-dev/+archive/ubuntu/edge/+packages19:38
kyrofaelopio, journalctl -u snap.snapweb.snapweb.service might be more helpful19:38
loolelopio: I'll check it out tomorrow, thanks19:38
ograelopio, why does that only have 2.12 ^^ ?19:38
loolelopio: I'm finishing lxd setup on rpi and kicking a cleanbuild19:38
mupBug #1616515 changed: warn uploaders and downloaders when a package or deps has CVEs <Snapcraft:Opinion> <Snappy:New> <https://launchpad.net/bugs/1616515>19:39
elopiokyrofa: that's what I pasted.19:40
kyrofaelopio, oh, that looked like status. That's all it gives you? Meh19:40
elopiolool: same error with devmode.19:41
ograkyrofa, elopio is that bug 1610026 you are talking about ?19:41
mupBug #1610026: snapweb fails to start after reboot <snapweb:Confirmed> <https://launchpad.net/bugs/1610026>19:41
loolelopio: ok, check dmesg for apparmor denials, if nothing then it's likely a missing +x or an unreadable data file somewhere19:41
elopioogra: no, that one happens with the one in the store. If I do snap install snapweb --edge, it starts here.19:42
loologra: I believe this is another one19:42
ograah, k19:42
ograkyrofa, arges, well, snapd comes from daily builds in https://launchpad.net/~snappy-dev/+archive/ubuntu/edge/+packages ... so as soon as 2.13 will show up there it will be in the ubuntu-core snap19:43
elopiolool: yes, that sounds likely because the snap that I build from master using snapcraft starts. So something that snapcraft does that the build script doesn't.19:43
argesogra: ok good to know! thanks19:43
elopioI'm just not sure which workaround to pursue now :S19:44
kyrofaogra, edge only though, right?19:44
ograkyrofa, well, mvo promotes them currently, we do not re-build19:44
ogra(that will change once the PPAs are cleaned out)19:45
mupPR snapd#1750 opened: store: request device session macaroon from store <Created by matiasb> <https://github.com/snapcore/snapd/pull/1750>19:45
ograso the edge package also ends up in the stable ubuntu-core currently19:45
loolelopio: I'll poke it more tomorrow; I might have to go through the same pains you did, but I guess there is no alternative to debug this19:45
loolor I could try running your snaps directly19:46
* lool EODs &19:46
elopiolool: oh, it started!19:46
* ogra goes afk for a while too19:46
kyrofaelopio, he's gone, sorry, you failed for today19:46
kyrofaogra, so they don't go into any channel by default?19:48
elopiokyrofa: he's gone too.19:49
kyrofaArgh, europeans19:49
elopiothey stop working at lunchtime. We should move there :)19:50
kyrofaYeah that sounds nice19:51
elopionessita or noise][1: does it make sense for snapweb to require a manual review before I can publish it on edge?19:53
mupPR snapd#1704 closed: snap: add key management commands <Created by cjwatson> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1704>19:59
=== mup_ is now known as mup
jdstrandkyrofa: hey, otoh, if I found a bug in the desktop part, would I file that against snapcraft?20:10
sergiusensjdstrand an issue on the github upstream maybe?20:11
nessitaelopio, hi! you mean there was an upload requiring manual review?20:13
jdstrandsergiusens: ok, thanks20:13
sergiusensjdstrand just trying to avoid more bugs :-)20:14
elopionessita: well, yes, I'm pushing packages there. But the idea is to make an upload for every change in master through launchpad, so that will be a lot of slow manual reviews and breaks the purpose of rapidly changing edge20:15
nessitaelopio, what's the error you are having?20:16
jdstrandsergiusens: do you know where that is otoh?20:16
elopionessita: no error. It uses the snap-control interface which is restricted.20:16
nessitaelopio, right, so once we have the proper assertions per snap in place, we will be able to state "privileged interfaces" per snap in said assertion20:18
nessitaand that will be fed to c-r-t20:18
nessitaso manual review will not be required20:18
sergiusensjdstrand https://github.com/ubuntu/snapcraft-desktop-helpers `snapcraft define <part-name>` should tell you as well iirc20:18
nessitaelopio, until then, you will need a +1 from a reviewer20:19
nessitaelopio, privileged interfaces is GA, so not far :-)20:19
jdstrandsergiusens: thanks! 'define' tells me cool stuff but not the project or where to report bugs20:19
jdstrandsergiusens: (fyi)20:19
elopionessita: alright, that sounds good. Could the assertion be only for edge? I think I would need a signature from the security team to push to stable in some cases.20:20
nessitaelopio, hummmmmmm good question, I think no, the assertion is per snap. Note that there is no way to restrict a snap revision to be publish in extra channels after approval20:23
=== mup_ is now known as mup
mupPR snapd#1751 opened: tests: add workaround for u-d-f to unblock all-snap image tests <Created by mvo5> <https://github.com/snapcore/snapd/pull/1751>20:24
sergiusensjdstrand the 'source' could be an indication; but this is actually a good point, we should expose `origin` there :-)20:24
elopionessita: it might be fine. I can be trusted to ask for a review before moving the snap, but it would be great if this could be crypto enforced.20:25
elopionessita: so this means https://bugs.launchpad.net/software-center-agent/+bug/1580371 doesn't make sense anymore, right?20:25
jhodappI can't figure out why snapcraft can't find the test-client binary after building it, here's my snapcraft.yaml: http://pastebin.ubuntu.com/2308618120:26
nessitalet me check20:29
sergiusensjhodapp might be related to your .pro file there20:30
sergiusensjhodapp is the test-client in stage or prime?20:30
sergiusensor even inside parts/test-client/install ?20:30
jhodappsergiusens, I only see it under part/test-client/build20:31
nessitaelopio, well, it makes sense a request, is just that our solution for it is the one using assertions instead of special-casing inside the source code20:31
nessitaelopio, let me add a comment in there20:31
elopionessita: thanks. It is indeed a lot better than what we discussed before.20:32
elopionessita: and another question while that gets implemented. I pushed a snap and it's waiting in the manual review queue. Then I pushed a new version. Is there a way to cancel the first review? Or will the reviewers just ignore it?20:32
loolelopio: oh cool, how did it start?20:33
loolelopio: my cleanbuild failed :-(20:33
loolelopio: http://paste.ubuntu.com/23086213/20:33
elopiolool: the revert was missing a chmod +x, as you suggested.20:33
elopiolool: try the snaps from my ftp.20:34
nessitaelopio, I don't know for sure, let me check20:34
elopioI will test in rpi2 after lunch.20:34
jhodappsergiusens, any ideas?20:35
mupPR snapd#1752 opened: tests/main/ack: fix test/style <Created by pedronis> <https://github.com/snapcore/snapd/pull/1752>20:36
sergiusensjhodapp is you `make install` dtrt wrt that PREFIX you set?20:37
loolelopio: awesome, your snaps work fine!20:37
jhodappsergiusens, dtrt wrt?20:38
sergiusensjhodapp do the right thing with regards to20:38
elopiokyrofa: you see, I won!20:38
jhodappsergiusens, I believe it does, let me double check that20:38
elopioluckily that means I don't have to solve all the bugs I collected and can get back to testing :)20:39
sergiusenselopio please check the nodejs armhf one though :-)20:39
mupPR snapd#1752 closed: tests/main/ack: fix test/style <Created by pedronis> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1752>20:39
sergiusenselopio and the proxy one!20:39
elopiosergiusens: the proxy is solved. It's building.20:39
jhodappsergiusens, do you mean from the parts dir or building test-client manually on its own?20:39
sergiusenselopio +1 it then please :-)20:40
elopiosergiusens: oh wait, you mean the https env var. I had already forgotten about that one.20:40
sergiusensjhodapp does make install DESTDIR=/some-path work for this?20:40
sergiusensfor that project20:40
elopioI think I know how to reproduce it without launchpad. Let me see...20:40
sergiusensI am no qmake expert though20:41
mupPR snapd#1728 closed: asserts: add a key-proof assertion <Blocked> <Reviewed> <Created by cjwatson> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/1728>20:41
sergiusenslool when are you joining the league of snapcrafters?20:42
jhodappsergiusens, let me check20:44
jhodappsergiusens, hmm, one problem might be that make install doesn't really seem to ever have anything to do20:48
mupBug #1616629 opened: could not unmarshal state entry "snap-type" <Snappy:New> <https://launchpad.net/bugs/1616629>20:54
jhodappsergiusens, yeah that's definitely the issue...the install target is messed up...ugg qmake :)21:01
nessitaelopio, sorry, I got distracted. I'm looking at snapweb details right now21:03
nessitaelopio, many revnos with red exclamation mark21:03
nessitayour question was.../21:03
nessita(I see a warning of "21:03
nessita(NEEDS REVIEW) 'snapd-control' requires approval lint-snap-v2_blacklist (snapweb, snapd-control)21:03
elopionessita: there are some revisions that I don't need reviewed, because I pushed newer. My question was how to tell about this to the reviewers.21:06
nessitaelopio, if you go to a revno detail do you see any button action at the bottom?21:06
nessitalike https://myapps.developer.ubuntu.com/dev/click-apps/5455/rev/14/21:06
elopionessita: no buttons.21:08
nessitaelopio, then no, sorry. I'm happy to reject as many revision as you instruct me21:08
elopionessita: I just need the last 4.21:13
elopioone per arch.21:13
nessitaok, let me reject 10 and below21:13
nessitaelopio, done21:15
elopiothank you21:15
nessitajdstrand, so, how can we (store folks) know when is OK to approve some interface usage such as the one requested by elopio? (21:18
nessita(NEEDS REVIEW) 'snapd-control' requires approval lint-snap-v2_blacklist (snapweb, snapd-control)21:18
elopiosergiusens: I can't test the nodejs thing. It's not what I thought and scalingstack uses only http proxy.21:22
elopiosergiusens: furthermore, I don't understand. If I have an http_proxy=foo and https_proxy=bar, the workaround makes no sense. It will use https through my foo proxy.21:23
cmarsjust noticed that the copy plugin is deprecated and it recommends "dump". seems to take a different configuration, how do i port it over?21:58
josephtcmars: I've got a basic example here: https://git.launchpad.net/~joetalbott/+git/dump_example/tree/snapcraft.yaml22:07
kyrofajosepht uses too many usernames22:07
cmarsjosepht, thanks. I was using the files: attribute on the copy plugin to compiled artifacts in my project directory to the snap... how do I do that with dump?22:08
kyrofaI keep trying to type @josepht on github22:08
cmarsjosepht, is organize: doing the mapping that files: used to?22:10
mupBug #1616650 opened: snap refresh while command is running may cause issues <snapd-interface> <Snappy:New> <https://launchpad.net/bugs/1616650>22:10
josephtcmars: if you just want to get a copy you can include it in 'stage' option (and maybe 'snap')22:10
josephtcmars: I'm using 'organize' to change the name of a file and then 'stage' and 'snap' to copy it into those partws22:10
josephtkyrofa: I'm 'josepht' on github :)22:11
cmarsjosepht, ok, got it working, thanks!22:12
josephtcmars: awesome! no problem22:12
* josepht -> dinner22:13
kyrofajosepht, oh yeah, searching for you to assign bugs then :P22:17
mupPR snapcraft#753 closed: Add the arm64 architecture to the nodejs plugin <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/753>22:26
sergiusenselopio have you checked https://github.com/npm/npm/issues/205022:28
sergiusenselopio specifically the last comment22:28
sergiusenselopio your suggestion is the same one we had for bzr22:28
sergiusenshave something external dtrt22:29
mupBug #1616657 opened: snapd install removes Unity launcher-compliant entries <Snappy:New> <https://launchpad.net/bugs/1616657>22:34
sergiusenskyrofa want to look at snapcraft#75422:50
mupPR snapcraft#754: Use in plugin code to remove unwanted files <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/754>22:50
sergiusenskyrofa what are your thoughts on LP: #1616656 ?22:55
mupBug #1616656: intermittent failure to load correct plugin when a local plugin is a subclass of existing plugin <Snapcraft:Triaged> <https://launchpad.net/bugs/1616656>22:55
sergiusenskyrofa hmm, maybe wait for my email reply to make it to the bug :-P22:56
sergiusenskyrofa there we go22:57
sergiusenskyrofa but you are distracted reviewing my PR I suppose22:57
kyrofasergiusens, yeah I don't really have any good ideas there simply because I don't know python well enough. We need to research it23:11
* kyrofa -> dinner break, back in a bit23:14
nacckyrofa: sergiusens: have you asked barry about that? he'd be my goto python person :)23:15
=== Birchy is now known as figment[1000]

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!