Re: SystemD Unit file customization for a snap

2017-01-11 Thread Stuart Bishop
On 12 January 2017 at 11:33, Stuart Bishop 
wrote:

>
> On 12 January 2017 at 02:31, Charles Butler 
> wrote:
> You don't have much control over the generated systemd service file. Its
> an open issue. So while you could have your snap accept configuration
> options, the snap can't rewrite its own systemd service file (or it could
> escape its containment). What you would need to do is write a wrapper for
> bin/etcd that sets the environment variables (pulled from snap
> configuration, or from a .ini file or similar stored in $SNAP_DATA or
> $SNAP_COMMON) before os.exec'ing the real bin/etcd
>

(and if you choose this approach, you of course need your charm to restart
the service when you change the config. snapd can't do that for you, yet.
Well, maybe the config handler is able to restart the service but I suspect
confinement would block that attempt)


Since you are driving this from a charm though, you don't need it. systemd
> supports '.d' style directories, allowing you to extend a .service file
> owned by some other process. This is how the snap layer adds support for
> downloading snaps via proxies, so see https://git.launchpad.net/
> layer-snap/tree/reactive/snap.py#n62 for an example.
>
>
-- 
Stuart Bishop 
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Bad system call - 45 for my binary app

2017-01-11 Thread Jamie Strandboge
On Wed, 2017-01-11 at 11:34 +0200, Andrey Rogovsky wrote:
> Hi, all!
> 
> I crafted snap for i386 X11 app (no sources) which work success on amd64
> arch in development mode.
> But when I install it in strict mode - got this error:
> 
> = Seccomp =
> Time: Jan 11 11:26:38
> Log: auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=17988
> comm="BlueQuest" exe="/snap/bluequest/x1/usr/bin/BlueQuest" sig=31
> arch=4003 45(brk) compat=1 ip=0xf7749547 code=0x0
> Syscall: brk
> 
> How I can resolve this problem?
> 

This sounds like bug #1592022 which should be fixed in snapd and snap-confine
2.20. What versions of there packages do you have installed?

[1]https://bugs.launchpad.net/snap-confine/+bug/1592022

-- 
Jamie Strandboge | http://www.canonical.com



signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Serial Port Plug/Interface issue with Ubuntu-core 16.04 (#2557)

2017-01-11 Thread Mritunjai Singh
Hi All,

Kindly refer to: https://github.com/snapcore/snapd/issues/2557

We are trying to get a head start on Core Snappy working with our RF Mesh 
network card. It connects over serial and needs to be available at boot. We 
first tried this using snap approach but due to missing hotplugging 
serial-interface in current(latest) version of snapcraft, serial i/o requests 
are being denied even if the snap has the permission to use serial port.

We have been suggested the gadget snap approach in order to expose /dev/ttyS0 
to the serial port interface for tunnccd snap to access it. It would be very 
helpful if someone can point me to the working example of a gadget snap with 
access to serial interface or any end to end gadget snap example and its build 
steps.

Regards,
Mritunjai


-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Kernel plugin: Avoid redownloading os.snap on a local Git repo

2017-01-11 Thread Kyle Fazzari
This doesn't really involve cleaning, in fact it's not ideal that
anything needs to be cleaned at all in this case-- snapcraft needs to
pick up local changes automatically. That work in ongoing.

On 01/09/2017 05:35 PM, Gustavo Niemeyer wrote:
> 
> This is one area that is still super confusing, and would be worth
> investing some time on soon.
> 
> We discussed this back in May on:
> 
> - clean behavior is confusing
>   https://bugs.launchpad.net/snapcraft/+bug/1582469
> 
> As described there, this is a rock on the most important pipeline of the
> tool.
> 
> 
> On Mon, Jan 9, 2017 at 11:31 PM, Kyle Fazzari
> > wrote:
> 
> On 01/09/2017 12:08 PM, Michał Sawicz wrote:
> > W dniu 09.01.2017 o 20:32, Michał Sawicz pisze:
> >> I *think* (may be wrong) that `snapcraft pull` can help here:
> >>
> >> http://snapcraft.io/docs/reference/snapcraft-command#pull
> 
> >
> > I was able to force `snapcraft pull` to pull things again by messing
> > with parts/part-name/state - might wanna try that in case there's no
> > better answers.
> 
> Careful with this, snapcraft tends to get upset if you mess with its
> state behind its back.
> 
> Lifecycle steps build upon each other: pull -> build -> stage -> prime.
> Let's say you ran `snapcraft build A`, which will pull part A (let's say
> it was commit abdc1), and then build it. If commit abcd2 is later made
> and you want to build it, you need to clean the pull step (which will
> also clean the build step) with `snapcraft clean A`, and build again:
> `snapcraft build A`. That will pull any updates that have been made, and
> build anew.
> 
> --
> Kyle Fazzari (kyrofa)
> Software Engineer
> Canonical Ltd.
> k...@canonical.com 
> 
> 
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io 
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
> 
> 
> 
> 
> 
> -- 
> 
> gustavo @ http://niemeyer.net
> 
> 

