Re: Is there any way to list all of the configure options for a snap application?

Yeah, I think this is much needed. For example, I really want to know what are the configuration options for the core snap. One use case could be that I want to stop the autopilot upgrade feature.. Thanks & best regards, XiaoGuo On Wed, Feb 8, 2017 at 2:20 PM, Manik Taneja wrote: > > > On Feb 7

Re: Error to call "docker" command in a snap

On Tue, Feb 07, 2017 at 10:11:55PM -0600, Peng Liu wrote: > Sure! I have reported a bug for it. > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662754 Hi Peng, could you try the kernel in http://people.canonical.com/~jj/linux+jj/ and report back? Thanks signature.asc Description: PGP si

Re: Is there any way to list all of the configure options for a snap application?

> On Feb 7, 2017, at 10:14 PM, XiaoGuo Liu wrote: > > Hi, > > According to the article at > https://github.com/snapcore/snapd/blob/master/tests/lib/snaps/snapctl-hooks/meta/hooks/configure, > we can configure a snap using "snap get/set" command. Is there any way to > list all of the config

Is there any way to list all of the configure options for a snap application?

Hi, According to the article at https://github.com/snapcore/snapd/blob/master/tests/lib/snaps/snapctl-hooks/meta/hooks/configure, we can configure a snap using "snap get/set" command. Is there any way to list all of the configuration options for a snap app so that an end user can fine-tune the ap

Re: Is there any way to disable snap-confine of the all-snap image?

Is it possible to enable "classic" confinement policy for all-snap (Ubuntu core system) image? Thanks. Peng On Tue, Feb 7, 2017 at 10:22 PM, Peng Liu wrote: > Hi Folks, > > A Linux kernel issue related to snap-confine (kernel panic!) haunts me > quite a while. Is there any way to disable it for

Is there any way to disable snap-confine of the all-snap image?

Hi Folks, A Linux kernel issue related to snap-confine (kernel panic!) haunts me quite a while. Is there any way to disable it for now? Thanks. Peng -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Error to call "docker" command in a snap

Sure! I have reported a bug for it. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662754 Thanks Peng On Tue, Feb 7, 2017 at 10:01 PM, Seth Arnold wrote: > On Tue, Feb 07, 2017 at 09:56:04PM -0600, Peng Liu wrote: > > Yes, thanks for your reminder. I found a kernel panic! The logs are >

Re: Error to call "docker" command in a snap

On Tue, Feb 07, 2017 at 09:56:04PM -0600, Peng Liu wrote: > Yes, thanks for your reminder. I found a kernel panic! The logs are below: Thanks Peng; could you please file a bug with "ubuntu-bug linux"? (At least I think that should work.) If that doesn't work, please include at least uname -a outpu

Re: Error to call "docker" command in a snap

Hi Seth, Yes, thanks for your reminder. I found a kernel panic! The logs are below: [ 3629.66] audit: type=1400 audit(1486525969.972:2717): apparmor="ALLOWED" operation="create" profile="snap.paradrop-daemon.paradrop//null-/usr/bin

Re: Error to call "docker" command in a snap

On Tue, Feb 07, 2017 at 09:43:38PM -0600, Peng Liu wrote: > I built a snap which needs to call "docker" command instead of using > bindings like docker-py to get logs from a container. Unfortunately, the > command reported an error with messages "support process for mount > namespace capture exited

Error to call "docker" command in a snap

Hi Folks, I built a snap which needs to call "docker" command instead of using bindings like docker-py to get logs from a container. Unfortunately, the command reported an error with messages "support process for mount namespace capture exited abnormally". >From the snap, I can use docker-py to d

Re: Where to save stuff (in snap-agnostic way)

Hi Jamie, Thanks for your explanation. You are right. The directory name takes the very first execution of the command. After that, when accessing the /tmp directory, it uses the directory created earlier if it is running from another command. I have updated my example code at https://github.com/

Re: snapd available in Trusty Tahr

On 07/02/17 21:31, Manik Taneja wrote: > > > On Tue, Feb 7, 2017 at 12:36 PM, Mark Shuttleworth > wrote: > > On 07/02/17 20:17, Thomas Voß wrote: > > > > https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724 > >

Re: snapd available in Trusty Tahr

On Tue, Feb 7, 2017 at 12:36 PM, Mark Shuttleworth wrote: > On 07/02/17 20:17, Thomas Voß wrote: > > https://bugs.launchpad.net/ubuntu/+source/xorg-server- > lts-xenial/+bug/1655724 > > was released to the updates pocket today. > > Congrats! Quick feedback from folks with Trusty (14.04 LTS) syste

Re: snapd available in Trusty Tahr

On 07/02/17 20:17, Thomas Voß wrote: > https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724 > was released to the updates pocket today. Congrats! Quick feedback from folks with Trusty (14.04 LTS) systems, cloud or desktop, would be welcome. Pick a favorite snap and take it

