Re: snap integration with XFCE

2016-10-24 Thread Didier Roche
Le 06/10/2016 à 21:34, Eloy García (PC Actual) a écrit : > Hi all. > > I develop a java-based application to download and manage wallpapers > from the Internet (wallpaperdownloader) > (https://bitbucket.org/eloy_garcia_pca/wallpaperdownloader/overview). > The applications is in the store but now I'

Re: snap integration with XFCE

2016-10-24 Thread PC Actual
Hi Didier! Thanks as always for your answer and feedback :) I suspected it and I was taking a look to desktop launcher source code on github, but I didn't have time to test it. One question: Can I create the symblink when the snap application is executed (after installation) via the script that i

Re: snap integration with XFCE

2016-10-24 Thread Didier Roche
Le 24/10/2016 à 10:58, Eloy García (PC Actual) a écrit : > Hi Didier! > > Thanks as always for your answer and feedback :) I suspected it and I > was taking a look to desktop launcher source code on github, but I > didn't have time to test it. One question: Can I create the symblink > when the sna

[snaps/deb] Cross dependencies / forward compatibility between debs & snaps?

2016-10-24 Thread Samuel Cozannet
Hello, This may seem a very stupid question (apologies for this) but it just popped to me as I was working on a .deb. Background: I am currently working with IBM on some GPU docker based images, so I have to use docker on ppc64le. I came across nvidia-docker, which is the tool distributed by nVi

Problems trying to create a snap package for bioinformatics tools

2016-10-24 Thread Gordon Ball
Hello I have been trying to create a snap package for the `cufflinks` [1] biofinformatics tools. These are packaged for debian/ubuntu, but the package is not built for xenial due to issues with boost 1.56-1.59. [2] I tried building a snap package (see snapcraft.yaml below - just a simple `stage-p

Re: Problems trying to create a snap package for bioinformatics tools

2016-10-24 Thread Didier Roche
Le 24/10/2016 à 16:13, Gordon Ball a écrit : > Hello Hey Gordon, > I have been trying to create a snap package for the `cufflinks` [1] > biofinformatics tools. These are packaged for debian/ubuntu, but the > package is not built for xenial due to issues with boost 1.56-1.59. [2] Nice way to shi

"path must be relative" in filesets is holdover convention from debian packaging, causes grief

2016-10-24 Thread Dan Kegel
Hi! When generating snapcraft.yaml from e.g. CMakeLists.txt for a large project, I wanted to exclude some dev files which live at a configuration-dependent location, e.g. filesets: dev: - -@FOO@/include - -@FOO@/lib/*.a - -usr/share/doc Can you spot the usabilit

Configuring apparmor / seccomp for a snap to allow sendmsg and mkfifo?

2016-10-24 Thread Dan Kegel
I'm trying to snap a largish package; works fine in devmode, but as the app likes to use unix sockets and fifos, it fails in confined mode with $ sudo /snap/bin/snappy-debug.security scanlog = AppArmor = Time: Oct 24 11:41:09 Log: apparmor="DENIED" operation="sendmsg" profile="snap.foo" pid=8536 c

Connecting to Ubuntu SnapWeb; https://localhost:4201 shows Your connection is not secure

2016-10-24 Thread Chris
This is the first time I've noticed this happening and I keep SnapWeb loaded in my browser. The owner of localhost has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website. localhost:4201 uses an invalid security certificate

Re: Connecting to Ubuntu SnapWeb; https://localhost:4201 shows Your connection is not secure

2016-10-24 Thread Chris
On Tue, 2016-10-25 at 04:00 +0200, Jo-Erlend Schinstad wrote: > What if you connect to https://127.0.0.1:4201? > https://127.0.0.1:4201/ shows the same error > > On 25 October 2016 at 02:26, Chris wrote: > > This is the first time I've noticed this happening and I keep > > SnapWeb > > loaded in

Re: "path must be relative" in filesets is holdover convention from debian packaging, causes grief

2016-10-24 Thread Didier Roche
Le 24/10/2016 à 17:49, Dan Kegel a écrit : > Hi! > > When generating snapcraft.yaml from e.g. CMakeLists.txt for a large project, > I wanted to exclude some dev files which live at a > configuration-dependent location, e.g. > > filesets: > dev: > - -@FOO@/include > - -@FOO

Re: Configuring apparmor / seccomp for a snap to allow sendmsg and mkfifo?

2016-10-24 Thread Didier Roche
Le 24/10/2016 à 21:52, Dan Kegel a écrit : > I'm trying to snap a largish package; works fine in devmode, > but as the app likes to use unix sockets and fifos, it fails in > confined mode with > > $ sudo /snap/bin/snappy-debug.security scanlog > = AppArmor = > Time: Oct 24 11:41:09 > Log: apparmor=

Re: "path must be relative" in filesets is holdover convention from debian packaging, causes grief

2016-10-24 Thread Dan Kegel
On Mon, Oct 24, 2016 at 11:21 PM, Didier Roche wrote: > You have the parts//install directory, which is your target > for your parts installation. All files are there (and DESTDIR is set to > there). It sounds then normal to not rely on absolute path, but only > relative one to reference those, an

Re: "path must be relative" in filesets is holdover convention from debian packaging, causes grief

2016-10-24 Thread Didier Roche
Le 25/10/2016 à 08:46, Dan Kegel a écrit : > On Mon, Oct 24, 2016 at 11:21 PM, Didier Roche wrote: >> You have the parts//install directory, which is your target >> for your parts installation. All files are there (and DESTDIR is set to >> there). It sounds then normal to not rely on absolute path