-- 
Kyle Fazzari (kyrofa)
Software Engineer
Canonical Ltd.
k...@canonical.com



signature.asc
Description: OpenPGP digital signature
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Slow snap build on Ubuntu Core device

2017-01-11 Thread Jim Hodapp
That works well ogra, started using this on my laptop.

On Tue, Jan 10, 2017 at 10:55 AM, Oliver Grawert  wrote:

> hi,
> Am Dienstag, den 10.01.2017, 15:40 + schrieb Alan Pope:
> >
> > >
> > For archive packages being slow (as you have) I use apt-cacher-ng on
> > my laptop. It caches the debs making snapcraft builds much faster.
>
> shamelessly promoting my onw snap here:
>
> sudo snap install packageproxy ...
>
> point your sources.list entries to http://localhost:/ubuntu-ports a
> nd be happy ;)
>
> ciao
> oli
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Manual update of snap/snapd and core/ubuntu-core

2017-01-11 Thread Chris Wayne
Hi Jenny,

>From the looks of it, your system has actually been updated automatically,
as your first email indicates you had core version 641, and now have core
714.  The reason you could not update to core on the edge channel to
version 870 is because that version has not been validated yet.

Does snap --version still show 2.18?  With core rev 714 (which your snap
list indicates you have installed) you should now be seeing 2.20.

Thanks
Chris

On Wed, Jan 11, 2017 at 7:05 AM, Jenny Murphy 
wrote:

