/srv/irclogs.ubuntu.com/2016/01/05/#snappy.txt

=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
fgimenezgood morning08:18
JamesTaitGood morning all; happy Tuesday, and happy Golden Gate Bridge Day! 😃09:39
=== shuduo is now known as shuduo-afk
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== kickinz1_ is now known as kickinz1
Chipacastevebiscuit: mo'in!11:01
Chipacastevebiscuit: a question that suddenly came to me11:01
Chipacastevebiscuit: why is webdm fetching the icon?11:01
Chipacastevebiscuit: (as opposed to giving the url to the browser and letting it figure it out)11:02
stevebiscuitChipaca: hello!11:08
LefterisJPhello11:09
stevebiscuitChipaca: the browser could handle things for uninstalled packages as the icon path would be something on the store11:09
LefterisJPWhen using snappy-remote, to upload a testing snap to a snappy target is it supposed to give some form of progress bar? I would like to determine if my process is stuck or if it's actually doing something11:10
stevebiscuitChipaca: for installed packages, the path would be something like "/1.0/icons/myapp.myorigin/icon" which would be unaccessible11:10
Chipacahurr durr11:11
Chipacastevebiscuit: sorry i even asked :-)11:11
stevebiscuitChipaca: not to worry, I had to double check!11:12
LefterisJPHey all got a question. I am trying to deploy some test snapps from the snapcraft examples. The host is an Ubuntu 14.04 LTS and the snappy target is a Raspberry PI.11:47
LefterisJPWhen I do snapcraft the resulting .snap file has amd64 in its name and when I try to deploy with snap-remote I get this error:11:48
LefterisJP/tmp/webcam-webui_1_amd64.snap failed to install: package's supported architectures (amd64) is incompatible with this system (armhf)11:49
LefterisJP 11:49
LefterisJPHow can I generate a .snap file for specific architecture?11:49
LefterisJPhmmm is anyone seeing my messages/questions or is there a problem with my IRC client :-) ?12:06
ChipacaLefterisJP: wait a bit for sergiusens or kyrofa to be around, i think12:15
Chipacastevebiscuit: how much do we care about somebody calling their icon something utf8-ish?12:15
kyrofaGood morning12:17
stevebiscuitChipaca: good question, when a snap is built will it allow a utf8 filename?12:18
Chipacastevebiscuit: let's assume no, at least for now12:19
kyrofaLefterisJP, I believe snapcraft needs to be run on the target arch12:19
stevebiscuitChipaca: grand, I'm happy to abdicate the responsibilty :)12:20
Chipacastevebiscuit: especially because what we do know is incorrect for utf8 filenames only on firefox12:20
Chipacawhich does blow my mind a little bit12:20
Chipacaand not in a good way12:20
Chipacaalthough that's 2013 info; might need updating12:21
LefterisJPkyrofa: thanks for the reply. So I would have to install snapcraft in a Raspberry PI and then build the package there?12:23
kyrofaLefterisJP, I believe so, assuming you're compiling (last I checked snapcraft didn't support cross-compiling)12:25
kyrofaLefterisJP, or in an arhm qemu or something12:26
kyrofas/arhm/arm/12:26
sergiusensgood morning12:33
kyrofaMorning sergiusens :)12:35
kyrofasergiusens, to double check: to build an armhf .snap with snapcraft, snapcraft needs to run on an arm, right?12:35
sergiusenskyrofa, today, yes12:36
LefterisJPor in general what is the recommended way to build for Raspberry PI target from an Ubuntu host.12:36
sergiusenskyrofa, you are up early, or maybe I am up late :-P12:37
kyrofasergiusens, yeah a little. This time of year exercising in the morning sucks12:38
kyrofasergiusens, so I'm trying to shift my schedule back a little so I can exercise after work12:38
LefterisJPsergiusens: You mentioned today yes. Is there any plans to add support for compiling for RaspPi (armhf) from an Ubuntu host in the future?12:39
sergiusensLefterisJP, only ideas; probably mostly for things like go and node. Nothing stops you today from writing a custom plugin basing out of one of the existing ones that does just that for your needs though12:40
LefterisJPI am still getting my bearings as to how Snappy Ubuntu works and how I can accomplish my goals.12:41
LefterisJPThanks I understand.12:41
sergiusensLefterisJP, what are your goals?12:41
LefterisJPI may bother you guys a bit more with extra "newbie" questions.12:41
kyrofaLefterisJP, no bother!12:43
kyrofaLefterisJP, but yeah, if you can explain what exactly you're looking to accomplish, we can probably point you in the easiest direction12:50
LefterisJPI am working for slockit (http://slock.it/) and am trying to evaluate and see if it makes sense to use Snappy Ubuntu for our work. I am trying to gather as much info as possible to creating Snappy Frameworks as my final goal is to create an Ethereum(https://ethereum.org/) Snappy Framework which other Snappy apps can utilize.12:53
LefterisJPAt least for now for testing purposes I use a Raspberry Pi as my testing target environment12:53
kyrofaLefterisJP, for evaluation purposes perhaps it would be easier to use an amd64 virtual machine running snappy?12:54
kyrofaLefterisJP, a qemu VM is just going to be slow is all12:55
sergiusenskyrofa, btw are you on xenial?12:55
kyrofa(an arm one anyway)12:55
sergiusenskyrofa, I am seeing this with the tests http://paste.ubuntu.com/14410381/12:55
sergiusensbut it does not happen on travis12:56
kyrofasergiusens, no I'm on trusty :P12:56
kyrofasergiusens, huh, that doesn't look good12:56
kyrofaLooks like the mock lib changed... ?12:57
sergiusenskyrofa, indeed12:57
kyrofagrr... breaking api...12:57
kyrofasergiusens, I'm not sure how to fix that in a backward-compatible way12:58
sergiusenskyrofa, I'll look into it12:58
kyrofasergiusens, alright let me know. I can fire up a xenial lxc in no time12:58
sergiusenskyrofa, I can do it with more code12:59
sergiusenskyrofa, the problem is the error 'helper' message when the assertion fails13:00
kyrofasergiusens, oh. Did they just remove support for it?13:00
sergiusenskyrofa, I don't think it was removed entirely as I use it too and those don't fail (Equal), only in the called one it seems13:01
kyrofasergiusens, worst case we can just remove the helper message and that will work on all versions13:01
* sergiusens checks the docs13:01
sergiusenskyrofa, I;ll leave the message, don't worry ;-)13:01
sergiusenseasy to fix13:01
sergiusenskyrofa, so even worse, nothing changed; assert_not_called only exists in 3.5 and trusty uses 3.4 so you were tricked by the mock's consumtion of anything it was called with :-P13:11
kyrofasergiusens, oh no13:11
kyrofasergiusens, that's _terrible_13:11
kyrofasergiusens, oh, so embarrassing :P13:11
kyrofasergiusens, easy fix though13:13
sergiusenskyrofa, yeah, done already; taking more time to think of a commit message than anything else :-13:13
sergiusens:-P13:13
kyrofasergiusens, just using .called?13:14
sergiusenskyrofa, yeah13:14
kyrofasergiusens, great, thanks for mopping up behind me13:14
sergiusenskyrofa, https://github.com/ubuntu-core/snapcraft/pull/20013:14
LefterisJPSo I have a bit more general question. Once you make an app or Framework for Ubuntu core it does not mean that it will run on every device running Ubuntu core, right? It means only for devices having the same architecture? Then to support each device you would have to generate a .snap for that device's architecture separately?13:35
kyrofaLefterisJP, you have the right idea, although it's possible to create a .snap for multiple architectures if your project supports such a thing. An example might be a series of shell scripts, or something you've already compiled for other architectures13:36
kyrofaLefterisJP, keep in mind that you don't HAVE to have snapcraft build your snap for you. In current releases you can just snappify a directory with snappy build (future releases moves that functionality into snapcraft, but you can still just snappify a directory)13:37
LefterisJPinteresting, where can I find more information for multiple architectures projects? I mean I saw some projects adding an architectures list in the yaml file, like: `architecture: [amd64, armhf]` but how can you specify the rules as to how to build each architecture.13:41
kyrofaLefterisJP, that's what I'm saying-- if you want snapcraft to do the building for you, you're going to be stuck with the host arch13:49
LefterisJPhmm okay13:50
kyrofaLefterisJP, however, let's pretend your project was written in go, or C++. Let's say you built it yourself for multiple architectures and ended up with a binary for each13:50
kyrofaThen you name them according to their arch: project_amd64, project_armhf, etc13:51
kyrofaLefterisJP, then you make a shell script that looks at the current arch, and launches the right onw13:51
kyrofaone*13:51
kyrofaLefterisJP, now that shell script is your snappy binary13:51
kyrofaLefterisJP, and voila, you support multiple architectures in the same .snap13:51
kyrofaLefterisJP, and you don't need snapcraft to build it-- just setup the meta/package.yaml etc. accordingly and run snappy build13:52
LefterisJPkyrofa: Thank you for your help13:56
LefterisJPIs there any blog post or tutorial or something I can use for reference for this?13:56
LefterisJPI found this to be useful: https://insights.ubuntu.com/2015/06/03/so-you-want-to-write-a-snappy-app/13:56
kyrofaLefterisJP, of course, it's why we're here :) . And yeah, that sounds kinda like what I described, nice13:58
kyrofaLefterisJP, and we are indeed trying to make that better in snapcraft. But supporting cross-compiling for all the supported possibilities in a general way is a difficult problem to solve14:04
LefterisJPyeah I understand. I had seen a presentation by Maarten Ectors in (Ethereum) Devcon1 about Ubuntu Core and I had understood that you had somehow had a magical way to cross-compile for everything already. I know it's a hard problem to solve, but who knows, with enough research and work many architectures may be supported.14:08
LefterisJPAre these snapcraft pluging used for cross-compiling? https://github.com/ubuntu-core/snapcraft/tree/master/snapcraft/plugins14:08
sergiusensLefterisJP, no, those are just used for building natively14:11
sergiusensyou can override them and support a specific target if you want14:11
LefterisJPI see. Then just out of curiosity in which part of the system would any cross-compiling capability be built (in the future as you said)14:13
sergiusensLefterisJP, in the plugin itself14:13
sergiusensas each plugin (tech) uses a different mechanism to support this14:13
kyrofaLefterisJP, right, cross-compiling C++ is different than cross-compiling Go, for example14:14
LefterisJPyeah I know :(14:16
LefterisJP2 clients exist for Ethereum, one in Go and one in C++. I like C++ a lot myself but well ... cross-compiling it for different architectures is painful14:17
kyrofaLefterisJP, yeah that's my favorite14:17
kyrofaI'm afraid snapcraft isn't going to be the C++ cross compiling silver bullet though, sorry :( . At least... not yet ;)14:18
kyrofaLefterisJP, what build system does the C++ client use?14:18
LefterisJPcmake14:20
kyrofaLefterisJP, well at least you have that-- cross compiling is a little easier with a good build system obviously14:22
* kyrofa 's day always improves when he thinks he's out of coffee... and then discovers there's actually a little bit left14:30
kyrofasergiusens, standup?14:32
sergiusensoops14:32
=== greyback__ is now known as greyback
LefterisJPwhere you guys located at? Europe or US or both?14:50
enoch85ping kyrofa15:05
kyrofaHey enoch85 :)15:06
enoch85kyrofa, so I installed Ubuntu Snappy once again, and didn't touch anything else. what would be the next step?15:07
enoch85kyrofa, do I build the ownCloud.snap seperatly from the system, and can this be done inside a VM?15:07
enoch85kyrofa, can I use my scripts in the .snap or do I have to build it from schratch?15:08
kyrofaenoch85, in order to develop the .snap, I'd ignore the rpi2 for now and do this on your dev machine15:08
enoch85kyrofa, ok, where do I begin?15:09
kyrofaenoch85, well, assuming you're running Ubuntu on your dev machine. Are you?15:09
enoch85yes15:09
kyrofaenoch85, which version?15:09
enoch85on my laptop I have Ubuntu Mate 15.10, and when I develop scripts and such I usually do this on a Ubuntu Server VM15:10
enoch85kyrofa, sorry forgot to mention you...15:11
kyrofaExcellent. First of all, get snapcraft setup (https://developer.ubuntu.com/en/snappy/build-apps/get-started/)15:12
kyrofaenoch85, haha, no problem15:12
kyrofaenoch85, let me fire up a 15.10 lxc real quick so I can walk through with you15:13
enoch85kyrofa, hmm, so I can make a standard VM and use snapcraft to compile it onto snappy? that would be awesome!15:13
enoch85kyrofa, ok!15:14
kyrofaenoch85, indeed15:14
enoch85kyrofa, yeah, and I will create a dev envirroment I think... to keep things seperated.15:15
enoch85kyrofa, which one do you recomend?15:15
enoch85kyrofa, server or desktop?15:15
kyrofaenoch85, what virtualization tech are you using?15:15
enoch85kyrofa, VMware Workstation15:16
kyrofaenoch85, short answer is server-- you won't need a GUI15:16
kyrofaenoch85, but it won't hurt anything to have a gui either15:16
sergiusenskyrofa, this was fixed, right? https://bugs.launchpad.net/snapcraft/+bug/152437415:16
ubottuLaunchpad bug 1524374 in Snapcraft "Snap fails to build with "Bad Variable Name"" [Undecided,New]15:16
enoch85kyrofa, ok, but will it end up in alot of files all over the place, or is it clean in case I want to remove it later, in that case I don't need to create a seperate VM15:16
enoch85enoch85, I can just use my laptop as dev machine15:17
kyrofasergiusens, yes I believe so-- let me verify15:17
kyrofaenoch85, the files it creates are pretty localized15:18
kyrofasergiusens, yes: https://github.com/ubuntu-core/snapcraft/pull/16115:19
kyrofaenoch85, assuming you're talking about the process of building a .snap15:19
enoch85kyrofa, so basically purge snappy-tools when I'm done?15:20
sergiusenskyrofa, I can't remember when we did the split; I'll mark it fixed commited for trunk but leave it open for 1.x15:20
enoch85kyrofa, yes, that as well15:20
kyrofasergiusens, I think it was after, so that sounds good15:20
kyrofaenoch85, ah, yeah. And remove the PPA15:21
kyrofaenoch85, of course if you're worried, virtualize it (I do)15:21
enoch85kyrofa, ok, then let's go15:21
enoch85kyrofa, naah, I need to reformat my latop soon anyway, just another reason to do it if I choose not to proceed ;)15:22
kyrofaenoch85, hahaha, okay15:22
kyrofaenoch85, give me one sec, setting up...15:23
enoch85kyrofa, ok cool :)15:23
enoch85kyrofa, oh, nice progress bar when installing the tools15:23
enoch85kyrofa, can I get that in the server env as well?15:24
kyrofaenoch85, heh, I'm not sure what you're referring to15:26
enoch85kyrofa, I got a progress bar when I installed the tools, it appeard in the bottom line15:26
enoch85kyrofa, just wondering if I can script that in a regular apt-get upgrade command on a server for instance15:26
kyrofaenoch85, via apt-get? Yeah I'd assume that would be the same regardless of desktop or server15:27
enoch85kyrofa,15:27
enoch85cool15:27
enoch85kyrofa, anyway, on page 2 now in the guide15:27
enoch85kyrofa, snapcraft tutorial15:27
kyrofaenoch85, right, so, snapcraft is a tool that will build .snaps for you if you tell it your dependencies, etc.15:28
enoch85kyrofa, could I use ondrejs PPA for PHP 7 for instance?15:28
enoch85kyrofa, btw a completley doifferent question: will PHP 7 be optional in UBuntu 16.04?15:29
kyrofaenoch85, yes, but you'll need to write a custom snapcraft plugin for the nonstandard repo. And honestly I'm not sure regarding 16.0415:29
kyrofaenoch85, is PHP7 a requirement for owncloud nowadays?15:29
enoch85kyrofa, ok, so what I want is: LAMP with PHP 7 + ownCloud + some scripts that will be included in the snap at boot for the ownCloud. Basically, I want the same as I have today: https://en0ch.se/index.php/s/i3csGfYlpivkFvh15:31
enoch85kyrofa, not a requrement, but nice to have. speed things up quite a bit.15:31
enoch85kyrofa, please download and try if you have the time15:32
LefterisJPI am playing around with deploying a simple "Hello World" shell script snappy in a Pi and after succesfully deploying it with snappy-remote when I try to run it inside the Pi I get: `appname Test-snap-echo.sideload not allowed`15:33
LefterisJP 15:33
LefterisJPwhat am I doing wrong?15:33
kyrofaenoch85, alright. That sounds doable. I've not put together a php .snap before, so we may want to start with the default repos, just for simplicity for now15:33
enoch85kyrofa, yeah ok, and I (we) can develop it further later on15:34
enoch85:)15:34
kyrofaenoch85, exactly15:34
kyrofasergiusens, hey on wily, snappy-tools doesn't seem to include snapcraft?15:36
kyrofaSo enoch85 you'll need to `apt-get install snapcraft` as well15:38
enoch85kyrofa, on it15:38
sergiusenskyrofa, I'll add a note to check15:38
enoch85kyrofa, done15:38
kyrofasergiusens, just makes the docs inconsistent is all15:38
kyrofaAlright enoch85, let's first try to just make a .snap that has apache running15:39
enoch85kyrofa, ok15:40
enoch85kyrofa, LAMP**15:40
enoch85kyrofa, wouldn't it be possible to make a LAMP snap?15:40
kyrofaenoch85, haha, we're getting there15:41
enoch85kyrofa, ok15:41
enoch85:)15:41
kyrofaenoch85, but all the .snaps I've made so far are a little simpler. So we're going to learn together. Sound okay?15:41
enoch85kyrofa, very good. win-win15:41
kyrofaenoch85, I figure once we get a .snap with apache, we'll add PHP, then mysql, then owncloud15:42
enoch85kyrofa, into one snap, or seperate?15:42
kyrofaenoch85, into one15:42
enoch85kyrofa, ok cool15:42
kyrofaenoch85, alright, make sure you're here: https://developer.ubuntu.com/en/snappy/build-apps/your-first-snap/15:43
enoch85kyrofa, yes15:43
kyrofaenoch85, scroll down to the "Snapcraft Recipe"15:43
enoch85kyrofa, yes15:43
enoch85kyrofa, mkdir apache?15:44
kyrofaenoch85, so we use a file named `snapcraft.yaml` to instruct snapcraft on how to assemble our .snap15:44
kyrofaenoch85, make a folder for the overall snap. I'm making a ~/src/owncloud-snap folder15:44
enoch85kyrofa, ok15:44
kyrofaenoch85,  In that folder, create a snapcraft.yaml file15:45
enoch85kyrofa, touch i suppose?15:45
enoch85or just copy the text and add my things instead?15:45
kyrofaenoch85, or vi or some other editor, no matter. Right, take the text from the tutorial and alter to fit15:46
kyrofaenoch85, just the name through the icon15:46
kyrofaenoch85, generic metadata15:46
kyrofaenoch85, ooo, actually just run snapcraft init, haha15:46
kyrofaGet in that folder and run snapcraft init. Then alter the snapcraft.yaml to fit15:47
kyrofaenoch85, if I actually read the tutorial...15:47
enoch85kyrofa, haha ok15:47
enoch85sec15:47
enoch85kyrofa, sorry for noise:15:48
enoch85name: owncloud-server15:48
enoch85version: 115:48
enoch85vendor: Daniel Hansson <daniel@techandme.se>15:48
enoch85summary: ownCloud Server Snap15:48
enoch85description: ownCloud server is you self-hosted cloud15:48
enoch85icon: icon.png15:48
enoch85something like that?15:48
kyrofaenoch85, sure, that works fine15:48
LefterisJPguys ping: `appname Test-snap-echo.sideload not allowed` when trying to run a binary of an app I installed via snappy-remote. Why would I get this?15:48
kyrofaenoch85, make sure you actually have that icon. I use a .svg simply containing `<svg />` or something15:50
kyrofaenoch85, eventually we can actually use the owncloud icon15:50
enoch85kyrofa, was just about to ask... don't have an icon15:50
enoch85can copy one from ownCloud though15:50
kyrofaenoch85, that works15:50
enoch85kyrofa, yes15:50
enoch85sec15:50
kyrofaLefterisJP, is the shell script executable?15:53
enoch85kyrofa, saved that inside the owncloud-snap folder (my dev folder)15:53
enoch85kyrofa, togehter with the icon15:53
kyrofaenoch85, owncloud? That's fine, we won't use it just yet but it won't hurt anything. 8.2.2?15:54
LefterisJPkyrofa: yes15:54
enoch85kyrofa, yes, latest15:54
kyrofaLefterisJP, out of curiosity (not sure it will fix anything) try changing the name to something without hyphens and try again15:54
kyrofaenoch85, alright, so now let's tell snapcraft that we want apache15:55
enoch85kyrofa, exiteing!15:55
enoch85kyrofa, exciting!*15:55
LefterisJPkyrofa: Will do. Does that mean I need to purge it from the snappy target too? Also, my package.yaml calls the executable like:15:56
LefterisJP   exec: ./bin/testecho.sh15:56
LefterisJPdo I need to put sh in front? The script does have the shebang on the top15:56
kyrofaLefterisJP, no as long as the shebang is valid you should be good. And no, when you're sideloading you can load it right over the top15:57
kyrofaenoch85, so we're going to specify parts, like further in the tutorial15:58
enoch85kyrofa, i'm with you15:58
enoch85kyrofa, just a file called parts?15:59
kyrofaenoch85, no, no files, this is all in the yaml15:59
enoch85kyrofa, sorry, add it to .yaml15:59
kyrofaenoch85, right, you got it15:59
kyrofaenoch85, so every .snap is made up of (potentially many) parts15:59
enoch85kyrofa, cool15:59
enoch85kyrofa, what repos can I use here?16:00
kyrofaenoch85, in snapcraft, each part is assembled by one of its many plugins. Part of the process we're going through may very well end up making a php plugin16:01
kyrofa(since snapcraft doesn't have one)16:01
enoch85kyrofa, ok. is it ok to post here or do you want a pastebin instead?16:02
enoch85kyrofa, maybe PM?16:02
kyrofaenoch85, pastebin is less noisy and easier to read. Perhaps PM would quiet the list down a bit :)16:02
enoch85kyrofa, like that?16:03
enoch85kyrofa, what should be instead of plugin and source i.e?16:03
kyrofaenoch85, let's take this PM16:04
=== chihchun is now known as chihchun_afk
LefterisJPI have a question about this blogpost: https://insights.ubuntu.com/2015/06/03/so-you-want-to-write-a-snappy-app/16:09
LefterisJPHe has a snappy directory with bin/ARCH1 and bin/ARCH2 and has 2 executables under it16:10
LefterisJPhow does snappy build know which one to put in what architecture? Cause I tried to do something similar and it ended up having bin/ARCH1 and bin/ARCH2 under the Raspberry PI where I only wanted to have the corresponding Architecture subtree there.16:11
kyrofadholbach, https://developer.ubuntu.com/en/snappy/build-apps/snapcraft-syntax/ doesn't show sublists16:11
kyrofaLefterisJP, that's the thing-- it puts both16:11
kyrofaLefterisJP, that's why you need that third item-- the shell script that determines which one to run16:12
dholbachkyrofa: ok, looking into it16:12
LefterisJPI could do that, but then how does (in the blogpost) the package.yaml point to the same executable?16:12
kyrofaLefterisJP, the executable is the shell script16:12
kyrofaLefterisJP, which will run on all archs16:12
kyrofaLefterisJP, then launch the corresponding binary16:13
dholbachkyrofa: I filed https://bugs.launchpad.net/developer-ubuntu-com/+bug/1531200 to track it16:13
ubottuLaunchpad bug 1531200 in Ubuntu Developer Portal "Snappy/Snapcraft docs don't show sublists" [Undecided,New]16:13
kyrofadholbach, thank you! Yeah, I'm just pointing people to github for now16:14
dholbachkyrofa: we're getting closer to finally having the markdown importer working and deployed, from there on it should be a lot less tedious and we started adding tests as well16:15
kyrofadholbach, awesome!16:15
LefterisJPkyrofa: I understand what you say, but in the blog post he seems to produce a binary called "port-listener" from go-build and then another one with the same name through go-build cross compiling for ARM. And he only puts them in different bin/ directories under the main snappy/ dir.16:15
LefterisJPkyrofa: And his package.yaml does not seem to contain a shell script16:16
LefterisJPservices:16:16
LefterisJP - name: port-listener16:16
LefterisJP   description: "template Go snappy project"16:16
LefterisJP   start: ./bin/port-listener16:16
LefterisJP   caps:16:16
LefterisJP     - networking16:16
LefterisJP     - network-service16:16
LefterisJPUnless this bin/port-listener is actually a selection shell script16:16
kyrofaLefterisJP, exactly!16:17
kyrofaLefterisJP, your last point is spot on16:17
kyrofaLefterisJP, and it in turn runs the binary that it knows will run on the current arch16:18
LefterisJPkyrofa: I see. Quite strange that he does not mention this in the blog post (https://insights.ubuntu.com/2015/06/03/so-you-want-to-write-a-snappy-app/)16:20
kyrofaLefterisJP, "The run file plays a little trick. It invokes the correct binary file depending on the currently running architecture. This allows you to package one snap that works on my architectures. "16:21
LefterisJPkyrofa: My bad16:24
LefterisJPkyrofa: Missed that line totally16:24
LefterisJPkyrofa: Okay now I found it in the bzr repo too. Got the shell file. This will be really helpful. Thanks.16:25
kyrofaLefterisJP, no problem!16:26
renatHi! It's Renat from Screenly. I wanted to contact @mectors about creating a custom store for screenly snaps. It is set up by store.id setting in YAML file for the  OEM snap. Is there any information about that? Thanks.16:30
renatHi, kyrofa!16:30
kyrofarenat, hey there!16:32
LefterisJPkyrofa: But wouldn't it be smarter if the binaries were only uploaded to the device for which they were made, and having package.yaml determine which binary goes to which architecture? And then snappy-remote or snappy-install can simply deny installation for incompatible architectures. Because as it stands right now we will end up having binaries inside the /apps/bin/ of a snappy app that we would never use. I am wondering how come16:33
LefterisJPthings ended up as they are now16:33
renatkyrofa, can you help me please? I want to contact mectors, but cannot see his nick in users list here. Question about custom store for Screenly becoming more urgent, and I want to resolve it until it's too late.16:34
kyrofasergiusens, do you know anything about renat's question?16:35
kyrofarenat, I'm afraid I've not dealt with that, but I'd be curious about the answer as well. We'll see if we can find someone else to help you :)16:36
kyrofasergiusens, or know who to talk to about it, anyway. I suspect mectors is not actually the right person16:48
sergiusensrenat, do you have his email?16:57
sergiusensrenat, kyrofa I think you want to talk to beuno16:58
renatsergiusens, kyrofa, thanks.17:00
renatsergiusens, how can I contact beuno?17:00
kyrofasergiusens, yeah I wondered. renat have you tried the snappy mailing list?17:00
sergiusensrenat, I just pinged beuno to join, not sure why he isn't here17:01
renatsergiusens, thanks!17:20
sergiusensChipaca, hey, does license agreement require a license version or vice versa?18:41
Chipacasergiusens: no18:43
sergiusensChipaca, either of those require a license though? And if not, it seems sane if I require those keys to have a license defined, right?18:44
Chipacasergiusens: if package version A has require-license-agreement, and B has require-license-agreement, and A is installed, and A and B both have the same license version, then the user isn't asked again18:44
Chipacaon upgrade i mean18:44
Chipacasergiusens: if you require a license agreement, a license file is required and must be nonempty18:46
Chipacasergiusens: i'm not sure i'm answering your question =)18:48
enoch85does anyone know the user and pass to the snappy OVA image?18:49
enoch85found here: https://insights.ubuntu.com/2015/01/15/snappy-ubuntu-core-now-on-the-hypervisor-of-your-choice-with-ova/18:49
ogra_same as everywhere :)18:50
ogra_ubuntu/ubuntu by default18:50
sergiusensChipaca, perfectly; it was obvious, but was making sure :-)18:50
sergiusensChipaca, but you can have a license, require an agreement and not version it, meaning it is a one time thing or until you version it18:51
enoch85ogra_, tried ubuntu ubuntu, but no. :/18:52
Chipacasergiusens: yes. And you can have a license and a version and not require an agreement18:52
ogra_enoch85, then something must be broken ... the rootfs is the same everywhere for snappy18:52
Chipacasergiusens: and you can have a license version and no license and not require an agreement, and that probably doesn't complain even =)18:52
enoch85http://i.imgur.com/UPPwifU.png ogra_18:53
enoch85ogra_, and I get: intel_rapl: no valid rapl domains found in package 018:54
enoch85maybe that's the cause?18:54
ogra_i doubt that18:54
sergiusensChipaca, that last one seems more like a bug though ;-)18:55
sergiusensChipaca, I'm making it complain in snapcraft fwiw18:55
enoch85ogra_, any clue?18:56
ogra_enoch85, not from that screenshot ... perhaps cloud-init went south or something ... check your boot loag (i'm officially not here btw :) )18:57
ogra_*log18:57
enoch85ogra_, ok, thanks :)18:57
=== jdstrand_ is now known as jdstrand
plarselopio: on x86, I'm seeing a message from udf with rolling/edge: "expected 5 partitons but found 0" but it exits 0. I'm assuming this was a silent failure?19:32
plarselopio: and on a different system, I get 'error while executing external command kpartx -ds /tmp/x86.img: device-mapper: remove ioctl on loop1p5 failed: Device or resource busy'19:57

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