#snappy 2015-10-01 <fgimenez> good morning <davidcalle> Good morning o/ <clobrano> morning :) <elopio> fgimenez: hello. I did this: https://github.com/elopio/go-subunit/pull/7 <elopio> which was a little hard and confusing for me. Could you please review it with extra care? <fgimenez> elopio, hey, sure i'll take a look. now get some rest! :) <elopio> yup, bed time \o/ <elopio> see you later. <clobrano> Chipaca: if you have time, I'd like to hear your opinion about a change to hw-assign <guest56723> is it possible to "install" wily-preinstalled-desktop-next-amd64.tar.gz on a spare partition? <vmayoral|pc> sergiusens, ricmm: can you guys look at https://bugs.launchpad.net/snapcraft/+bug/1501651. We can't go that path to generate the snaps. Any ideas? <ubottu> Launchpad bug 1501651 in Snapcraft "ARM chroot issues: fatal error: rt_sigaction failure" [Undecided,New] <vmayoral|pc> we'll try getting snapcraft working in a native way on the RPi2 images but that seems a hack. Let us know if you come up with something else <Chipaca> clobrano: i don't have time right now, but if you write it out i can read it when i do have time <Chipaca> clobrano: OTOH this might be mailing-list fodder <clobrano> Chipaca: sure, no problem <sergiusens> vmayoral|pc, yeah, I thought you were using python and c <sergiusens> vmayoral|pc, qemu arm static doesn't play well with go <sergiusens> we should push ogra to fix it ;-) <vmayoral|pc> sergiusens: i'm using python <sergiusens> ah Chipaca already replied <sergiusens> vmayoral|pc, oh, I see <sergiusens> vmayoral|pc, so while you can't snapcraft all the way, you have reached the snap stage for everything <sergiusens> vmayoral|pc, you can run 'snappy build' from your host targetting the ./snap dir, it should just work (TM) <Chipaca> anything that tries to catch signal NSIG-1 breaks in qemu <sergiusens> vmayoral|pc, we will be moving 'snappy build' to 'snapcraft' as we mentioned yesterday <Chipaca> including, apparently, an unnamed threading implementation? dunno * vmayoral|pc trying out "snappy build" <vmayoral|pc> sergiusens: similar result with "snappy build" https://gist.github.com/vmayoral/c248de02f8cc79c53548 * Chipaca afk for a while <Chipaca> vmayoral|pc: if it's just python, why are you building it in a qemu? * Chipaca leaves with that <vmayoral|pc> Chipaca: trying to get a .snap for the demo <vmayoral|pc> not sure, but, would i be able to intall a .snap generated in x86? (even if it's just python? <vmayoral|pc> that's why <sergiusens> vmayoral|pc, from OUTSIDE the chrrot I said ;-) <sergiusens> Chipaca, he is using snapcraft; he needs to get the right python runtime! <vmayoral|pc> sergiusens: that did it, thanks <sergiusens> \o/ <sergiusens> :-) <sergiusens> asac, http://paste.ubuntu.com/12630697/ <longsleep> vmayoral|pc: did you see my https://code.launchpad.net/~longsleep/snapcraft/snapcraft-debs-plugin - i use that to generate armhf snaps on x86_64 by using rebuilt debian packages - the branch is outdated now, but i will continue working on it soon <dholbach> sergiusens, do we have a good example for a scons project we could add to snapcraft's source? <sergiusens> dholbach, yeah, coming soon ;-) sabdfl is playing with it <dholbach> cool! <JamesTait> Good morning all; happy Thursday, and happy International Coffee Day! ð ðµ <sergiusens> tedg, are you up yet? <zyga> ogra: hey <zyga> ogra: how do you feel? <zyga> ogra: I have a thing you could help me with <zyga> ogra: let's say I have a raspberry pi <zyga> ogra: and I'd like to build the image with my magic sauce inside <zyga> ogra: I'd like to build a patched version of snappy itself (snapd) <zyga> ogra: patched CLI <zyga> ogra: some extra systemd units that start <zyga> ogra: how would I go about this? <zyga> ogra: I would really love to have a call with you and try to get to a point where I can make my own image (or iterate in some way) <asac> mvo: https://sigquit.wordpress.com/2009/03/13/the-core-pattern/ <sergiusens> tedg, you around? can you get your catkin branch code polished for an MP? <sergiusens> tedg, would be great to use os.walk instead of 'find' or shutil.rmtree and so on and so forth <sergiusens> hmm, I'll create an MP and add comments <sergiusens> tedg, code looks good <sergiusens> asac, http://paste.ubuntu.com/12630697/ <tedg> sergiusens: Awake :-) <tedg> sergiusens: Cool, I was waiting to see if you guys needed stuff from it. <sergiusens> tedg, \o/ <sergiusens> tedg, I'll send an email :-) * tedg is glad to know he was missed :-) <sergiusens> tedg, done, two emails <tedg> Haha, on the Erle Spider: https://twitter.com/pierredewet/status/649549049780158465 <jdstrand> ogra2: hey, couple questions I have a feeling you might know the answer to: a) if I set a static ip address via snappy config ubuntu-core (easy enough), how do I setup the resolver? b) what is the recommended way to setup remote logging (ie, a snappy system sending to remote 514/udp)? <DexterF> greetings <DexterF> how "vanilla" is the Snappy Ubuntu 4.2 kernel? 4.2 has spanking new code for a certain DVB receiver I'd like to run on a Pi2, but will it be just like vanilla? are dev files like headers just like on x64, i.e., can I install build-essential and build fancy kernel modules against it like linuxtv? <vmayoral|pc> sergiusens: we can use your help for the camera snap <sergiusens> vmayoral|pc, is that also ros? <vmayoral|pc> no, it's not <sergiusens> vmayoral|pc, I'm down stairs <sergiusens> vmayoral|pc, want to come <sergiusens> ? <vmayoral|pc> yeap, thanks <tomconte> Hi everyone! Playing with snapcraft here and having strange Permission issues <tomconte> I suspect some kind of AppArmor problem but not sure how to troubleshoot it <elopio> plars: I need your help with the agent test script. Please ping me when you have time. <plars> elopio: sure, what's up? <elopio> plars: first, the deb that we are using needs to be updated daily to keep track of the changes in trunk. <plars> elopio: which deb? <elopio> could we somehow install it from the ppa? Or do you have an alternative way to make sure that we always get the daily deb? <elopio> currently it is just a hardcoded link. <elopio> plars: http://people.ubuntu.com/~elopio/spi_scripts/snappy-tests-job.sh <elopio> https://code.launchpad.net/~snappy-dev/+archive/ubuntu/tools-proposed/+files/snappy-tests-job_1.0.0ubuntu1-0%7E64%2B201510010310%7Eubuntu15.10.1_amd64.deb <plars> elopio: why died this need to be a deb? This would potentially destabilize the host for that test device <plars> elopio: couldn't this be an artifact that gets downloaded and runs binaries from a local extracted path? <elopio> plars: the alternative was to set up the GOPATH in the agent and get it from trunk. But you didn't like it that way, so we went for the deb. <elopio> plars: it is an artifact that gets downloaded and runs binaries. The problem is that the artifact changes the path every day. <plars> elopio: I installed all the go dependencies you asked for so that you could do that, remember? <elopio> yes, but then you told me to downlod, extract and run. <elopio> plars: if it's ok for you, I'll switch to source code and go run. <plars> elopio: I thought that was the plan all along, and I think you have golang and the other deps you need there to do it. You just need a script that sets the path, pulls your branch, and does the build <elopio> good. I'm on it. <elopio> plars: second problem. If you look at the script, now I'm pushing the results summary to the json. <plars> elopio: let me know if you need anything from me, happy to help however I can <elopio> the tests should currently fail because there's a bug. And attach the error. <elopio> but they all pass, and the payload is empty. <elopio> I'm not sure what's going on here. <plars> One minute, let me look <plars> elopio: '/bin/sh: 1: ./snappy-tests-job.sh: Permission denied\n' <plars> elopio: it doesn't seem to be getting very far <elopio> oh, ok. And what should I do for it to fail instead of pass if I have that error? <elopio> ev: ^ here's a case where I need to deactivate the test and create a new one. <ev> elopio: noted; and huh, we seem to have slightly screwed up and never documented that <ev> getting that on the board <plars> elopio: what does your spec look like? <plars> elopio: I would think that the spi agent should pick up that failed run of the script, and call it a fail, unless you have it running some other command after that <elopio> plars: wget ...; ./script... <plars> and the later command passes <elopio> It's missing the chmod +x <plars> elopio: right, but that should exit non-0 <plars> elopio: if that's the last command in your spec, then I would think it should get called a fail, but perhaps I'm doing something that eats it <plars> let me look <vmayoral|pc> tedg: http://wiki.ros.org/cmake_modules <tedg> Cool, I'll use that then <plars> elopio: ah yeah, I think the spi agent would depend on the provisioning kit to pass that exit value along, but we don't want to end abruptly <ev> elopio: I stand corrected - we just need to generate a new PDF <plars> elopio: I could probably set a flag somewhere that if any command in your test_cmds list fails, we should exit non-zero, does that make sense to you? <ev> incoming <elopio> ev: great, thanks. <vmayoral|pc> tedg: awesome! <elopio> plars: makes sense. <elopio> the other problem would be how to collect that error. <sergiusens> tedg, also meet ahcorde <tedg> Howdy ahcorde ! <ahcorde> Hi tedg ;) <elopio> ev: and I have a feature request. Not sure how to send it. When I create a new test opportunity, it gives me an id. But then I can't use that id to query for the results. <sergiusens> ahcorde, http://paste.ubuntu.com/12632171/ <sergiusens> tedg, so ahcorde is going to try and save you time checking if you have all the deps <ev> elopio: all feature requests to me (or Ursinha when I'm away) <sergiusens> tedg, you can remove demos, spider_imu_dev from the list <tedg> This is my new favorite command: find . -name package.xml -exec grep _depend {} \; | grep -v \<\!-- | cut -d \> -f 2 | cut -d \< -f 1 | sort -u <tedg> :-) <Ursinha> me <sergiusens> Ursinha, you! <Ursinha> sergiusens: happy belated birthday! <elopio> ev: by mail? * Ursinha hugs sergiusens <ev> elopio: is there anything more to your request than that? If we just made it so that you could use the ID returned in a test opportunity to retrieve results for just that opportunity, would that be enough, or is there more to it? * sergiusens hugs Ursinha <ev> elopio: generally, yes :) <Ursinha> \o/ <elopio> ev: that's just what I want, thanks. <ev> getting it on the board <tedg> vmayoral: ahcorde: cppunit? libcppunit? <vmayoral> tedg: not needed (i believe) <Ursinha> elopio: email is generally a good idea, makes it harder to miss the request :) <ev> Ursinha: hm, I wonder if elopio's request is a facet of this https://trello.com/c/EIgSVwFy/65-story-search-test-results-data <elopio> ev: Ursinha: that seems to involve a lot more. I just need another key to be allowed when querying for results. <Ursinha> let me see <elopio> and not urgent. I added a UUID to the image_unique_id, and I'm querying that. <elopio> works ok. <ev> I remember we discussed this with noise ages ago and had a card on such filtering <ev> I've added https://trello.com/c/jbxyvqec/188-story-filter-test-results-by-test-opportunity-id until we can otherwise prove we don't need it <vmayoral> sergiusens: https://github.com/ament <plars> elopio: I'll have a patch up for that later after I get through some other stuff, but in the meantime, just ignore the pass/fail status and chmod +x your script and I think you'll get a lot farther :) <tedg> vmayoral: ahcorde: eigen? eigen-containers? <elopio> plars: yes, I'll add the +x and change the script to run from source. <elopio> I'll probably mess it up and have to ask you again to copy the error for me :) <plars> elopio: and great idea on the results query by test id, I think that would be useful as well - you can kind of hack around it by giving your image a unique id every time, but more options for query would always be better <plars> elopio: no problem, I have a much easier way of looking at the trace now <elopio> plars: specially now that my client that requests stuff is in python. <elopio> it's really easy to capture the result from the previous call. <plars> cool <ahcorde> tedg: libeigen3-dev <Ursinha> ev: I've tagged the story accordingly, and moved to the "progress and result reporting" lane -- feel free to reorder the priority <ev> thanks Ursinha <Ursinha> ev: thanks for creating the card <ev> elopio: the latest PDF now has the instructions for deactivating <sergiusens> ogra, hey, mind testing the latest snapcraft in tools-proposed with your snapcraft.yaml's? <longsleep> i just switched to latest snapcraft trunk to work on my plugins, seems it now requires jsonschema which i do not have yet, is trunk supposed to work? <plars> elopio: oh, another dirty trick you might want to consider (I find it helpful) is to save off all your output during your test script, pastebin it at the end of the job, and post the pastebin link in the results json for spi to pick up, then you can easily see a few more details <elopio> plars: smart smart. <tedg> longsleep: You'll need to grab python3-jsonschema <tedg> longsleep: It validates the YAML now using that <elopio> fgimenez: you have one ExecCommand in the config-test that needs to be udpated for the cli branch. <longsleep> tedg: sure, but i thought i have the daily ppa - shouldnt it just give me the dependencies * longsleep checks apt sources <tedg> longsleep: I'm not sure if the PPA has moved to version 0.2 yet. <tedg> sergiusens: ^ <tedg> It was "not daily" there for a while to avoid breaking people. <longsleep> tedg: yes - the ppa seems to have 0.2.1 or 0.2.2 but for some reason my system has 0.1-0~135~ubuntu14.04.1 <tedg> You should upgrade, it's better now ;-) <longsleep> the ppa i use is http://ppa.launchpad.net/snappy-dev/snapcraft-daily/ubuntu <sergiusens> longsleep, trunk works as long as you install what is in debian/control <fgimenez> elopio, ok thanks, i'll merge from trunk once it's landed <sergiusens> longsleep, daily ppa is dead, ppa:snappy-dev/tools is what we use <longsleep> ah there is indeed an update - you folks pushed that recently? <sergiusens> longsleep, 0.2, a long while ago <sergiusens> longsleep, 0.2.2 I just staged in the daily ppa <sergiusens> longsleep, if you want the next tentative thing, use ppa:snappy-dev/tools-proposed <sergiusens> longsleep, don't use http://ppa.launchpad.net/snappy-dev/snapcraft-daily/ubuntu <longsleep> sergiusens: ah ok thanks - i will remove the daily and add the proposed then. I got the spappy-dev/tools ppa already. <elopio> fgimenez: do you have any idea why the prints of my python script in jenkins appear only when the script finishes? <sergiusens> longsleep, hmm, if you have /tools you should of at least gotten 0.2.1 <longsleep> sergiusens: yeah, seems like have not updated for a while <longsleep> i get python3-jsonschema now when doing an upgrade so i think i am good thanks <fgimenez> elopio, nope, didn't notice that, i thought it was due to the connection with spi <elopio> fgimenez: no, it should print: results not found, trying again... <elopio> there's a plugin for python scripts in the build which might do it better. <longsleep> sergiusens: another question, do you have plans to make it possible for snapcraft to use local plugins? <sergiusens> longsleep, it already can <sergiusens> longsleep, just x- it <longsleep> sergiusens: oh thats great <sergiusens> longsleep, there's a test inside integration_tests, which implements a nothing plugin <longsleep> sergiusens: found it - that is local to a snap though. What if i need the same plugin for multiple snaps? <sergiusens> longsleep, ah, upstream submission <sergiusens> longsleep, are you asking about the deb one? <longsleep> sergiusens: yes that one <sergiusens> longsleep, else I need to still work on some path overriding bug/task still open somewhere <longsleep> sergiusens: i will sync it to the latest tree <sergiusens> longsleep, sounds good, also if you can, unit tests and / or integration tests <longsleep> sergiusens: Yeah sure, it worked well for me so far - i am building 20 snaps or so with it. <fgimenez> nice evening all o/ <tedg> vmayoral: <tedg> vmayoral: Looking at catkin_make vs. catkin_make_isolated <tedg> vmayoral: It seems I have to use isolated because of orocos? <longsleep> Mhm seems like snapcraft needs meta-data now in snapcraft.yaml <vmayoral> yes * longsleep has some snaps to upgrade <vmayoral> tedg: yes <tedg> vmayoral: Is there a reason I wouldn't want to use isolated all the time? <vmayoral> we use isolated all the time <vmayoral> tedg: i can't come up with a reason not to use it <tedg> K <tedg> I will too :-) <elopio> plars: this time the run took more than 15 minutes, but I still get no result_payload. <plars> elopio: looking <plars> elopio: https://pastebin.canonical.com/140981/ sorry for the poor formatting, I just get the full string out in a log <plars> elopio: from a quick glance, it looks like it might want hg installed? * plars wonders who uses hg still <elopio> plars: yes. code.google.com. Can you please install it? <plars> elopio: will do <elopio> I will make the script smarter so it doesn't fail if summary is not there. And send this to pastebin. <plars> elopio: and I'll add it to the extra packages to get installed in the environment too <elopio> plars: you have pastebinit installed, right? <plars> elopio: yes <plars> elopio: the bbb ones have mercurial now at least <plars> elopio: you aren't doing anything on rpi at the moment right? There's something wrong with that one that I'm trying to sort out, possibly a bad usb stick again <elopio> plars: no rpi yet. <longsleep> whats the latest syntax in snap yaml? architecture or architectures? <tedg> longsleep: architectures, and it's an array of architectures <DexterF> heya <DexterF> put 15.04 on a pi2. so.. does core have the same packages as standard ubuntu? can I just snappy install build-essential and compile fancy kernel modules? <DexterF> hmm, obviously not <elopio> plars: is the CWD on the agent is new every time I run it? #snappy 2015-10-02 <plars> elopio: yes <elopio> plars: could you please check what's the latest error? <elopio> I'm not yet catching the good stuff in the payload. Butt when I test it here it works. <plars> elopio: sure, just a minute <plars> elopio: this seems to be the interesting bit: cat: /results/output/log: No such file or directory\nYou are trying to send an empty document, exiting.\ncat: /results/output/summary: No such file or directory\n./snappy-tests-job.sh: 9: ./snappy-tests-job.sh: cannot create /spi_test_result.json: Permission denied <elopio> plars: hum. The docs say that there is an env var $CWD. <elopio> I was using that. I'll take it out. <elopio> thanks. Another try... <plars> elopio: $PWD perhaps? <elopio> plars: no, the docs say $CWD. But it's not entirely clear what they meant with that. <plars> elopio: which docs? <elopio> plars: spi-user-docs-latest.pdf <plars> could be a misprint, but I would think $PWD should work * elopio needs better bash superpowers. <yashi_> regarding to bug #1499429, what's a proper workflow to reflect review comment to my launchpad branch? force push or another branch? <ubottu> bug 1499429 in Snapcraft "snapcraft dies with "export: python3.5/dist-packages: bad variable name"" [Critical,Confirmed] https://launchpad.net/bugs/1499429 <elopio> yashi_: hello. <elopio> I replied on the merge proposal. Just make the change, bzr commit and bzr push. <yashi_> elopio: thanks! <elopio> you use the same branch, but are not forcing anything. It will keep the previous commits. <elopio> yashi_: thanks a lot for finding this, and fixing it. Have you signed the contributors agreement? <elopio> http://www.ubuntu.com/legal/contributors/submit <yashi_> elopio: nop, reading.... <elopio> yashi_: Here's the faq: http://www.ubuntu.com/legal/contributors/licence-agreement-faq <elopio> please let me know if you want to know something else. <yashi_> elopio: the submission ask me to put a project contact. what is it? <yashi_> elopio: hmm. do i need to print the pdf, sign it, and snail back to canonical? <elopio> yashi_: the contact is asac. Alexander Sack <djennings@example.org> <elopio> yashi_: and no, afaik you don't have to send the pdf. Let me confirm. <elopio> yashi_: it says that you can send the pdf if you don't have a launchpad account. You are good with filling the form. <elopio> sigh, I djennings@example.org. I can't even capture the error. <elopio> plars: again, please, whenever you see this. <yashi_> elopio: done <elopio> yashi_: thank you! <elopio> welcome to snapcraft. If you ever get bored, we have tons of things funny things you can do ;) <yashi_> elopio: will push a fix today <elopio> sergiusens: hey, you are up. <elopio> sergiusens: these are the problems I had: <elopio> ttps://bugs.launchpad.net/snapcraft/+bug/1499429 <elopio> https://bugs.launchpad.net/snapcraft/+bug/1501980 <elopio> https://bugs.launchpad.net/snapcraft/+bug/1501977 <ubottu> Launchpad bug 1501980 in Snapcraft "the error message when a plugin is not found is not good" [Undecided,New] <ubottu> Launchpad bug 1501977 in Snapcraft "py2-project example fails to snap" [High,New] <elopio> other than that, looks good. <elopio> haven't tried the minecraft one yet. <clobrano> morning :) <fgimenez> good morning <davidcalle> asac, thanks for the heads-up, that's an impressive team effort :) Are there any sections you'll still want to keep under wraps or can I assume (after today eod) everything is ready for a first publication? <dholbach> good morning <davidcalle> Hey dholbach, how are you? <dholbach> hey davidcalle <dholbach> good good - how about you? <davidcalle> dholbach, life is good <davidcalle> dholbach, nice work with the snappy doc propositions, I agree with everything :) <dholbach> yeah, I was trying to find a balance between: more useful for certain demographics and not too much new maintenance work for us :) <dholbach> ... and leaving IA intact <clobrano> Chipaca: I'll drop here my hw-assign question (I wrote on the mailing list too), please have a look at it, when you've got time :) <JamesTait> Good morning all; happy Friday, and happy International Day of Non-Violence! ð <clobrano> Chipaca: about the possibility to assign a symlink to a device node using hw-assign command (Bug #1496319), I had everything done and ready to be submitted for something like: "snappy hw-assign <device> <symlink>" but, then, I thought that it's more common to create a symlink only if some conditions are met (like VID/PID, etc.), so I've got the idea to change it in: "hw-assign <device> <properties>" where <properties> would be a string containing part of <clobrano> the Udev rule to append to the newly created rule, like "ATTRS{idVendor}==...". This way one can add different rules, not only symlinks. What do you think? <ubottu> bug 1496319 in Snappy "Could not create symlink to hw device with udev rules" [Undecided,New] https://launchpad.net/bugs/1496319 <Chipaca> clobrano: hmm. first thought is whether udev has been audited enough to have people safely write rules <clobrano> Chipaca: yep, that was my first idea too <clobrano> Chipaca: like with great power comes great responsability :) <clobrano> Chipaca: but at the same time, it's common symlinking to a generic /dev/ttyUSB* and then add conditions to narrow down the list of possible device nodes <lool> vmayoral|pc: ssh {{EMAIL+PHONE}} <clobrano> Chipaca: however, that things can be done at different times. First try and add the first implementation and then see if/when we can move to the second one <Chipaca> clobrano: so which would the first implementation be? <clobrano> Chipaca: just hw-assign <device-node> <symlink> <clobrano> Chipaca: where <symlink> is optional <asac> davidcalle: not sure yet. lets see how it looks like <Chipaca> clobrano: and how would the move to the second phase work? <lool> tedg, sergiusens: ssh {{EMAIL+PHONE}} for the ARM buildd <lool> vivid, installing snapcraft there now <clobrano> Chipaca: that's depend on you all I think :), I can't decide if/when that change will be applicable <Chipaca> clobrano: no, i mean <Chipaca> clobrano: let's say we implement hw-assign <device> [<symlink>] <Chipaca> clobrano: document taht <Chipaca> clobrano: people use it <Chipaca> clobrano: how do we introduce the new thing without breaking the old? <clobrano> Chipaca: ooh, right <clobrano> Chipaca: well, it's not that hard to recognize a symlink (valid) from a string defining a udev rule, just to keep the backward compatibility <clobrano> Chipaca: but I got your point <lool> vmayoral, tedg, sergiusens: please use {{EMAIL+PHONE}} instead, sorry <lool> root will go away on reboots, and we should not use root <lool> ok, sudo works now, removing your root SSH keys guys <lool> yeah, building! <dholbach> fgimenez, elopio: does "python3 setup.py test" crash for you in lp:snapcraft too? <fgimenez> dholbach, let me try <fgimenez> dholbach, yes, pip-requirements is failing http://paste.ubuntu.com/12637380/ <dholbach> fgimenez, http://pastebin.ubuntu.com/12637392/ is what I'm seeing <dholbach> zyga, ^ do you know what's happening here? <zyga> dholbach: looking <zyga> dholbach: yes, it's fixed with a branch that didn't land yet <zyga> dholbach: it's a one-line fix <zyga> dholbach: but I'm not sure if someone fixed it because the original contributor did the fix in a werid way but didn't respond to feedback <zyga> sergiusens: ^^ <zyga> dholbach: it happens because wily has two versions of python3 <dholbach> zyga, are http://paste.ubuntu.com/12637380/ and http://pastebin.ubuntu.com/12637392/ the same issue? <zyga> dholbach: no, that seems different <zyga> dholbach: the 2nd one looks like a bug elsewhere, how did you get it? <zyga> dholbach: is that trunk, any released version, something else? <dholbach> trunk <zyga> dholbach: on wily? <dholbach> yes <dholbach> I just ran python3 setup.py test <zyga> dholbach: one sec <zyga> dholbach: I'll just fix the bug that the contributor tried <zyga> dholbach: and see if I get to the 2nd one <dholbach> <3 <zyga> dholbach: I should have fixed it earlier but I really wanted yashi_ (AFAIR) to reply <dholbach> no worries <zyga> dholbach: https://code.launchpad.net/~yashi/snapcraft/snapcraft/+merge/272337 this is the thing <dpm> dholbach, looking at the developer manual, trying to do 'sudo apt-get install snapcraft-examples' does nothing for me. I'm on 15.04, and I've got the ppa:snappy-dev/tools installed <dpm> anything I'm missing? <zyga> yashi_: around? <dholbach> dpm, not sure if anyone updated the ppa - let me check <dholbach> dpm, https://launchpad.net/~snappy-dev/+archive/ubuntu/tools/+sourcepub/5408454/+listing-archive-extra <dholbach> dpm, it should be there <dholbach> are you sure you have the ppa enabled and your apt sources updated? * dpm apt updates to be sure <dpm> that might have been it <dpm> yeah, that was it, thanks dholbach <dholbach> cool <zyga> fg <dholbach> zyga, what does force-push mean in the MP= <dholbach> ? <zyga> dholbach: bzr push --overwrite <zyga> dholbach: before it lands that's the best way to do it <dholbach> ah, so you're asking yashi to push --overwrite to his branch? <zyga> dholbach: lp tracks past in case someone wants to do data mining but for everyone else it gets rid of "fixup stuff" commits that are just noise <zyga> dholbach: ys <zyga> yes* <dholbach> ok <zyga> dholbach: if you want I can fix and land this myself in 5 minutes <zyga> dholbach: do you want me to fix that quickly? <dholbach> zyga, I don't know - I just noticed that the test was broken <zyga> dholbach: yes, we know about it, I think I will just fix it now <dholbach> ok <victorp> pitti, hey - got home and I am able to ssh over wifi to the pi. Thanks! <pitti> victorp: cool! <pitti> victorp: wipi! <victorp> hehe <mvo> vmayoral: this will work lp:~mvo/snappy/snappy-classic-mode but its not the final on-disk layout and the comandline will be slightly diffrent <vmayoral> mvo: great, thanks a lot. I'll have a look <mvo> vmayoral: happy to give you a binary and/or talk more later <vmayoral> mvo: that'll be great! let's do that <Chipaca> mvo: tell me about that branch; does it need reviewing, or is it in progress? <mvo> Chipaca: it needs to actually go back to WIP <Chipaca> done :) <mvo> Chipaca: because there were some changes during the sprint how its constructed etc <mvo> Chipaca: thanks! <vmayoral> sergiusens: getting https://gist.github.com/vmayoral/b3ea80d53d5fe25e3ed2 when trying to upload the snap to the store <vmayoral> sergiusens: the framework doesn't exist so it just rejects it <sergiusens> vmayoral, I'll accept it <sergiusens> vmayoral, do you have the link? <jdstrand> beuno: hey, pindonga was working on the issues found here: https://myapps.developer.ubuntu.com/dev/click-apps/3560/review/r/2/. it turned out to be that the server isn't setting the proper local and it has nothing to do with my snap. he approved the last one but isn't here now. would you mind approving this one? <vmayoral> sergiusens: so i actually don't think that the snap get's even submitted <vmayoral> sergiusens: it gets rejected before the review process complaining about the missing framework * jdstrand -> gone for a few hours <beuno> vmayoral, I think you can click and ask for a manual review <vmayoral> sergiusens, beuno: stucked at this form https://myapps.developer.ubuntu.com/dev/click-apps/upload/?format=snap <vmayoral> i believe the manual review process is available in a later step, but let me know if i'm not looking at the right place <beuno> ah <beuno> so we need to add that framework first <beuno> nessita, ^ <beuno> vmayoral, what's the string? * Chipaca hopes it's vmayoral-the-magnificent <vmayoral> beuno: the framework has been named "raspivid" <nessita> beuno, hello <sergiusens> beuno, fyi, they use a framework, I guess we just need to add it to the framework list <beuno> vmayoral, done <sergiusens> beuno, I think i can do that <beuno> sergiusens, indeed <beuno> done already <nessita> even better <vmayoral> beuno: trying again, thanks! <vmayoral> beuno, sergiusens: it got in https://myapps.developer.ubuntu.com/dev/click-apps/3591 <vmayoral> beuno, sergiusens: remaking the snap to fix the errors <sergiusens> vmayoral, awesome, no inlfight installation ftw ;-) <sergiusens> vmayoral, oh, run click-review from your host/laptop <vmayoral> sergiusens: in the store already, we were missing a "description" field. <sergiusens> vmayoral, great <lool> vmayoral: I found the issue with ros/cmake/tests <lool> vmayoral: in the process, I found it hard to move the directory around, clean didn't clean up enough <lool> vmayoral: that is, I copied to a different dir, ran snapcraft clean, and then snapcraft build failed because of a ton of generated files hardcoding the previous path <lool> vmayoral: this was really hard to fix, would you know a clean way? <lool> oh shit, I take it back, the error is still there :-( <vmayoral> lool: so generally, "cakin_make clean" does a good job on that. Wanna join us in the room or should i "screen -x"? <plars> elopio: sorry, I had already gone to sleep when you sent that <plars> elopio: elasticsearch seems to have blown up on me, so I can't see much right now, let me sort out what happened with that and get you to retry <olli> ueh <dholbach> sergiusens, https://code.launchpad.net/~dholbach/snapcraft/fix-pep8-and-doc-indentation/+merge/273195 updated <plars> elopio: when you have a chance, could you try again? <elopio> plars: I've launched a new run. <jdstrand> popey: hey, you around? (quick store review) <popey> jdstrand: ya <jdstrand> popey: would you mind taking a look at https://myapps.developer.ubuntu.com/dev/click-apps/3560/r/2/? there are two review failures but it is due to a server side issue that pindonga has the fix for bt that hasn't rolled out yet. the snap is fine <jdstrand> popey: he approved 0.1 and it had the same to review failures <popey> okay <jdstrand> two* <plars> elopio: It looks like it's done, but I didn't see it execute any test commands, last I saw it was trying to boot the test image <plars> elopio: perhaps the test image didn't boot? <elopio> plars: can you take a look at the script to see if I'm doing something stupid? <plars> elopio: I really think the test image didn't boot <elopio> plars: if that happens, there will be a ssh timeout and the test will fail. <jdstrand> popey: thanks! :) <elopio> but it always says pass. And I get no payload. <plars> elopio: no, it won't even get that far if it can't confirm that the image booted <plars> elopio: it won't even try to run the tests <plars> elopio: I'm kicking off a test job of mine to see if something else could be causing this <elopio> ok <plars> grr... logstash broke again <plars> this was supposed to work <victorp> anyone knows if I have to include a .service file on a snap service or if that is taken care on its own? <Chipaca> victorp: you do not have to include a .service file <Chipaca> victorp: in fact it will be ignored :) <victorp> Chipaca, so any idea why when I restart the service I have sideloaded as a snap I get an error ...ICLGcNeLFEPe.service failed to load: No such file or directory <Chipaca> victorp: that's a bug <Chipaca> victorp: in particular, one we've fixed <victorp> hehe <Chipaca> victorp: but i'm bad at tracking where it is in the pipeline to you <victorp> ok, I shall ignore then <victorp> Chipaca, np, I was just thinking I might be doing something wrong, I will ingore it for now and continue <Chipaca> the error is real, but if it's not blocking you, sure <victorp> is not blocking <Chipaca> ok :) <victorp> service runs fine from a restart of the pi * Chipaca nods <Chipaca> victorp: and you can probably find the right service and restart it using systemctl, if i remember that bug correctly <Chipaca> hmm <Chipaca> victorp: just reproduced in latest stable, so the fix isn't there <victorp> ack <Chipaca> ... this might be a different bug <Chipaca> victorp: um. What I'm seeing is that it's not forgetting about the old service <Chipaca> victorp: that is, "snappy service status" shows the old one and the new one <victorp> oh <victorp> yeah I saw that too <Chipaca> victorp: but the new one is running alright <fgimenez_> have a nice weekend o/ <Chipaca> pitti: you around? <mwenning> Hi snappy team, I did a sudo snappy update and then rebooted, grub comes up with system-b , goes thru a certain amount of booting, then gets a kernel panic and starts over. Is there a way to manually switch back to system-a? <Chipaca> mwenning: it should switch back on its own <Chipaca> mwenning: what system is this? <Chipaca> of it *isn't* switching on its own, i'd love to have a look at the system, if it is image'able <mwenning> Chipaca, switch to snappy-internal #snappy 2015-10-03 <yashi_> elopio: pushed with --overwrite <DexterF> hi <DexterF> I'd like to have the 4.2 kernel from snappy in ubuntu-mate pi2 edition, is there a deb package I can download and install there? <DexterF> heya <DexterF> does anybody have core 15.04 running right now and could get me the .config file of the latest kernel, or tell me where I can get it? #snappy 2015-10-04 <hadeska> im trying to add a physical network interface to a lxd container on ubuntu core but it doesnt seem to work , anyone could help ? <shuduo> anyone has run Victor Palau's glowapi on RPi2? I always got 404 error with the REST api link (replaced with real IP). <yashi_> Chipaca: thank you for merging my change <yashi_> Chipaca: however, merge seems to be done only for python3. <yashi_> Chipaca: http://bazaar.launchpad.net/~yashi/snapcraft/snapcraft/revision/210 has both 2 and 3, though. <Chipaca> yashi_: i merged sergio's branch, which was a branch of yours <DexterF> hi <Chipaca> yashi_: not sure if that answers it <Chipaca> DexterF: hi <Chipaca> shuduo: i haven't, but, what rest api link? <DexterF> I'd like to run the snappy kernel on Ubuntu Mate for Raspi2. My idea was get the snappy kernel source and just dpkg-buildpackage it, but I cannot find the src. help? <Chipaca> DexterF: there aren't snappy kernels <Chipaca> DexterF: just kernels <Chipaca> DexterF: that are used by snappy <DexterF> https://developer.ubuntu.com/en/snappy/ <- what would you call the kernel that the pi2 image here contains? <DexterF> or rather this one http://people.canonical.com/~platform/snappy/raspberrypi2/ubuntu-15.04-snappy-armhf-rpi2.img.xz <DexterF> either way, the kernel that that image boots, I'd like to port that to ubuntu-mate/pi2. pointers appreciated. <Chipaca> DexterF: i presume ubuntu-mate/pi2 is ubuntu? * Chipaca downloads ogra_'s rpi2 image to take a look <DexterF> no, it's slackware with a ported GNU/Herd kernel running on a Sun. <DexterF> that's why it is called ubuntu-something <Chipaca> DexterF: in that case, the kernel it uses is an ubuntu package, from an ubuntu archive <DexterF> Chipaca: I had a look at the ubuntu git tree but could not find it. <Chipaca> DexterF: couldn't find what? <Chipaca> the kernel used in ubuntu-mate/rpi2, or the kernel used in snappy ubuntu core for rpi2? <DexterF> the ubuntu package for that kernel. <Chipaca> the kernel used in ubuntu-mate/rpi2, or the kernel used in snappy ubuntu core for rpi2? <DexterF> the one used in snappy <DexterF> or snappy ubuntu core if you prefer <Chipaca> DexterF: did you find the other one, then? <DexterF> Chipaca: is the plain linux-source package that comes with the distro, so yes. but that's a 3.18 kernel so making a config from that is a bit tedious, plus I don't know if I could just like that port it to a vanilla 4.2 src <Chipaca> DexterF: can you point me at where that package comes from? <Chipaca> DexterF: apt-get --print-uri would probably help <DexterF> apt-get install linux-source. wherever it gets those. <DexterF> sec <DexterF> E: Command line option --print-uri is not understood <Chipaca> --print-uris <DexterF> neither <Chipaca> tab is your friend <DexterF> apt-get --print-uris linux-source <DexterF> E: Command line option --print-uris is not understood <Chipaca> apt-get install --print-uris linux-source <DexterF> linux-source is already the newest version. :) I try and force, sec <Chipaca> --reinstall <DexterF> did that, does not become any more verbose either. I'll uninstall, if that don't help... <DexterF> ill wireshark... <DexterF> no, not even now. let me check sources.. <Chipaca> hold on <Chipaca> what are you doing, exactly <DexterF> trying to get apt to tell me where it gets the linux-source package, since you asked for that <Chipaca> DexterF: show me the command you are entering <DexterF> apt-get install --print-uris linux-source <DexterF> after purging the package <Chipaca> and what is the output? pastebin it please <DexterF> http://pastebin.com/ThshALLL <Chipaca> this is what you *should* be getting: <Chipaca> apt-get -qq install --print-uris --reinstall linux-source <Chipaca> 'http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-source-4.2.0_4.2.0-12.14_all.deb' linux-source-4.2.0_4.2.0-12.14_all.deb 107776972 MD5Sum:fa90f64d3f1132715605b64e146ff992 <Chipaca> 'http://archive.ubuntu.com/ubuntu/pool/main/l/linux-meta/linux-source_156.14.161.142.12_all.deb' linux-source_156.14.161.142.12_all.deb 2184 MD5Sum:68331205b67b02230581fe26a54ffd52 <Chipaca> no purging necessary <Chipaca> this is for an amd64 box, but it shouldn't make a difference <Chipaca> can you, in fact, install that package? <DexterF> Chipaca: the package installs fine <Chipaca> strange <Chipaca> DexterF: the reason i'm asking is because until very recently we didn't have an ubuntu kernel that worked properly on the raspberry pi 2 <Chipaca> DexterF: so I don't know where ubuntu-mate/rpi2 is getting its kernel <Chipaca> DexterF: but it's not an ubuntu kernel <DexterF> Chipaca: who is "we"? <Chipaca> DexterF: humanity <DexterF> ... <Chipaca> DexterF: so that's probably a linux kernel from e.g. raspbian <DexterF> I'll ask them. what you say is a bit strange, though, a gernem IT newspage (still one of the better ones) announced that snappy ubuntu core now has a spanking new 4.2 kernel with full raspi2 support. hence my question who "we" was, assuming you are a snappy developer <Chipaca> I am <Chipaca> ogra_ will know more about the kernel without having to dig -- sorry i wasn't able to help you dig further <Chipaca> however he is off today <Chipaca> DexterF: i don't see why you say it's strange <Chipaca> DexterF: what I'm saying is completely compatible with what you say that newspage says <DexterF> Chipaca: maybe I get somethign wrong here: for a moment assume I know linux for a bit and then tell me, what is snappy and what is ubuntu core? <Chipaca> DexterF: ubuntu core is a minimal ubuntu flavour, aimed mostly at people building appliances or single-purpose servers <Chipaca> more or less :) <DexterF> ok. and snappy? <Chipaca> DexterF: snappy is a new way of packaging a distribution that uses transactional updates on a mostly readonly system <DexterF> transactional mainly means: there are rather images than packages that get mounted over an existing tree? <Chipaca> DexterF: evolved from the tech we (ubuntu) developed for the phone <Chipaca> DexterF: transactional meaning the system updates as a whole, or fails to update as a whole <DexterF> mmmmmhnope, don't get it <Chipaca> DexterF: what don't you get? <DexterF> the "updates or fials as a whole" thing. <DexterF> at tech level, how are snappy... "packages" different from say deb packages <Chipaca> ah <Chipaca> DexterF: snaps have a much simplified dependency structure; no libaries, no conflicts, just a dependency on frameworks can be expressed. Snaps are not extracted into a common directory, but into their own little place, and when the services and binaries in them are run, they do so in their own little jail <DexterF> Chipaca: how is that different from Docker or LXC? <Chipaca> DexterF: how is that the same? <DexterF> well, put everything required to run the package in a sandbox that does not depend on much <Chipaca> DexterF: aren't those entire systems? don't you actually boot those? <DexterF> but anyway, maybe I'm not doing this right: all I need is a minimalistic distro that brings me the comfort of central package management like apt, zypper, yum or whatever and a kernel running on a raspi2 including i2c and all, which would be 4.2 and higher. <DexterF> Chipaca: uh, no, those are container concepts, these run against the same kernel as the host system <Chipaca> DexterF: but you boot the container <Chipaca> DexterF: with its own init and all <DexterF> so maybe I should rather look at ubuntu core? but 4.2 is a must, hence that news item got my attention <DexterF> Chipaca: good question, I actually only read up on docker and lxc but never implemented a setup <Chipaca> DexterF: https://lists.ubuntu.com/archives/snappy-devel/2015-September/001058.html <Chipaca> DexterF: that answers several of your questions, i think <Chipaca> including the name of the source of the kernel package <giminni> hello I have a problem to execute "docker exec -ti <progname> bash the message output is "type=1400 audit(1443969471.682:30): apparmor="DENIED" operation="open" profile="docker_docker-daemon_636-721-3251" name="/" pid=<pid-#> comm="docker.x86_64" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 How can I exec into a running container? even docker attach is hanging arount, appreciate any hints on that <giminni> I am running the latest snappy & updates <giminni> (amd64)ubuntu@localhost:~$ docker info <giminni> Containers: 2 <giminni> Images: 43 <giminni> Storage Driver: aufs <giminni> Root Dir: /var/lib/apps/docker/636-721-3251/aufs <giminni> Backing Filesystem: extfs <giminni> Dirs: 47 <giminni> Dirperm1 Supported: true <giminni> Execution Driver: native-0.2 <giminni> Kernel Version: 3.19.0-28-generic <giminni> Operating System: <unknown> <giminni> CPUs: 1 <giminni> Total Memory: 741.1 MiB <giminni> Name: localhost.localdomain <giminni> ID: 7M25:QCMT:AQJM:X5HZ:PVLW:CK7A:4VYA:7CIP:GLOK:HXA7:UGV5:L2EI <giminni> WARNING: No swap limit support <giminni> (amd64)ubuntu@localhost:~$ docker version <giminni> Client version: 1.6.2 <giminni> Client API version: 1.18 <giminni> Go version (client): go1.4.2 <giminni> Git commit (client): 8f2d6e5 <giminni> OS/Arch (client): linux/amd64 <giminni> Server version: 1.6.2 <giminni> Server API version: 1.18 <giminni> Go version (server): go1.4.2 <giminni> Git commit (server): 8f2d6e5 <Chipaca> giminni: suggest you ask again tomorrow; most people are off today <giminni> thx I'll do that tomorrow <shuduo> Chipaca, http://victorpalau.net/2015/10/02/piglow-api-one-small-snap-for-humanity/ <Chipaca> shuduo: has the service started successfully? <Chipaca> shuduo: "snappy service status" should tell you <shuduo> Chipaca, i can see glowapi status is "enabled; loaded; active (running)" <Chipaca> shuduo: ok. And can you connect to port 8000 from the board itself? <Chipaca> e.g. by doing "telnet localhost 8000" <shuduo> Chipaca, there is no telnet in snappy image. should i install it? <Chipaca> ah, that's true <Chipaca> netcat (nc) <Chipaca> shuduo: i mean: nc localhost 8000 <shuduo> Chipaca, yes, it stuck now and no output <Chipaca> shuduo: write "GET /" and hit enter twice <shuduo> Chipaca, it outputs "HTTP/1.1 400 Bad Request" <shuduo> Chipaca, btw, i just hit once then it exit with above output <Chipaca> shuduo: so, piglow is listening to port 8000 <Chipaca> shuduo: and if you use your external address instead of localhost? <shuduo> Chipaca, yes, i just tried again and it returns "404 page not found" <Chipaca> shuduo: where did you try that from? <Chipaca> because 404 is not 400 <Chipaca> it's a different response <Chipaca> and it shouldn't be <shuduo> i paste victor's link to my browser and replace localhost with its real ip address <Chipaca> shuduo: ok, backpedal a bit <Chipaca> shuduo: first, none of those urls are browser-friendly <Chipaca> shuduo: because they all need to be POST <Chipaca> and if you're just writing the url in your browser it won't work <Chipaca> give me a bit <Chipaca> shuduo: are you ssh'ing in to the board, or are you typing at it manually? <shuduo> Chipaca, i tried to copy an example code of using nc to send POST to localhost but it returns 400 error. i guess my command is not correct. <shuduo> Chipaca, i'm sshing <Chipaca> shuduo: try this: python3 -c 'from urllib.request import urlopen; print(urlopen("http://localhost:8000/v1/on", data=b""))' <shuduo> Chipaca, cool. it works now. piglow be turned on for 1 sec. thanks <Chipaca> ah, missing a .read() there <Chipaca> shuduo: try this: python3 -c 'from urllib.request import urlopen; print(urlopen("http://localhost:8000/v1/on", data=b"").read())' <Chipaca> shuduo: now, that's still localhost <Chipaca> shuduo: try it remotely, does that work now? (change "localhost" to the right ip) <shuduo> Chipaca, with read(), it looks same. led turned on for 1 sec and exit. <Chipaca> that's ok. It's just that if the piglow returned anything, without the read() you wouldn't see it <Chipaca> shuduo: try it remotely; if that works, you're set, but i suspect there's something else going on as well <shuduo> Chipaca, yes, remote accessing works good too. <Chipaca> ah, neat <Chipaca> i wonder why the browser was saying 404 instead of 400 <Chipaca> anyway, never mind, it works \o/ <Chipaca> shuduo: if you want to make it work with a browser, you need to write some html <Chipaca> shuduo: and probably some javascript in the html unless you just want to hit one endpoint :) <Chipaca> e.g. <form action="http://the.ip:8000/v1/on"><input type=submit value=on></form> <shuduo> Chipaca, got it. i see someone can control piglow by an app from ubuntu phone on a video. #snappy 2015-10-05 <zyga> good morning <zyga> mvo: hey, did you have a safe trip home? <dholbach> good morning <fgimenez> good morning <clobrano> morning o/ <Chipaca> *yawn* <Chipaca> morning! <Chipaca> mvo: o/ <mvo> hey Chipaca! good morning <Chipaca> mvo: welcome back to the world of the living mr mvo! <Chipaca> mvo: hope you've been able to rest and snuggle the family :) <mvo> Chipaca: :) thanks! I did and it was very nice. I am currently write down all that I can remember from the sprint <Chipaca> mvo: good idea. carry on. :) <mvo> Chipaca: is there anything I can do for you? <mvo> Chipaca: I guess code reviews? <mvo> Chipaca: (haven't really looked yet :( <mvo> Chipaca: I will certainly need a break from spec writing at some point <Chipaca> mvo: don't worry about it *until* you need that break :) <Chipaca> i'm in no hurry <Chipaca> puzzled by things that are nil not being equal :) <mvo> Chipaca: heh :) <Chipaca> i've got thing != nil, but thing == (*snappy.SnapPart)(nil) <Chipaca> *head scratch* <Chipaca> on the upside, tests are hitting some weird corner cases :D <mvo> woah <Chipaca> ah, i know why; thing is an interface <Chipaca> interface value <Chipaca> \o/ <JamesTait> Good morning all; happy Monday, and happy Teachers' Day! ð <dpm> dholbach, it seems now LP can build snaps http://blog.launchpad.net/general/launchpad-news-september-2015 <dholbach> yep, great news, isn't it? :-D <dholbach> I'm just finishing my patch pilot shift today, then I'll go and play around with it and then write a blog post :) <dpm> cool :) <Chipaca> with bug 1487010 still stuck, that means no race detector for go in wily, right? <ubottu> bug 1487010 in golang (Ubuntu) "please upload new package to reenable go's race detector on wily" [Undecided,In progress] https://launchpad.net/bugs/1487010 <squll> Hello, I have a .snap file. We are wondering how to run this? <mvo> squll: run "snappy install your-snap" on a snappy system, snaps will only work on snappy systems, i.e. http://ubuntu.com/snappy <Chipaca> mvo: any chance of a review on https://code.launchpad.net/~chipaca/snappy/activate-package/+merge/272716 ? <Chipaca> mvo: http://i.imgur.com/UnlYwpF.jpg <squll> built a snappy file, still no clue on running that <squll> Anyone got tips? <Chipaca> squll: how did you build it? <squll> snappy build . <Chipaca> squll: and how did you try to run it? <squll> We still have no clue on even how to run that <Chipaca> squll: and, more interestingly for me <Chipaca> ok <squll> And Googling 'How to run a snappy app' gives me alot of information on building <squll> But I am not really seeing a command or something like that to run it <Chipaca> squll: did you see mvo's reply to you the first time you asked? <Chipaca> squll: how do you run an apk? <squll> No I did not <Chipaca> <mvo> squll: run "snappy install your-snap" on a snappy system, snaps will only work on snappy systems, i.e. http://ubuntu.com/snappy <squll> Yes I saw that <squll> We did that indeed. <squll> snappy versions gives us a list with that name in the list <squll> But then I want to run it (it gives me data when executing it) <Chipaca> squll: sorry, i'm not sure i understand <Chipaca> squll: did you install the snap in a snappy ubuntu core system? <squll> Yes we did <squll> We have an Erle Rover (robot) with an small pc on it running snappy Ubuntu Core <Chipaca> squll: ok <Chipaca> squll: and does your snap have binaries, services, both, ...? <squll> We are able to connect to the snappy app webinterface where we were able to run the HelloWorld snap. We find a hello-world.canonical file after some searching. That is indeed running and echo'ing hello world as expected. <Chipaca> squll: does *your* snap, the one you built, have binaries, services, both, ...? <squll> So then we go along and follow the tutorial of the vendor of our robot containing a snappy which prints out the date. <squll> No it does not <Chipaca> what prints out the date? <squll> Well, we just don't really understand what we should expect after like a succesful build. Do we get a .canonical file or somthing? <squll> It's just some C++ code, let me look up if there is a public github <Chipaca>
{'channel': 'snappy', 'month': 10}