> Oh ok, so when they do, the updates will start happening automatically?
> Thanks.
>
> On 11 January 2017 at 11:54, Jamie Bennett 
> wrote:
>
>> Hi Jenny,
>>
>> The lack of update is due to the platform you are using: St Louis. It
>> looks like the team responsible for St Louis updates has not fully
>> validated the new Ubuntu Core software which is why you haven't seen an
>> update yet. I suspect that an update is forthcoming soon.
>>
>> Regards,
>> Jamie.
>>
>> On 11 Jan 2017, at 13:38, Jenny Murphy 
>> wrote:
>>
>> Hi,
>>  This is the error I get after step 1:
>>
>>
>> admin@localhost:~$ snap refresh core --edge
>> error: cannot refresh "core": cannot refresh "core" to revision 870: no
>> validation by "stlouis"
>>
>> On 11 January 2017 at 10:21, Manik Taneja  wrote:
>>
>>> Hi Jenny,
>>>
>>> Welcome to Ubuntu Core. I see that you are experiencing a timeout while
>>> retrieving assertions. We have added additional redundancy to the client in
>>> a later revision (2.20) of snapd. While we await for 2.20 to move into the
>>> stable channel, can I request that you manually upgrade to the edge channel
>>> using-
>>>
>>> snap refresh core --edge
>>> snap --version
>>> snap list
>>>
>>> Once the refresh succedes, than please try the snap refresh command to
>>> make sure that all snaps are updated to the latest. If you still experience
>>> similar issues, please let us know. For reference, here's a screenshot of
>>> the cmd usage-
>>>
>>> 
>>>
>>> Regards,
>>> Manik
>>>
>>> On Wed, Jan 11, 2017 at 11:39 AM, Jenny Murphy <
>>> jenny.mur...@episensor.com> wrote:
>>>
 Hi Jamie,
 Here is some more information as requested :

 admin@localhost:~$ snap info core
 name:  core
 summary:   "snapd runtime environment"
 publisher: canonical
 description: |
   The core runtime environment for snapd
 type:core
 tracking:stable
 installed:   16.04.1 (714) 79MB -
 refreshed:   2016-12-16 04:28:38 + UTC
 channels:
   stable:16.04.1 (714) 0B -
   candidate: 16.04.1 (714) 0B -
   beta:  16.04.1 (714) 0B -
   edge:  16.04.1 (870) 0B -

 admin@localhost:~$ snap refresh
 error: cannot refresh []: cannot refresh snap-declaration for
 "stlouis-kernel": Get https://assertions.ubuntu.com/
 v1/assertions/snap-declaration/16/0EawO5JYYJmNw9CmweMnyrwGgJ
 xDUHag?max-format=1: net/http: request canceled while waiting for
 connection (Client.Timeout exceeded while awaiting headers)

 admin@localhost:~$ snap list
 Name VersionRev  Developer  Notes
 bluez5.37-2 15   canonical  -
 core 16.04.1714  canonical  -
 gateway  2.0x3  devmode
 modem-manager1.4.0-114   canonical  -
 network-manager  1.2.2-10   73   canonical  -
 snappy-debug 0.26   25   canonical  -
 snapweb  0.21.2 24   canonical  -
 stlouis  16.04-1.13 11   canonical  -
 stlouis-kernel   4.4.0-57-1 7canonical  -
 tpm2 1.0-2.112   canonical  -
 uefi-fw-tools1.2-0.7.2+git  2canonical  -


 snapcraft@lists.snapcraft.io
 On 11 January 2017 at 07:16, Jamie Bennett  wrote:

> Hi Jenny,
>
> On 09/01/17 at 10:28am, Jenny Murphy wrote:
> > Hi,
> >  My query is related to a few of the recent discussions regarding
> versions,
> > releases and updates/
> >
> > I currently have a Snappy Ubuntu system as follows :
> >
> > snap --version gives the following result :
> >  snap2.18.1
> >  snapd   2.18.1
> >  series  16
> >
> > more /etc/lsb-release yeilds :
> > DISTRIB_ID="Ubuntu Core"
> > DISTRIB_RELEASE=16
> > DISTRIB_DESCRIPTION="Ubuntu Core 16
> >
> > And finally snap list yields :
> > core 16.04.1641  canonical  --
> >
> > I don't see to be  getting any automatic updates which I don't mind
> about
> > as long as I could manually update.
> >
> > So just a few questions :
> >
> > 1. How can I update snap and snapd
>
> What happens when you type:
>
> $ snap info core
>
> Also, what happens when you type:
>
> $ 

Re: Manual update of snap/snapd and core/ubuntu-core

2017-01-11 Thread Jenny Murphy
Oh ok, so when they do, the updates will start happening automatically?
Thanks.

On 11 January 2017 at 11:54, Jamie Bennett 
wrote:

