snapcraft in docker container fails

2017-03-22 Thread Alistair Grant
Hi All, I've been building snap packages within a docker container successfully. Up to now all the containers have been built with devmode, but I would now like to build one with classic confinement (for a development application). Building the package fails because the core snap isn't installed,

Re: snapcraft in docker container fails

2017-03-22 Thread Alistair Grant
Hi Marco, On 22 March 2017 at 13:01, Marco Ceppi wrote: > Hi Alistair, > > We had a similar issue in our project, we found this: > > docker run -it -v $PWD:/root/snap -w /root/snap -e SNAPCRAFT_SETUP_CORE=1 > snapcraft/xenial-amd64 /bin/bash > > Where, when using that flag, the core snap will alr

Re: Moving from strict to classic confinement

2017-03-27 Thread Alistair Grant
Hi Eloy, Your readme mentions problems with xdg-open. Take a look at: https://github.com/snapcore/snapd-xdg-open which may help. Note that the host has to have snapd-xdg-open installed. Cheers, Alistair On 27 March 2017 at 09:22, Eloy García (PC Actual) wrote: > Hello everybody. > > I curre

classic 32 bit application

2017-03-29 Thread Alistair Grant
Hi All, I'm trying to package a 32 bit software development environment: Pharo Smalltalk (http://pharo.org). I've got it working OK as a devmode package, but as soon as I switch it to classic confinement it fails to run. The error message displayed when attempting to run the executable is "No su

Re: classic 32 bit application

2017-03-30 Thread Alistair Grant
Hi Sergio, Thanks for your reply. On 30 March 2017 at 15:36, Sergio Schvezov wrote: > On Thu, 30 Mar 2017 08:10:26 +0200, Alistair Grant wrote: >> Hi All, >> >> I'm trying to package a 32 bit software development environment: Pharo >> Smalltalk (http://pharo.or

Re: classic 32 bit application

2017-03-30 Thread Alistair Grant
On 30 March 2017 at 23:38, Seth Arnold wrote: > On Thu, Mar 30, 2017 at 08:10:26AM +0200, Alistair Grant wrote: >> I'm trying to package a 32 bit software development environment: Pharo >> Smalltalk (http://pharo.org). >> >> I've got it working OK as a devmod

Re: classic 32 bit application

2017-04-03 Thread Alistair Grant
Hi James, Thanks for your reply. On Fri, Mar 31, 2017 at 03:08:39PM +0800, James Henstridge wrote: > On 31 March 2017 at 05:38, Seth Arnold wrote: > > On Thu, Mar 30, 2017 at 08:10:26AM +0200, Alistair Grant wrote: > >> I'm trying to package a 32 bit software develop

Re: classic 32 bit application

2017-04-04 Thread Alistair Grant
Hi James, Thanks for your follow-up. On Tue, Apr 04, 2017 at 06:10:32PM +0800, James Henstridge wrote: > On 4 April 2017 at 03:25, Alistair Grant wrote: > > Hi James, > > > > On Fri, Mar 31, 2017 at 03:08:39PM +0800, James Henstridge wrote: > >> On 31 March 201

Re: classic 32 bit application

2017-04-04 Thread Alistair Grant
Hi Loic & Sergio, On Tue, Apr 04, 2017 at 06:19:50PM +0200, Lo??c Minier wrote: > Hi! > > ... > > If the runtime > linker can't be found for some reason, create your own wrapper to launch > your executable by calling the runtime linker directly (run > "/lib/ld-linux.so.2" to get help output or s

Manual review request?

2017-04-09 Thread Alistair Grant
Hi All, I registered the name Pharo and uploaded a snap on April 5. Pharo is a general purpose programming environment (Smalltalk), meaning that developers expect to be able to call any executable or load any library on their system, so the snap has classic confinement. I uploaded the snap to th

Re: Manual review request?

2017-04-10 Thread Alistair Grant
Hi Evan, On Mon, Apr 10, 2017 at 09:49:56AM +, Evan Dandrea wrote: > On Mon, 10 Apr 2017 at 06:25 Alistair Grant wrote: > > > Hi All, > > > > I registered the name Pharo and uploaded a snap on April 5. > > > > Pharo is a general purpose programming envir