Re: snapd available in Trusty Tahr

https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724 was released to the updates pocket today. Cheers, Thomas On Thu, Feb 2, 2017 at 8:38 AM, Thomas Voß wrote: > On Thu, Feb 02, 2017 at 12:51:59AM +0100, Joseph Rushton Wakeling wrote: >> On 31/01/17 14:01, Jamie Benne

Re: Spread Tests with proxy (mostly go get)

Hi Max, The problem isn't spread itself, as it won't try to communicate out of the host by itself. The problem is that snapd's test suite expects to be able to talk to the network. Someone would have to go through and fix all such cases to go through the proxy, which is perhaps more troubling tha

Re: Building for different architectures

Hi Kyle, On 7 February 2017 at 16:28, Kyle Fazzari wrote: > It doesn't, I'm afraid. That fix (and another coming soon[1]) are > specific to stage-packages, whereas it sounds like popey is using > `source` directly. I don't think there's a way to do this today, but we > were discussing implementin

Re: Building for different architectures

On Tue, Feb 7, 2017 at 1:20 PM, Oliver Grawert wrote: > hi, > On Di, 2017-02-07 at 16:07 +, Alan Pope wrote: > > Hi, > > > > Suppose I have a snap which requires a couple of non-archive debs as > > stage packages. Typically I'd have a part for each which uses the > > source: of a url directly

Re: Building for different architectures

On Tue, Feb 7, 2017 at 1:07 PM, Alan Pope wrote: > Hi, > > Suppose I have a snap which requires a couple of non-archive debs as > stage packages. Typically I'd have a part for each which uses the > source: of a url directly to the deb using the dump plugin. This works > fine building on my amd64

Re: Building for different architectures

On 02/07/2017 08:20 AM, Oliver Grawert wrote: > hi, > On Di, 2017-02-07 at 16:07 +, Alan Pope wrote: >> Hi, >> >> Suppose I have a snap which requires a couple of non-archive debs as >> stage packages. Typically I'd have a part for each which uses the >> source: of a url directly to the deb u

Re: Where to save stuff (in snap-agnostic way)

On Tue, 2017-02-07 at 12:04 +0800, XiaoGuo Liu wrote: > Hi Jamie, > > For my sample app at https://github.com/liu-xiao-guo/helloworld-fifo, I > tried to use the /tmp file to create a file, and  finally I get a file on > my Desktop like: > > root@liuxg:/tmp/snap.1000_snap.hello.fifo_TovLTW/tmp# ls

Re: Building for different architectures

hi, On Di, 2017-02-07 at 16:07 +, Alan Pope wrote: > Hi, > > Suppose I have a snap which requires a couple of non-archive debs as > stage packages. Typically I'd have a part for each which uses the > source: of a url directly to the deb using the dump plugin. This > works > fine building on my

Building for different architectures

Hi, Suppose I have a snap which requires a couple of non-archive debs as stage packages. Typically I'd have a part for each which uses the source: of a url directly to the deb using the dump plugin. This works fine building on my amd64 laptop (or wherever) and I end up with an amd64 snap. However

Re: Which interface exposes user folder to root

On Tue, 2017-02-07 at 12:27 +0800, Tonny Tzeng wrote: > Hi Jamie, > > Thanks for the detailed explanation, it's really helpful! > > However, I am hesitated to package my example files in the snap, just > curious, what's the proper way to package a "development snap" which reads > user given files

Re: snapcraft 2.26 has been released

On Tue, Feb 7, 2017 at 8:52 AM, Ted Gould wrote: > On Fri, 2017-02-03 at 08:57 -0300, Sergio Schvezov wrote: > > We are pleased to announce the release of version `2.26` of snapcraft has > been released: > https://launchpad.net/snapcraft/+milestone/2.26 > > > Lots of cool stuff landing in Snapcraf

Re: connecting a non-auto interface, automatically

On 07/02/17 14:43, Simon Fels wrote: > On 07.02.2017 15:36, knitzsche wrote: >> What is the approach to connect interfaces that are not auto-connecting >> without user intervention? >> >> That is, there's a snap (built into an image) that declares the >> log-observe plug. Log-observe interface does

Re: ubuntu-app-platform updated to Qt 5.6.2