> Hi Jenny,
>
> The lack of update is due to the platform you are using: St Louis. It
> looks like the team responsible for St Louis updates has not fully
> validated the new Ubuntu Core software which is why you haven't seen an
> update yet. I suspect that an update is forthcoming soon.
>
> Regards,
> Jamie.
>
> On 11 Jan 2017, at 13:38, Jenny Murphy  wrote:
>
> Hi,
>  This is the error I get after step 1:
>
>
> admin@localhost:~$ snap refresh core --edge
> error: cannot refresh "core": cannot refresh "core" to revision 870: no
> validation by "stlouis"
>
> On 11 January 2017 at 10:21, Manik Taneja  wrote:
>
>> Hi Jenny,
>>
>> Welcome to Ubuntu Core. I see that you are experiencing a timeout while
>> retrieving assertions. We have added additional redundancy to the client in
>> a later revision (2.20) of snapd. While we await for 2.20 to move into the
>> stable channel, can I request that you manually upgrade to the edge channel
>> using-
>>
>> snap refresh core --edge
>> snap --version
>> snap list
>>
>> Once the refresh succedes, than please try the snap refresh command to
>> make sure that all snaps are updated to the latest. If you still experience
>> similar issues, please let us know. For reference, here's a screenshot of
>> the cmd usage-
>>
>> 
>>
>> Regards,
>> Manik
>>
>> On Wed, Jan 11, 2017 at 11:39 AM, Jenny Murphy <
>> jenny.mur...@episensor.com> wrote:
>>
>>> Hi Jamie,
>>> Here is some more information as requested :
>>>
>>> admin@localhost:~$ snap info core
>>> name:  core
>>> summary:   "snapd runtime environment"
>>> publisher: canonical
>>> description: |
>>>   The core runtime environment for snapd
>>> type:core
>>> tracking:stable
>>> installed:   16.04.1 (714) 79MB -
>>> refreshed:   2016-12-16 04:28:38 + UTC
>>> channels:
>>>   stable:16.04.1 (714) 0B -
>>>   candidate: 16.04.1 (714) 0B -
>>>   beta:  16.04.1 (714) 0B -
>>>   edge:  16.04.1 (870) 0B -
>>>
>>> admin@localhost:~$ snap refresh
>>> error: cannot refresh []: cannot refresh snap-declaration for
>>> "stlouis-kernel": Get https://assertions.ubuntu.com/
>>> v1/assertions/snap-declaration/16/0EawO5JYYJmNw9CmweMnyrwGgJ
>>> xDUHag?max-format=1: net/http: request canceled while waiting for
>>> connection (Client.Timeout exceeded while awaiting headers)
>>>
>>> admin@localhost:~$ snap list
>>> Name VersionRev  Developer  Notes
>>> bluez5.37-2 15   canonical  -
>>> core 16.04.1714  canonical  -
>>> gateway  2.0x3  devmode
>>> modem-manager1.4.0-114   canonical  -
>>> network-manager  1.2.2-10   73   canonical  -
>>> snappy-debug 0.26   25   canonical  -
>>> snapweb  0.21.2 24   canonical  -
>>> stlouis  16.04-1.13 11   canonical  -
>>> stlouis-kernel   4.4.0-57-1 7canonical  -
>>> tpm2 1.0-2.112   canonical  -
>>> uefi-fw-tools1.2-0.7.2+git  2canonical  -
>>>
>>>
>>> snapcraft@lists.snapcraft.io
>>> On 11 January 2017 at 07:16, Jamie Bennett 
>>> wrote:
>>>
 Hi Jenny,

 On 09/01/17 at 10:28am, Jenny Murphy wrote:
 > Hi,
 >  My query is related to a few of the recent discussions regarding
 versions,
 > releases and updates/
 >
 > I currently have a Snappy Ubuntu system as follows :
 >
 > snap --version gives the following result :
 >  snap2.18.1
 >  snapd   2.18.1
 >  series  16
 >
 > more /etc/lsb-release yeilds :
 > DISTRIB_ID="Ubuntu Core"
 > DISTRIB_RELEASE=16
 > DISTRIB_DESCRIPTION="Ubuntu Core 16
 >
 > And finally snap list yields :
 > core 16.04.1641  canonical  --
 >
 > I don't see to be  getting any automatic updates which I don't mind
 about
 > as long as I could manually update.
 >
 > So just a few questions :
 >
 > 1. How can I update snap and snapd

 What happens when you type:

 $ snap info core

 Also, what happens when you type:

 $ snap refresh

 > 2. Is snap the front end to snapd ? Do they get updated together?

 Yes.

 > 3. Can I update snapd and not update ubuntu-core and core.

 On an Ubuntu Core system snapd is integral to the device, on a classic
 system
 snapd is an add-on package so in the former case the system and snapd
 are
 updated together.

 > 4. Should ubuntu-core and core be updated together also? From the
 previous
 > reply on this topic, it seems core is the framework and ubuntu-core
 is the
 > filesystem or is it vice versa?

 ubuntu-core is the old name for core. We renamed this to better 

