Oh, if you dont know how to test on ARM you can make the same snap for amd64 I am sure use a jre accordingly and then use a KVM to test it... once that work, just replace the jre with the armhf one etc. and it will work fine too!
On Fri, May 8, 2015 at 12:34 AM, Alexander Sack <[email protected]> wrote: > On Fri, May 8, 2015 at 12:31 AM, Alexander Sack <[email protected]> wrote: >> On Wed, May 6, 2015 at 11:50 AM, <[email protected]> wrote: >>> Hi >>> our raspi2 image is updated to the last version. >>> I uploaded the snap on dropbox >>> https://www.dropbox.com/s/us29rn028q9neum/freedomotic_5.6.0_armhf.snap?dl=0 >>> >>> Is there anyone who can try it on raspberry2 or another armhf board and >>> give us any feedback? To start it you must lanch ./start under bin folder. >> >> did you try to make a binaries: entry for this in package.yaml so you >> can start it with freedomotic.start using normal confinement? > > I tried running it direcetly and it doesnt work. The right thing to do > is to use use a binaries: entry in package.yaml (check out hello-world > example) and then use $SNAP_APP_PATH to find the top level dir of your > app in that start script. > > If you install hello-world you can see the environment variables you > have available: > > hello-world.env | grep SNAP_ > SNAP_APP_PATH=/apps/hello-world.canonical/1.0.14 > SNAP_ORIGIN=canonical > SNAP_APP_USER_DATA_PATH=/home/ubuntu//apps/hello-world.canonical/1.0.14 > SNAP_FULLNAME=hello-world.canonical > SNAP_NAME=hello-world > SNAP_APP_TMPDIR=/tmp/snaps/hello-world.canonical/1.0.14/tmp > SNAP_OLD_PWD=/home/ubuntu > SNAP_APP_DATA_PATH=/var/lib//apps/hello-world.canonical/1.0.14 > > > and in hello-world/meta/package.yaml you have this: > > name: hello-world > version: 1.0.13 > vendor: Snappy Developers <[email protected]> > icon: meta/hello.svg > binaries: > - name: bin/echo > - name: bin/env > > ... > > this makes commands like hello-world.env that get properly confined > and the right envs set. > > >> >>> >>> Thanks >>> Mauro >>> >>> On Mon, May 4, 2015 1:07 pm, Jamie Strandboge wrote: >>>> On 05/04/2015 09:04 AM, [email protected] wrote: >>>> >>>>> Hi Jamie, >>>>> thanks for your reply. Based on Loic Minier's suggested example >>>>> http://bazaar.launchpad.net/~lool/+junk/webcam-webui-snap/files/head:/me >>>>> ta/ I modified my package. >>>>> Would you like to test it on an ARM board? >>>>> >>>>> >>>>> The compilation process is OK. >>>>> >>>>> >>>> Based on looking at the packaging, it seems fine. The problem is the >>>> target system that you are installing the snap on is not running an up to >>>> date snappy. Please update your raspberry pi2 device to the latest stable >>>> release that came out a week and a half ago (or alternatively, to rolling). >>>> >>>> >>>>> Mauro >>>>> >>>>> >>>>> On Mon, May 4, 2015 8:33 am, Jamie Strandboge wrote: >>>>> >>>>>> On 05/04/2015 08:29 AM, Jamie Strandboge wrote: >>>>>> >>>>>> >>>>>>> On 05/03/2015 04:23 AM, [email protected] wrote: >>>>>>> >>>>>>> >>>>>>>> Hi all >>>>>>>> I created the snap with embedded Oracle jre but it doesn't start >>>>>>>> with the following error (RaspberryPi2)ubuntu@localhost:~$ >>>>>>>> start.sh.freedomotic aa-exec: ERROR: profile >>>>>>>> 'freedomotic_start.sh_5.6.0' does not exist >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I think it's related to AppArmor but I didn't find any doc >>>>>>>> example about this. Can you help me? How to add this file and >>>>>>>> modify the package.yaml? >>>>>>>> >>>>>>>> The snap is structure is online on >>>>>>>> https://github.com/mcicolella/freedomotic-snappy >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> It is related to apparmor-- the profile >>>>>>> 'freedomotic_start.sh_5.6.0' >>>>>>> isn't loaded into the kernel so the aa-exec failed. I looked at your >>>>>>> package.yaml and you are using the defaults (good), and there is >>>>>>> nothing more you need to do for the security policy. What is >>>>>>> probably happening is something during the install is failing prior >>>>>>> to the apparmor policy generation. >>>>>>> >>>>>>> What I find curious though is that you are using the command >>>>>>> 'start.sh.freedomotic'-- this should be freedomotic.start.sh >>>>>>> instead. Also the >>>>>>> reported error message shows snappy is using 'aa-exec' instead of >>>>>>> 'ubuntu-core-launcher'. Also, the package shouldn't have been able >>>>>>> to be in the half-installed state that it is in now (ie, unpacked, >>>>>>> but without generated security policy, etc). All of this indicates >>>>>>> your snappy system is out of date. >>>>>>> >>>>>> Sorry, I sent this a tad too soon... >>>>>> >>>>>> >>>>>> >>>>>> All of this indicates your snappy system is out of date and you >>>>>> should upgrade to the latest stable release that came out a week and a >>>>>> half ago (or >>>>>> alternatively, to rolling). >>>>>> >>>>>> -- >>>>>> Jamie Strandboge http://www.ubuntu.com/ >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> snappy-devel mailing list [email protected] Modify >>>>>> settings or unsubscribe at: >>>>>> https://lists.ubuntu.com/mailman/listinfo/snappy-devel >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Jamie Strandboge http://www.ubuntu.com/ >>>> >>>> >>>> >>> >>> >>> -- >>> snappy-devel mailing list >>> [email protected] >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/snappy-devel -- snappy-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