Hey Timo and al, I thought I fixed the terminal last week. At least the terminal available on the edge channel now is working for me. Does it work for you? I made sure that the stage-packages only contain packages that are not in ubuntu-app-platform and also used build-attributes: [no-system-libr

Re: snapcraft 2.26 has been released

On Fri, 2017-02-03 at 08:57 -0300, Sergio Schvezov wrote: > We are pleased to announce the release of version `2.26` of snapcraft > has been released: > https://launchpad.net/snapcraft/+milestone/2.26 Lots of cool stuff landing in Snapcraft. Can we get a "snapcraft- version" key in the snapcraft.ya

Re: connecting a non-auto interface, automatically

On 07.02.2017 15:36, knitzsche wrote: > What is the approach to connect interfaces that are not auto-connecting > without user intervention? > > That is, there's a snap (built into an image) that declares the > log-observe plug. Log-observe interface does not auto-connect [1]. In > this product, t

[System Enablement] New releases Feb 2017

Hey everyone, new releases of the alsa-utils, network-manager, upower and wifi-ap snaps were pushed into the candidate channel. alsa-utils 1.1.2-2: * First official release supported by Canonical * Aliases for all exported commands are available * Set of automated and manual test cases guarantee

connecting a non-auto interface, automatically

What is the approach to connect interfaces that are not auto-connecting without user intervention? That is, there's a snap (built into an image) that declares the log-observe plug. Log-observe interface does not auto-connect [1]. In this product, the user does not have a console, so they canno

Re: Snap security questions

On Wed, 2017-02-01 at 08:46 -0600, Jamie Strandboge wrote: > On Wed, 2017-02-01 at 20:33 +0800, James Henstridge wrote: > > > > Hi, > > > > On our team we've been working to snap the thumbnailer project.  While > > there are some problems that are probably specific to this package, > > there were

Re: HowTo: How to create a snap for a Python app with networking using snapcraft in Ubuntu 16.04

Le 07/02/2017 à 14:05, Simos Xenitellis a écrit : > On Tue, Feb 7, 2017 at 9:13 AM, Didier Roche wrote: >> Le 06/02/2017 à 10:56, Simos Xenitellis a écrit : >>> Hi All, >>> >>> I wrote an article about creating a snap for an existing Python >>> program using the new snapcraft 2.26. Then, I uploade

How to create a snap with snapcraft for howdoi (CLI utilility for stackoverflow)

Hi All! This is another tutorial for snapcraft. It reinforces the content of the previous how2 tutorial since they are both for similar tools, that require only the "network" plug. No GUI complexities yet. It's quite simple and helps to deal now with package management details on the Ubuntu Store.

Re: HowTo: How to create a snap for a Python app with networking using snapcraft in Ubuntu 16.04

On Tue, Feb 7, 2017 at 9:13 AM, Didier Roche wrote: > Le 06/02/2017 à 10:56, Simos Xenitellis a écrit : >> Hi All, >> >> I wrote an article about creating a snap for an existing Python >> program using the new snapcraft 2.26. Then, I uploaded to the Ubuntu >> Store. >> >> I am looking forward to r

[Dragonboard410c] Ubuntu OS Build Issues, and Support

Hi, We are using Dragonboard410C to build kernel snap, gadget snap and Ubuntu OS Image. We got the linux kernel (Debian release 16.09) from: https://builds.96boards.org/releases/dragonboard410c/linaro/debian/16.09/ Kernel snapcraft.yaml is at: http://pastebin.com/DcPe1TT2 and the gadget from: h

Custom Kernel and Gadged Snap Issue for Eragon410 board based on Dragonboard410c and other build related issues

Hi Oliver, Please find our answers inl

Re: ubuntu-app-platform updated to Qt 5.6.2

On Wed, Feb 1, 2017 at 8:52 AM, Timo Jyrinki wrote: >>> Isn't this what Kyle fixed by adding build-attributes: >>> [no-system-libraries] ? >>> >>> http://snapcraft.io/docs/build-snaps/syntax#parts >> >> Yes, that seems to be it, indeed. Thanks for the pointer Leo, I wasn’t >> aware of this new fe

Re: license.txt and snap/ directory

On Tue, 7 Feb 2017 01:46:04 +0100, Joseph Rushton Wakeling wrote: > On 07/02/17 00:24, Kyle Fazzari wrote: >> The fact that an empty directory is created here is a bug[1]. It should >> only create that directory if there's something to put in there. What >> Sergio is saying is this: >> >> Snapcraft

Re: the ppp interface (and general renaming/transitioning of interfaces)

hi, Am Montag, den 06.02.2017, 20:14 + schrieb Jamie Bennett: > On 06/02/17 at 04:06P, Oliver Grawert wrote: > > > > hi, > > Am Montag, den 06.02.2017, 15:50 +0100 schrieb Simon Fels: > > > > > >   > > > I've just checked this and all pppd things are still in core. See > > > https://paste.ubu

How to create a snap for how2 (stackoverflow from the terminal) in Ubuntu 16.04

Hi All, This is a complete tutorial on snapping "how2", a nodejs command-line tool that searches for you on StackOverflow, and just outputs what was selected as the correct answer. Being a nodejs program, it is messy to install with all the dependencies. So it was a very good candidate for snappi