Re: Manual update of snap/snapd and core/ubuntu-core

2017-01-11 Thread Jamie Bennett
Hi Jenny,

The lack of update is due to the platform you are using: St Louis. It looks 
like the team responsible for St Louis updates has not fully validated the new 
Ubuntu Core software which is why you haven't seen an update yet. I suspect 
that an update is forthcoming soon.

Regards,
Jamie.

> On 11 Jan 2017, at 13:38, Jenny Murphy  wrote:
> 
> Hi,
>  This is the error I get after step 1:
> 
> 
> admin@localhost:~$ snap refresh core --edge
> error: cannot refresh "core": cannot refresh "core" to revision 870: no 
> validation by "stlouis"
> 
>> On 11 January 2017 at 10:21, Manik Taneja  wrote:
>> Hi Jenny,
>> 
>> Welcome to Ubuntu Core. I see that you are experiencing a timeout while 
>> retrieving assertions. We have added additional redundancy to the client in 
>> a later revision (2.20) of snapd. While we await for 2.20 to move into the 
>> stable channel, can I request that you manually upgrade to the edge channel 
>> using-
>> 
>> snap refresh core --edge
>> snap --version
>> snap list
>> 
>> Once the refresh succedes, than please try the snap refresh command to make 
>> sure that all snaps are updated to the latest. If you still experience 
>> similar issues, please let us know. For reference, here's a screenshot of 
>> the cmd usage-
>> 
>> 
>> 
>> Regards,
>> Manik 
>> 
>>> On Wed, Jan 11, 2017 at 11:39 AM, Jenny Murphy  
>>> wrote:
>>> Hi Jamie,
>>> Here is some more information as requested : 
>>> 
>>> admin@localhost:~$ snap info core
>>> name:  core
>>> summary:   "snapd runtime environment"
>>> publisher: canonical
>>> description: |
>>>   The core runtime environment for snapd
>>> type:core
>>> tracking:stable
>>> installed:   16.04.1 (714) 79MB -
>>> refreshed:   2016-12-16 04:28:38 + UTC
>>> channels:  
>>>   stable:16.04.1 (714) 0B -
>>>   candidate: 16.04.1 (714) 0B -
>>>   beta:  16.04.1 (714) 0B -
>>>   edge:  16.04.1 (870) 0B -
>>> 
>>> admin@localhost:~$ snap refresh
>>> error: cannot refresh []: cannot refresh snap-declaration for 
>>> "stlouis-kernel": Get 
>>> https://assertions.ubuntu.com/v1/assertions/snap-declaration/16/0EawO5JYYJmNw9CmweMnyrwGgJxDUHag?max-format=1:
>>>  net/http: request canceled while waiting for connection (Client.Timeout 
>>> exceeded while awaiting headers)
>>> 
>>> admin@localhost:~$ snap list
>>> Name VersionRev  Developer  Notes
>>> bluez5.37-2 15   canonical  -
>>> core 16.04.1714  canonical  -
>>> gateway  2.0x3  devmode
>>> modem-manager1.4.0-114   canonical  -
>>> network-manager  1.2.2-10   73   canonical  -
>>> snappy-debug 0.26   25   canonical  -
>>> snapweb  0.21.2 24   canonical  -
>>> stlouis  16.04-1.13 11   canonical  -
>>> stlouis-kernel   4.4.0-57-1 7canonical  -
>>> tpm2 1.0-2.112   canonical  -
>>> uefi-fw-tools1.2-0.7.2+git  2canonical  -
>>> 
>>> 
>>> snapcraft@lists.snapcraft.io
 On 11 January 2017 at 07:16, Jamie Bennett  
 wrote:
 Hi Jenny,
 
 On 09/01/17 at 10:28am, Jenny Murphy wrote:
 > Hi,
 >  My query is related to a few of the recent discussions regarding 
 > versions,
 > releases and updates/
 >
 > I currently have a Snappy Ubuntu system as follows :
 >
 > snap --version gives the following result :
 >  snap2.18.1
 >  snapd   2.18.1
 >  series  16
 >
 > more /etc/lsb-release yeilds :
 > DISTRIB_ID="Ubuntu Core"
 > DISTRIB_RELEASE=16
 > DISTRIB_DESCRIPTION="Ubuntu Core 16
 >
 > And finally snap list yields :
 > core 16.04.1641  canonical  --
 >
 > I don't see to be  getting any automatic updates which I don't mind about
 > as long as I could manually update.
 >
 > So just a few questions :
 >
 > 1. How can I update snap and snapd
 
 What happens when you type:
 
 $ snap info core
 
 Also, what happens when you type:
 
 $ snap refresh
 
 > 2. Is snap the front end to snapd ? Do they get updated together?
 
 Yes.
 
 > 3. Can I update snapd and not update ubuntu-core and core.
 
 On an Ubuntu Core system snapd is integral to the device, on a classic 
 system
 snapd is an add-on package so in the former case the system and snapd are
 updated together.
 
 > 4. Should ubuntu-core and core be updated together also? From the 
 > previous
 > reply on this topic, it seems core is the framework and ubuntu-core is 
 > the
 > filesystem or is it vice versa?
 
 ubuntu-core is the old name for core. We renamed this to better reflect 
 that
 other cores could be available that are not Ubuntu based. Do you have both 
 of
 these installed 

Use of build-properties in the schema is deprecated.

2017-01-11 Thread Jenny Murphy
I recently upgraded to snapcraft 2.24 (from 2.22) for building my .snaps.
Now I am getting the following warning :

Use of build-properties in the schema is deprecated.
Plugins should now implement get_build_properties


This is my yaml file :

name: gateway
version: '2.0' # just for humans, typically '1.2+git' or '1.3.2'
summary: EpiSensor IIoT Gateway Application # 79 char long summary
description:
  This is a Java application with  web interface and a RESTful API.
grade: devel # must be 'stable' to release into candidate/stable channels
confinement: devmode # use 'strict' once you have the right plugs and slots
icon: epi-icon-256x256px.png

apps:
  main:
command: bin/wrapper
daemon: simple
plugs: [zap-plug]

plugs:
zap-plug:
interface: serial-port

parts:
move-lib:
plugin: dump
source: ./lib/
organize:
"*": lib/
move-ext-lib:
plugin: dump
source: ./ext-lib/
organize:
"*": ext-lib/
move-webapp:
plugin: dump
source: ./webapp/
organize:
"*": webapp/
move-config:
plugin: dump
source: ./config/
organize:
"*": config/
move-scripts:
plugin: dump
source: ./scripts/
organize:
"*": scripts/
main:
   plugin: ant
   source: .
wrapper:
plugin: make
source: .
move-rxtx:
after: [move-ext-lib]
plugin: dump
source: ./rxtx
organize:
RXTXcomm.jar: ext-lib/RXTXcomm.jar
librxtxSerial.so:
usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/librxtxSerial.so


Any ideas as to why this has changed?

-- 
*Jenny Murphy*
*EpiSensor, Georges Quay House, Georges Quay, Limerick, Ireland*
jenny.mur...@episensor.com   t | +353 (0) 61
512 511  w | http://www.episensor.com
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Issue with ubuntu OS snap first time boot.

2017-01-11 Thread Oliver Grawert
hi,
Am Dienstag, den 10.01.2017, 13:35 + schrieb Ajay Pandey:
> Hi All,
>  
> We are facing issue with the Ubuntu OS snap first time boot console-
> conf.
>  
...                   
>     error: while creating user: cannot communicate with server:
> Post    
>   http://localhost/v2/create-user:
> EOF  

is this on one of the official images or is it your own build ? 
looks like snapd did not start properly.

ciao
oli

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Manual update of snap/snapd and core/ubuntu-core

2017-01-11 Thread Jenny Murphy
Hi Jamie,
Here is some more information as requested :

admin@localhost:~$ snap info core
name:  core
summary:   "snapd runtime environment"
publisher: canonical
description: |
  The core runtime environment for snapd
type:core
tracking:stable
installed:   16.04.1 (714) 79MB -
refreshed:   2016-12-16 04:28:38 + UTC
channels:
  stable:16.04.1 (714) 0B -
  candidate: 16.04.1 (714) 0B -
  beta:  16.04.1 (714) 0B -
  edge:  16.04.1 (870) 0B -

admin@localhost:~$ snap refresh
error: cannot refresh []: cannot refresh snap-declaration for
"stlouis-kernel": Get
https://assertions.ubuntu.com/v1/assertions/snap-declaration/16/0EawO5JYYJmNw9CmweMnyrwGgJxDUHag?max-format=1:
net/http: request canceled while waiting for connection (Client.Timeout
exceeded while awaiting headers)

admin@localhost:~$ snap list
Name VersionRev  Developer  Notes
bluez5.37-2 15   canonical  -
core 16.04.1714  canonical  -
gateway  2.0x3  devmode
modem-manager1.4.0-114   canonical  -
network-manager  1.2.2-10   73   canonical  -
snappy-debug 0.26   25   canonical  -
snapweb  0.21.2 24   canonical  -
stlouis  16.04-1.13 11   canonical  -
stlouis-kernel   4.4.0-57-1 7canonical  -
tpm2 1.0-2.112   canonical  -
uefi-fw-tools1.2-0.7.2+git  2canonical  -


snapcraft@lists.snapcraft.io
On 11 January 2017 at 07:16, Jamie Bennett 
wrote:

> Hi Jenny,
>
> On 09/01/17 at 10:28am, Jenny Murphy wrote:
> > Hi,
> >  My query is related to a few of the recent discussions regarding
> versions,
> > releases and updates/
> >
> > I currently have a Snappy Ubuntu system as follows :
> >
> > snap --version gives the following result :
> >  snap2.18.1
> >  snapd   2.18.1
> >  series  16
> >
> > more /etc/lsb-release yeilds :
> > DISTRIB_ID="Ubuntu Core"
> > DISTRIB_RELEASE=16
> > DISTRIB_DESCRIPTION="Ubuntu Core 16
> >
> > And finally snap list yields :
> > core 16.04.1641  canonical  --
> >
> > I don't see to be  getting any automatic updates which I don't mind about
> > as long as I could manually update.
> >
> > So just a few questions :
> >
> > 1. How can I update snap and snapd
>
> What happens when you type:
>
> $ snap info core
>
> Also, what happens when you type:
>
> $ snap refresh
>
> > 2. Is snap the front end to snapd ? Do they get updated together?
>
> Yes.
>
> > 3. Can I update snapd and not update ubuntu-core and core.
>
> On an Ubuntu Core system snapd is integral to the device, on a classic
> system
> snapd is an add-on package so in the former case the system and snapd are
> updated together.
>
> > 4. Should ubuntu-core and core be updated together also? From the
> previous
> > reply on this topic, it seems core is the framework and ubuntu-core is
> the
> > filesystem or is it vice versa?
>
> ubuntu-core is the old name for core. We renamed this to better reflect
> that
> other cores could be available that are not Ubuntu based. Do you have both
> of
> these installed on your system? In fact, can you give us a full output of:
>
> $ snap list
>
> > I know there are a lot of questions here but it is just a little bit
> >sn unclear to me at the moment. Maybe there are also some other users in
> the
> > same position.
> >
> >
> > Thanks,
> > Jenny
> >
> >
> >
> > *Jenny Murphy*
> > *EpiSensor, Georges Quay House, Georges Quay, Limerick, Ireland*
> > jenny.mur...@episensor.com   t | +353 (0) 61
> > 512 511  w | http://www.episensor.com
>
> > --
> > Snapcraft mailing list
> > Snapcraft@lists.snapcraft.io
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>



-- 
*Jenny Murphy*
*EpiSensor, Georges Quay House, Georges Quay, Limerick, Ireland*
jenny.mur...@episensor.com   t | +353 (0) 61
512 511  w | http://www.episensor.com
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Bad system call - 45 for my binary app

2017-01-11 Thread Andrey Rogovsky
Hi, all!

I crafted snap for i386 X11 app (no sources) which work success on amd64
arch in development mode.
But when I install it in strict mode - got this error:

= Seccomp =
Time: Jan 11 11:26:38
Log: auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=17988
comm="BlueQuest" exe="/snap/bluequest/x1/usr/bin/BlueQuest" sig=31
arch=4003 45(brk) compat=1 ip=0xf7749547 code=0x0
Syscall: brk

How I can resolve this problem?

This is my snapcraft file:
name: bluequest
version: 1.0
summary: Game
description: Play Blue Quest Game.
icon: BlueQuest/assets/icon.png
grade: stable
confinement: strict

apps:
  bluequest:
command: usr/bin/bluequest
plugs: [network, network-bindx11, home, unity7, pulseaudio]

parts:
  bluequest:
   plugin: dump
   source: BlueQuest
   organize:
bluequest: usr/bin/bluequest
BlueQuest: usr/bin/BlueQuest
  usrlib32:
   plugin: dump
   source: /usr/lib/i386-linux-gnu
  syslib32:
   plugin: dump
   source: /lib/i386-linux-gnu
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Slow snap build on Ubuntu Core device

2017-01-11 Thread Gustavo Niemeyer
Nice :)

On Tue, Jan 10, 2017 at 5:55 PM, Oliver Grawert  wrote:

> hi,
> Am Dienstag, den 10.01.2017, 15:40 + schrieb Alan Pope:
> >
> > >
> > For archive packages being slow (as you have) I use apt-cacher-ng on
> > my laptop. It caches the debs making snapcraft builds much faster.
>
> shamelessly promoting my onw snap here:
>
> sudo snap install packageproxy ...
>
> point your sources.list entries to http://localhost:/ubuntu-ports a
> nd be happy ;)
>
> ciao
> oli
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>


-- 

gustavo @ http://niemeyer.net
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Snapd free space available check

2017-01-11 Thread Boris Rybalkin
Done https://github.com/snapcore/snapd/issues/2603

On 9 Jan 2017 13:57, "Zygmunt Krynicki" 
wrote:

> I don't think we're doing this yet.
>
>
> Can you please report an issue so that it can be tracked.
>
> Best regards
> ZK
>
> On Sun, Jan 8, 2017 at 6:25 PM, Boris Rybalkin  wrote:
>
>> Hello,
>>
>> Could you tell me if snapd does any free space check before installing a
>> snap?
>>
>> Github link would be ideal if possible.
>>
>> Thank you.
>>
>> --
>> Snapcraft mailing list
>> Snapcraft@lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/snapcraft
>>
>>
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft