snapd 2.23.6 released to the stable channel

[Jamie Bennett]

Hi,

The snappy team is happy to announce another release of the 2.23.6 series. This 
release focuses on improving the robustness of the configuration hook system.

The new release is available in the core snap in the stable channel and should 
be making it’s way to you soon automatically.

It is also available in the 14.04, 16.04, 16.10 and 17.04 proposed pockets. 
More distributions will follow at their own pace.

To install this new release just run the following command:

$ sudo snap refresh core

Or wait for an automatic refresh.

On the classic distribution you can also enable -proposed (see 
https://wiki.ubuntu.com/Testing/EnableProposed1) and install snapd from there.

The changes in detail:
• tests: fix interfaces-cups-control for zesty
• configstate,hookstate: timeout the configure hook after 5 mins, 
report failures
• packaging: rename the file shipping snap-confine AA profile to 
workaround dpkg bug #858004
• many: ignore configure hook failures on core refresh to ensure 
upgrades are always possible
• snapstate: restart as needed if we undid unlinking aka relinked core 
or kernel snap
• support for snap core set pi-config.framebuffer_{width,height} (and a 
bunch more, 
seehttps://forum.snapcraft.io/t/configuration-options-for-core-snap/87 for all 
options) config.txt setting

The source is available at 
https://github.com/snapcore/snapd/releases/tag/2.23.69, with test results and 
more discussion at: https://forum.snapcraft.io/t/new-release-snapd-2-23-6/26

Enjoy and let us know if you notice any issues.

Regards,
The snapd release team.
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: New stable "core" and "ubuntu-core" snaps released

[Jamie Bennett]

Sorry, yes, it will land with snapd 2.23 today hence why the timer
should not be relied upon.

Regards,
Jamie.

On Fri, Feb 17, 2017 at 1:00 PM, Oliver Grawert <o...@ubuntu.com> wrote:
> hi,
> Am Freitag, den 17.02.2017, 12:04 +0000 schrieb Jamie Bennett:
>>
>> The systemd timer has gone away in favour of an internal timer in
>> snapd so
>> this will no longer work.
>>
>
> i dont think that has landed yet [1] ...
>
> ogra@dragonboard:~$ snap get core refresh.schedule
> error: snap "core" has no "refresh.schedule" configuration option
> ogra@dragonboard:~$ snap info core|grep tracking
> tracking:edge
>
> but once it has you should be able to just unset the core config option
> instead of disabling the systemd timer to not interfere with any cron
> based bits.
>
> ciao
> oli
>
> [1] https://github.com/snapcore/snapd/pull/2833
> --
> 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: snapd available in Trusty Tahr

[Jamie Bennett]

The simplest way is to log out and back in again. We are looking at other 
options on how to make this easier.

Regards,
Jamie.

> On 9 Feb 2017, at 09:02, XiaoGuo Liu  wrote:
> 
> Hi Thomas,
> 
> So, an end user needs to manually add the path, right? It is not a little bit 
> straightforward though. I think it would be good to come with detailed 
> instructions.
> 
> Thanks & best regards,
> XiaoGuo
> 
> 
> On Thu, Feb 9, 2017 at 4:39 PM, Thomas Voß  > wrote:
> 
> 
> On Thu, Feb 9, 2017 at 5:02 AM, XiaoGuo Liu  > wrote:
> Hi,
> 
> I just tried to install the snapd and installed a hello-world snap app on 
> 14.04 desktop. However, I found a problem. When I un the hello-world, it 
> shows:
> 
> liuxg@liuxg:/snap/bin$ hello-world
> hello-world: command not found
> 
> 
> This is expected behavior right now. PATH is adjusted in 
> /etc/profile.d/apps-bin-path.sh (comes with the snapd package). /etc/profile 
> and the entries in /etc/profile.d/* are only considered for login shells. 
> With that, a reboot, logout/login, or sourcing /etc/profile in your current 
> shell will give you the correct PATH setup.
> 
> We are looking into letting the user know when installing the debian package 
> (as opposed to the situation where snapd is already part of the image). See 
> https://github.com/snapcore/snapd/pull/2819 
>  for reference.
> 
> Thanks for testing,
> 
>   Thomas
> 
>  
> Which means that /snap/bin path is not added to the path after installing the 
> core. Also, when I run it under the /snap/bin, it shows:
> 
> liuxg@liuxg:/snap/bin$ ./hello-world
> ERROR: ld.so: object '/lib/$LIB/liblsp.so' from /etc/ld.so.preload cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object '/lib/$LIB/liblsp.so' from /etc/ld.so.preload cannot be 
> preloaded (cannot open shared object file): ignored.
> Hello World!
> 
> My desktop info is:
> 
> liuxg@liuxg:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID:   Ubuntu
> Description:  Ubuntu 14.04.5 LTS
> Release:  14.04
> Codename: trusty
> 
> liuxg@liuxg:~$ snap list
> Name Version  Rev  Developer  Notes
> core 16.04.1  888  canonical  -
> hello-world  6.3  27   canonical  -
> 
> Thanks & best regards,
> XiaoGuo
> 
> 
> On Wed, Feb 8, 2017 at 5:35 AM, Andrew Mason 
>  > wrote:
> Awesome, i am going to give this a try!
> 
> On 8 February 2017 8:01:30 am ACDT, 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
> >  
> > 
> > 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 for
> a spin.
> The experience is very clean now. I just tried on AWS and have RocketChat up 
> and 
> running-
> 
> 
> Kudos to everyone involved in delivering this!
> 
> Cheers,
> Manik
> 
> -- 
> Sent from my mobile device.
> 
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io 
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/snapcraft 
> 
> 
> 
> 
> 
> -- 
> XiaoGuo, Liu 
> 
> --
> 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 
> 
> 
> 
> 
> 
> -- 
> XiaoGuo, Liu 
> -- 
> 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: the ppp interface (and general renaming/transitioning of interfaces)

[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.ubuntu.com/23941360/
> > 
> wow, this is weird, yes, it is indeed still in there, i was 100% sure
> it was dropped together with the watchdog package when i got a ping
> from you guys to drop both after 15.04 ... but i just checked the
> respecting seed diff and noticed only watchdog was actually dropped ...
> 
> so please ignore this ...
> 
> yet, we probably still want an interface that allows access to console
> devices only. and also plan some process in case we need to rename
> interfaces if their backend changes.

Access to serial tty-only devices makes sense and a dedicated interface makes
sense.

> 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: Using docker for clean builds of classic snaps

[Jamie Bennett]

Hi Joe,

We have this page that explains how to build using Docker containers (the url 
name is wrong but the contents are right).

  * https://snapcraft.io/docs/build-snaps/trusty

Regards,
Jamie.

> On 1 Feb 2017, at 22:47, Joseph Rushton Wakeling 
>  wrote:
> 
> Hello all,
> 
> Curious question.  Since snapcraft cleanbuild support is still a 
> work-in-progress for classic snaps, has anyone tried using Docker to provide 
> a clean build environment for them?  If so -- can you advise on what you did?
> 
> I'm not super Docker-experienced, so while I imagine setting up the basic 
> environment wouldn't be too difficult -- I don't imagine the dockerfile would 
> need much more than FROM ubuntu:16.04 and the installation of snapcraft -- 
> I'm not sure how to run the actual snapcraft command via Docker.  Can anyone 
> suggest how to do this?
> 
> No worries if no one can advise -- if not, assuming cleanbuild support isn't 
> close in the pipeline, I will try to look into this further myself in the 
> next weeks.
> 
> Thanks & best wishes,
> 
>-- Joe
> 
> -- 
> 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

snapd available in Trusty Tahr

[Jamie Bennett]

Hi,

The team are pleased to announce that, after extensive testing in proposed, 
snapd is officially available in the Trusty Tahr updates archive [1]. If you 
are running a 14.04 system we encourage you to give it a try and report any 
issues [2]. Thanks to all involved in making this happen.

Regards,
Jamie.

[1] https://launchpad.net/ubuntu/trusty/+source/snapd
[2] https://bugs.launchpad.net/ubuntu/+source/snapd
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Snaps are not just for the serious things ...

[Jamie Bennett]

> On 27 Jan 2017, at 14:44, Alan Pope  wrote:
> 
> Hi,
> 
> Happy Friday everyone.
> 
> I discovered 'bucklespring' in the snap store recently. You may enjoy it 
> too...
> 
> https://www.youtube.com/watch?v=4cp6j42NXnM 
> 

Love this!

> We need more of these kinds of fun things :)
> 
> Cheers,
> -- 
> Alan Pope
> Community Manager
> 
> Canonical - Ubuntu Engineering and Services
> +44 (0) 7973 620 164
> alan.p...@canonical.com
> http://ubuntu.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

Re: CUPS in a snap: Using content interface to connect printer driver snaps

[Jamie Bennett]

> On 26 Jan 2017, at 07:50, Alberto Mardegan  
> wrote:
> 
> On 25/01/2017 21:29, Till Kamppeter wrote:
>> So CUPS needs to provide a slot to take these files somehow and this
>> slot needs to accept any printer driver snap and any number of printer
>> driver snaps.
>> 
>> Can one do this with the "content" interface? And if yes, how?
> 
> Note: snapd developers are very welcome to correct me if I'm wrong. :-)
> 
> My understanding is that this is currently not possible, but it's being
> worked on in an effort called "interface hooks": these are executables
> shipped by your snap which will be run whenever an interface gets
> connected. They can be provided either by the consumer snap (plug) or by
> the provider snap (socket), or both. You could use them to register the
> driver into cups.
> 
> By the way, do we have an ETA for this feature? I'm also in a badly need
> for it. :-)

The work is progressing nicely but no definitive ETA at the moment. We are all 
looking forward to seeing it as soon as possible.

> Ciao,
>  Alberto

Regards,
Jamie.

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

Re: [NEWS] KDE Application snaps in stable channel

[Jamie Bennett]

> On 23 Jan 2017, at 14:54, Michael Hall  wrote:
> 
> With the release of Snapd 2.20 (and corresponding Snapcraft release)
> that introduced the new dbus interface, Harold Sitter from KDE was
> unblocked on the last thing keeping KDE applications from being cleanly
> snapped and published in the Snap Store.
> 
> https://apachelog.wordpress.com/2017/01/20/snapping-dbus/
> 
> These KDE App snaps also take advantage of the content interface to
> share a common kde-frameworks-5 snap that contains the bulk of their
> platform dependencies. This keeps the individual application snap sizes
> down to 5mb or less.

The framework snap is 203.44mb but indeed, the other apps are pretty small. One 
caveat is that you must install the framework first before any KDE application 
and that there is no auto-installation of the framework if you do it in the 
wrong order. Installing the application first, then the framework results in an 
"error while loading shared libraries: libKF5Crash.so.5: cannot open shared 
object file: No such file or directory” error until you remove the app and 
reinstall. Still, it’s a great step forward with just a few kinks to iron out, 
great work and I’m looking forward to more KDE snaps!

> You can find the currently published apps with "snap find kde", and
> there are more that are in the process of being snapped and published.
> 
> -- 
> Michael Hall
> mhall...@ubuntu.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

Re: Which snap interface allows accessing /dev/rfkill?

[Jamie Bennett]

Hi Tonny,

A quick grep of the snapd source code shows that /dev/rfkill is part of the 
network-control and network-manager interfaces.

Regards, 
Jamie.

> On 19 Jan 2017, at 09:41, Tonny Tzeng  wrote:
> 
> Hi,
> 
> I'd like to unblock the Bluetooth interface on Ubuntu Core, so I use 
> 'stage-packages' keyword to install 'rfkill' package to my snap. If I install 
> the snap in devmode, the rfkill command works as expected. But if the snap is 
> installed in confined mode, I always get 'Permission denied', and the 
> /var/log/syslog shows below message:
> 
> Jan 19 09:17:42 localhost kernel: [177262.419927] audit: type=1400 
> audit(1484817462.015:2031): apparmor="DENIED" operation="open" 
> profile="snap.iotivity-smarthome-demo.rfkill" name="/dev/rfkill" pid=14430 
> comm="rfkill" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
> 
> Would anyone help me which interface should I declare with the plugs keyword? 
>  I've tried hardware-observe and bluetooth-control interfaces but no success. 
> Any pointers would be appreciated, thanks in advance.
> 
> Best Regards,
> Tonny
> -- 
> 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: Please test my asciinema snap

[Jamie Bennett]

On 18/01/17 at 04:19am, Mark Shuttleworth wrote:
> 
> ... you may also need to enable xenial-proposed main in
> /etc/apt/sources.list to make sure you have the very latest snapd.

Yes, classic needs snapd 2.21 from proposed otherwise you will not be able to
find or install the snap.

After that, it works a treat [1], thanks.

> Mark

Regards,
Jamie.

[1] https://asciinema.org/a/bdlo4mxqzvko1sfretclbzl79

> On 18/01/17 04:16, Mark Shuttleworth wrote:
> > It's a 'classic-only' snap, so you need:
> >
> >   sudo snap install --classic asciinema
> >
> > Then 'asciinema rec' starts a recording session, and you're off to the
> > races.
> >
> 
> 
> -- 
> 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: [announce] twistypuzzle snap

[Jamie Bennett]

Great work Spencer. I presume your project is hosted on GitHub at:

  * https://github.com/spencerparkin/TwistyPuzzle

I don't see a snapcraft.yaml file there so I would be interested in
what it looks like and how you found the whole process.

After playing with it briefly I have filed the following bug.
  * https://github.com/spencerparkin/TwistyPuzzle/issues/1

Regards,
Jamie.

On Wed, Jan 18, 2017 at 6:39 AM, Spencer Parkin
 wrote:
> Hi,
>
> I've just uploaded to beta channel my new snap: twistypuzzle.  Unlike
> "rubecube," one of my other snaps, this one can simulate a variety of twisty
> puzzles.  My main motivation is the technical challenge such a program
> represents.
>
> There are still some bugs that must be resolved before releasing to the
> stable channel, but in the mean time, I'd be curious to know what anyone
> thinks about it.  I think it's a cool idea, but hey, maybe it's not.
>
> Out of curiosity, is there a way to monetize a snap?  I see a "buy" option
> in the snap command, and I see a "price" field on the Ubuntu Apps web-page
> for my snap, but I can't seem to find any information about how to configure
> these for a snap.  I don't think my snaps are worth anything, and I want
> people to actually use them (so I want them to be free), but it would be
> interesting to know how or if this can be done.
>
> Thanks,
> --Sp
>
> --
> 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

[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 <jenny.mur...@episensor.com> 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 <ma...@canonical.com> 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/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 <jamie.benn...@canonical.com> 
>>>> 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

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

[Jamie Bennett]

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
> 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

Re: Only one page of snaps on SnapWeb?

[Jamie Bennett]

Hi Chris,

> On 19 Dec 2016, at 15:52, Chris <cpoll...@embarqmail.com> wrote:
> 
> On Mon, 2016-12-19 at 11:06 +, Jamie Bennett wrote:
>> Hi Chris,
>> 
>>> 
>>> On 18 Dec 2016, at 14:31, Chris <cpoll...@embarqmail.com> wrote:
>>> 
>>> I've asked this before but I'm still wondering why there is only
>>> one
>>> page of snaps listed (A-E)? I can do a search for a snap such as
>>> 'PubIP' and it will come up but there is no way in SnapWeb to go
>>> forward from the first page.
>> 
>> This functionality is being worked on but the idea of SnapWeb is not
>> to show you every single possible snap that can be installed (that
>> would quickly get quiet unwieldily), instead we aim to surface the
>> most prominent snaps. Think of it like a real bricks-and-mortar
>> store; the snaps that are featured are right there in the store
>> window for everyone to see, the most popular snaps per category are
>> in their own sections, and the stuff that you knew up front you
>> wanted but can’t find being displayed can always be retrieved from
>> the warehouse. So mapping that to what we have in the SnapWeb edge
>> channel today, the front store page should be [1] the featured snaps,
>> at the top you can select categories like database, media, messaging
>> [2] for the most popular snaps in that category, and if you know what
>> you want you can use the search bar.
>> 
>> SnapWeb is being actively worked on so you will see lots of changes
>> regularly. If you want to see the latest please:
>> 
>>   $ snap refresh —edge snapweb
>> 
>> or, on a system without snapweb
>> 
>>   $ snap install —edge snapweb
>> 
> Thanks for the explanation Jamie. Using the above command I updated to
> 0.23.9 and reloaded snapweb in Firefox. I'm curious though as to what's
> the purpose of what I show in the screenshot.

This too is work in progress, as the —edge channel disclaimer implies. The team 
are looking to add more functionality to SnapWeb to expose the most common 
requirements for a web-based frontend on an IoT gateway-like device. This 
includes showing information about the device itself, any users that are 
associated with the device, software updates available, and to allow some 
settings to be changed. What your screenshot shows is the beginning of that 
work.

Keep an eye out for more changes and improvements to the project in the coming 
weeks/months.

>> and file any bugs at https://bugs.launchpad.net/snapweb
>> 
>> Regards,
>> Jamie.
>> 
>> [1] “should be” - this functionality is currently being worked on and
>> is very new.
>> [2] Snap Sections are again very new. We are still coming up with the
>> right naming scheme and ensuring each snap is in the right place. 
>> 
>>> 
>>>  
> -- 
> Chris
> KeyID 0xE372A7DA98E6705C
> 31.11972; -97.90167 (Elev. 1092 ft)
> 09:20:12 up 4 days, 15:39, 2 users, load average: 0.34, 0.24, 0.35
> Ubuntu 16.04.1 LTS, kernel 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2
> 15:59:10 UTC 2016-- 
> 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: Only one page of snaps on SnapWeb?

[Jamie Bennett]

Hi Chris,

> On 18 Dec 2016, at 14:31, Chris  wrote:
> 
> I've asked this before but I'm still wondering why there is only one
> page of snaps listed (A-E)? I can do a search for a snap such as
> 'PubIP' and it will come up but there is no way in SnapWeb to go
> forward from the first page.

This functionality is being worked on but the idea of SnapWeb is not to show 
you every single possible snap that can be installed (that would quickly get 
quiet unwieldily), instead we aim to surface the most prominent snaps. Think of 
it like a real bricks-and-mortar store; the snaps that are featured are right 
there in the store window for everyone to see, the most popular snaps per 
category are in their own sections, and the stuff that you knew up front you 
wanted but can’t find being displayed can always be retrieved from the 
warehouse. So mapping that to what we have in the SnapWeb edge channel today, 
the front store page should be [1] the featured snaps, at the top you can 
select categories like database, media, messaging [2] for the most popular 
snaps in that category, and if you know what you want you can use the search 
bar.

SnapWeb is being actively worked on so you will see lots of changes regularly. 
If you want to see the latest please:

  $ snap refresh —edge snapweb

or, on a system without snapweb

  $ snap install —edge snapweb

and file any bugs at https://bugs.launchpad.net/snapweb

Regards,
Jamie.

[1] “should be” - this functionality is currently being worked on and is very 
new.
[2] Snap Sections are again very new. We are still coming up with the right 
naming scheme and ensuring each snap is in the right place. 

> -- 
> Chris
> KeyID 0xE372A7DA98E6705C
> 31.11972; -97.90167 (Elev. 1092 ft)
> 08:24:21 up 3 days, 14:43, 2 users, load average: 0.36, 0.28, 0.40
> Ubuntu 16.04.1 LTS, kernel 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2
> 15:59:10 UTC 2016-- 
> 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: Ubuntu core on BBB

[Jamie Bennett]

Hi Luther,

> On 16 Dec 2016, at 08:19, Luther Goh Lu Feng  wrote:
> 
> Thanks for the clarification.
> 
> My beaglebone black is from element14. There seems to be beagleblack gadget 
> snap listed[1][2], which I can also find in the output
> 
> $ snap info beagleblack --verbose
> 
> The listed publisher is mvo. May I know how I can get the contact with the 
> publisher?

mvo is Michael Vogt, ogra is Oliver Grawert, both of which are on the Snappy 
team at Canonical.

For clarification, we have a number of official reference platforms produced by 
the Snappy team, they are:

* Raspberry Pi2/3
* Qualcomm Dragonboard 410c
* x86 32/64

The Beaglbone black support is what we call a ‘community build’, done by 
enthusiasts but not part of the official list. We very much encourage people to 
create community builds for their favourite boards and this is what ogra and 
mvo have done.

> I have contacts in element14 that I can reach out to but would like to 
> understand the context and status of the gadget snap published by mvo.

I think you should talk to element14 about having Ubuntu Core as an official 
option or directly with Beagleboard themselves. Beagleboard have a forum where 
you could start the conversation or contact information on - 
https://beagleboard.org/about .

Regards,
Jamie.

> I am also curious why ogra published his own gadget snap instead of using the 
> "official looking" beagleblack snap (see screenshot). Thanks
> 
> 
> -- Luther
> [1] https://developer.ubuntu.com/en/snappy/start/gadget-snaps/
> [2] https://uappexplorer.com/apps?type=snappy=beagle=relevance
> 
> 
> 
> 
> On Friday, December 16, 2016 3:17 PM, Mark Shuttleworth  
> wrote:
> Hi Luther
> 
> To help firm up BBB support, please log that request / preference with
> the SoC manufacturer. Rpi2/3 and Qualcomm Dragonboard are already
> certified iirc.
> 
> Mark
> -- 
> 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: running your pi3 from USB only (no SD card)

[Jamie Bennett]

> On 15 Dec 2016, at 17:45, Oliver Grawert  wrote:
> 
> hi,
> 
> a minute ago a new gadget snap for the pi3 has hit the edge channel.
> 
> alfonso beato kindly provided a pull request that enables our pi3
> gadget to completely boot from USB after you turned your ROM to USB
> boot following the instructions on [1].
> 
> this will allow you to drop SD cards completely if desired, just dd
> your image to USB disk/stick and boot away ...
> 
> enjoy ... and thanks again to alfonso !

Great news!

> ciao
>   oli
> 
> [1] https://www.raspberrypi.org/documentation/hardware/raspberrypi/boot
> modes/msd.md-- 
> 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: docker snap not working

[Jamie Bennett]

Yes, thanks to mvo we will test Docker as part of the usual test battery.

Regards,
Jamie.

> On 6 Dec 2016, at 16:34, Loïc Minier  wrote:
> 
> Michael Vogt just added this check; nice!
> https://github.com/snapcore/snapd/pull/2421 
> 
> 
> On Tue, Dec 6, 2016 at 3:34 PM, Mark Shuttleworth  > wrote:
> 
> Can we add Docker to a list of 'critical snaps' that is part of our 
> pre-release validation suite?
> 
> Mark
> 
> 
> On 06/12/16 05:05, Manik Taneja wrote:
>> 
>> 
>> On Dec 6, 2016, at 4:51 AM, Loïc Minier > > wrote:
>> 
>>> Hi,
>>> 
>>> On Tue, Dec 6, 2016 at 3:49 AM, Peng Liu >> > wrote:
>>> There is some known issue of the docker snap, check the google doc for 
>>> detailed information.
>>> https://docs.google.com/document/d/1JHa6tkuR9PtpnAVVmAJIAKuyKBy8E9ZkvG5Wbc6HZSY/edit#
>>>  
>>> 
>>> 
>>> And you need to make sure your snapd is the latest version.
>>> 
>>> Exactly; it only affects Ubuntu Core images (not snaps on classic), and 
>>> there are two workarounds:
>>> - either install the snap with devmode
>>> - or run this after boot (and then restart dockerd):
>>> $ sudo nsenter -m/run/snapd/ns/docker.mnt
>>> 
>>> 
>>> # umount --lazy /var/lib/snapd/hostfs/sys
>>> 
>>> The fix is in snap-confine git and is planned for upload this Friday.
>> Thanks Loic!
>>> 
>>> Best regards,
>>> - Loïc Minier
>>> -- 
>>> 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 
> 
> 
> 
> 
> 
> -- 
> - Loïc
> -- 
> 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: quassel-webserver snap

[Jamie Bennett]

On 24/11/16 at 08:11am, Didier Roche wrote:
> Le 23/11/2016 à 18:19, Celso Providelo a écrit :
> >
> >
> > On Wed, Nov 23, 2016 at 2:52 PM Leo Arias  > > wrote:
> >
> > Hello,
> >
> > I know a bunch of people here use quassel. There's a new snap for you:
> >
> > $ sudo snap install quassel-webserver --edge
> > $ sensible-browser https://localhost:64443
> >
> > The main developer, Joël Charles, has been amazing. For a couple
> > of weeks we have been experimenting with his project. First, we
> > had to solve an issue with the less-middleware module because it
> > wanted to use the install directory instead of SNAP_DATA [1], then
> > we got travis to build the snap on every PR [2], and finally he
> > agreed to beta test the new enable-ci command of snapcraft that
> > Celso is working on.
> >
> > When I asked about feedback or feature requests, he said: "Not
> > that I think of, it just went very smoothly" :_)
> >
> > Of course, a few seconds later travis broke and we found a bug in
> > Celso's PR, just to keep us grounded. It was a quick fix, and now
> > every change on master will build and push the snap to edge [3].
> >
> > I really want to thank Joël because we now have a set of scripts
> > tested in real live, that we can just apply to new projects. Also
> > Celso because without the enable-ci command, this would never have
> > been a smooth experience.
> >
> >
> > Amazing work Leo! Thanks for jumping in so quickly (it's not even
> > landed in master) and experimenting with this feature in real
> > circumstances.
> >
> > Until it lands and 2.23 gets SRU-ed in xenial we have to cope with the
> > lack of support for local store credentials (`.snapcraft.cfg`). There
> > are other less-intrusive alternatives like [1], but once the
> > transition is gone `enable-ci` will do the right thing for the
> > majority of projects (simple ones).
> >
> > We hope this initiative along with build.snapcraft.io
> >  (down the road) will considerably increase
> > the number of revisions released in edge, like we already see for core
> > and lxd. That's why we are also working on metrics to capture how
> > developers are pushing/releasing their snaps (webui, snapcraft,
> > travis, LP, etc). It will be nice to observe these trending as we
> > offer easier ways to do CI with snaps.
> >
> Great work guys!
> 
> It would be nice of you guys to blog about your experience for
> integrating CI from master and push to the store on a edge channel as a
> step by step recipe. Maybe something worth posting on
> https://insights.ubuntu.com?

On a similar note, lets get the Quassel guys blogging about it too, I
don't see anything on http://quassel-irc.org/ atm.

> Cheers,
> Didier

> -- 
> 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: Ms Dev center ugh

[Jamie Bennett]

On 23/11/16 at 07:38pm, Spencer wrote:
> Just wanted to say that the Ubuntu snap submission process is infinitely 
> better than Microsoft's app submission process.  Ironically, while I do not 
> consider my self particularly Linux-literate, figuring out snaps has been so 
> much more enjoyable than Microsoft packages.  And their website is crap.
> 
> Sorry.  Just had to throw that into the void.

It's great to hear you had a good time snapping your software Spencer,
welcome to the community.

Regards,
Jamie.

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

Re: Provisional snap for DUB (D language package/build manager)

[Jamie Bennett]

Regards,
Jamie.

> On 1 Nov 2016, at 23:43, Sergio Schvezov  
> wrote:
> 
> 
> 
>> El 01/11/16 a las 23:31, Joseph Rushton Wakeling escribió:
>>> On 27/10/16 22:13, Joseph Rushton Wakeling wrote:
 On 27/10/16 08:37, Didier Roche wrote:
 I would look at /var/log/syslogs. Apparmor and seccomp denials are
 listed there. Note that if you didn't already, you should really start
 developping your snap in devmode. That way, it will get confinment out
 of the equasion to get your relocatable code and dependencies working.
 Then, we can turn on confinement and figure out those issues to be able
 to publish in the stable channel.
>>> 
>>> Yea, I probably should have started with devmode.  Thanks for the advice 
>>> about
>>> syslogs; I'll check it out and see what I can find.
>> 
>> OK, so it looks like apparmor was indeed responsible.  The loglines in 
>> question:
>> 
>> Oct 30 17:50:50 computername kernel: [ 9532.992875] audit: type=1400 
>> audit(1477846250.853:43): apparmor="DENIED" operation="link" 
>> profile="snap.dub.dub" 
>> name="/home/username/code/D/dgraph/build/dgraph_graphtest" pid=22464 
>> comm="dub" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 
>> target="/home/username/code/D/dgraph/.dub/build/application-debug-linux.posix-x86_64-ldc_0-B7AFC7F4AA486AA98C5445F91F5653DB/dgraph_graphtest"
>> Oct 30 17:50:50 computername kernel: [ 9533.035303] audit: type=1326 
>> audit(1477846250.897:44): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
>> pid=22464 comm="dub" exe="/snap/dub/x1/bin/dub" sig=31 arch=c03e 
>> syscall=92 compat=0 ip=0x7f9b72d13717 code=0x0
>> 
>> I'm not experienced with apparmor, so could someone explain exactly what 
>> this means?  (I get the general idea, but the specifics would be useful to 
>> understand precisely.)
> 
> If this is x86_64, everything is aligned with the world, syscall 92 is chown. 
> A useful tool here can help you out, and luckily there is one, run `snap 
> install snappy-debug` and it will do some nice things to figure out what is 
> going on wth these apparmor and seccomp blockers.
> 
>> 
>> In particular, is there an obvious reason why this might be showing up with 
>> the dub snap, when the earlier ldc2 snap didn't have this problem?  I would 
>> guess because the ldc2 instance used by the snap-packaged dub is internal to 
>> the snap and does not benefit from the home-directory interface that dub 
>> itself gets?
> It seems to be just a dub problem.
> 
>> 
>> Setting the containment to devmode removes the problem, but it would be nice 
>> to be able to have strict confinement earlier rather than later.
>> 
> If this is the problem and you can patch the software then removing the chown 
> could work, I am CCing Jamie for other ideas that could come up.
> 
> -- 
> 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: Snap sources

[Jamie Bennett]

Try the https interface which would be:

git clone https://github.com/snapcore/snapweb.git

Regards,
Jamie.

On Tue, Oct 11, 2016 at 3:23 PM, Chris  wrote:
> On Tue, 2016-10-11 at 09:56 +0200, Didier Roche wrote:
>> Le 10/10/2016 à 23:45, Chris a écrit :
>> >
>> > Other than those shown here - https://uappexplorer.com/apps?type=sn
>> > appy
>> > =title are there other places to get Snaps from?
>> >
>> Actually, there is now!
>>
>> If you use the beta3 images, they come with snapweb baked in
>> (listening
>> on port 4200). You can connect to it, click on "store" and you will
>> see
>> the available snaps for your architecture!
>>
>> You should be able to install it as well on your desktop system.
>>
>> Didier
>>
> Hmm, everything was going really well until I ran the command
>
> chris@localhost:~/GO_PROJECTS/src/github.com/snapcore$ git clone git@gi
> thub.com:snapcore/snapweb.git
> Cloning into 'snapweb'...
> Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> Not sure what I should be do now.
>
> Chris
>
> --
> Chris
> KeyID 0xE372A7DA98E6705C
> 31.11972; -97.90167 (Elev. 1092 ft)
> 09:19:10 up 15:29, 1 user, load average: 0.38, 0.32, 0.36
> Ubuntu 16.04.1 LTS, kernel 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:11:45 
> UTC 2016
>
>
> --
> 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: More Ubuntu-Core boot up problems...

[Jamie Bennett]

Hi Mike,

> On 6 Sep 2016, at 21:27, MikeB  wrote:
> 
> I'm building a Ubuntu Core image using latest snapcraft to build a 4.4-based 
> kernel snap.
> 
> I then use ubuntu-device-flash core 16 --channel=edge --kernel=$snap 
> --gadget=pc --os=ubuntu-core -o $IMG to create the image.
> 
> I then have a script that converts the image file to an ONIE NOS installer - 
> but that's irrelevant.
> 
> Up until this weekend, things were going pretty well.  I could boot ubuntu 
> core on my target network switch, set up the Ubuntu profile, then login in 
> using ubuntu/ubuntu.
> 
> I rebuilt this weekend and now I can still boot up and set up the Ubuntu 
> profile, but I can't login.  The ubuntu/ubuntu doesn't work and I tried every 
> combination of my Ubuntu profile user that I could think of, but can't login.

Recently we changed the first boot experience, removing the default user (this 
is insecure if people forget to remove/change the password) and instead we 
require that the device is set up manually. This process uses console-conf and 
will walk you through setting up a first user (must have a store account) and 
any network changes that may be needed. For this you will need a screen and 
keyboard attached. We are looking at alternative options to configure a device 
for people who do not have a screen and keyboard attached but that is something 
for the near future.

Regards, 
Jamie.

> So, my switch is now pretty much a brick.
> 
> Here's the last things on the console I see...
> 
> [  OK  ] Started Generate sshd host keys.
>  Starting OpenBSD Secure Shell server...
> [FAILED] Failed to start Run snappy firstboot setup.
> See 'systemctl status snapd.firstboot.service' for details.
> [  OK  ] Started Snappy daemon.
> [  OK  ] Started Network Service.
>  Starting Update resolvconf for networkd DNS...
> [  OK  ] Started OpenBSD Secure Shell server.
> [  OK  ] Reached target Multi-User System.
> [  OK  ] Reached target Graphical Interface.
>  Starting Update UTMP about System Runlevel Changes...
>  Starting Notify bootloader that boot was successful...
> [  OK  ] Started Update UTMP about System Runlevel Changes.
> [FAILED] Failed to start Notify bootloader that boot was successful.
> See 'systemctl status snapd.boot-ok.service' for details.
> [  OK  ] Started Update resolvconf for networkd DNS.
> 
> 
> The first 'Failed' has been happening all along.  But the second 'Failed' is 
> new to me.  Usually, at this point I see some cloud-init/network-init 
> messages but that's not happening.
> 
> I can't login, so I can't tell you what 'systemctl status' is for those 
> errors.
> 
> Any help would be appreciated.
> 
> Thanks, Mike
> -- 
> 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: DEPRECATED: 'license' defined in snapcraft.yaml

[Jamie Bennett]

On 05/09/16 at 01:34pm, Simon Fels wrote:
> On 05.09.2016 13:31, Jamie Bennett wrote:
> > On 05/09/16 at 07:06pm, Stuart Bishop wrote:
> >> On 5 September 2016 at 18:08, David Callé <david.ca...@canonical.com> 
> >> wrote:
> >>
> >>
> >> > License files can be copied across if they are present in the setup/
> >> > directory. Reproduced from docs/meta.md
> >> >
> >> > "
> >> > ## Fixed assets
> >> >
> >> > Some metadata is provided in the form of conventions, such as license
> >> files,
> >> > icons and desktop files among others. For these fixed files to make 
> >> it
> >> into
> >> > your final snap they need to be in a `setup` directory at the same 
> >> level
> >> of
> >> > your `snapcraft.yaml`.
> >> > "
> >> >
> >> > Of course the website needs updating to reflect the new syntax (and 
> >> the
> >> fact
> >> > that icon e.t.c also uses the setup/ dir now).
> >>
> >> You can find these details in the docs here:
> >> http://snapcraft.io/docs/build-snaps/metadata#fixed-assets
> >>
> >>
> >>
> >> This does not mention the magic name(s) needed for license (nee licence,
> >> copyright, legal, copying etc.) files to be discovered and made available 
> >> from
> >> the snap metadata by installers, the snap store or other consumers. Which 
> >> is
> >> what we are really asking.
> > 
> > Just put the license in the setup/ directory and name it license.txt.
> 
> What does this actually trigger? Is it detected by the store? Or is it
> just shipped with the snap and then being available as part of $SNAP?

I don't know if it is used in the store, someone else with more knowledge will
have to comment.

> regards,
> Simon

Regards,
Jamie.
 
> -- 
> 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: DEPRECATED: 'license' defined in snapcraft.yaml

[Jamie Bennett]

On 05/09/16 at 07:06pm, Stuart Bishop wrote:
> On 5 September 2016 at 18:08, David Callé  wrote:
> 
>
> > License files can be copied across if they are present in the setup/
> > directory. Reproduced from docs/meta.md
> >
> > "
> > ## Fixed assets
> >
> > Some metadata is provided in the form of conventions, such as license
> files,
> > icons and desktop files among others. For these fixed files to make it
> into
> > your final snap they need to be in a `setup` directory at the same level
> of
> > your `snapcraft.yaml`.
> > "
> >
> > Of course the website needs updating to reflect the new syntax (and the
> fact
> > that icon e.t.c also uses the setup/ dir now).
> 
> You can find these details in the docs here:
> http://snapcraft.io/docs/build-snaps/metadata#fixed-assets
> 
> 
> 
> This does not mention the magic name(s) needed for license (nee licence,
> copyright, legal, copying etc.) files to be discovered and made available from
> the snap metadata by installers, the snap store or other consumers. Which is
> what we are really asking.

Just put the license in the setup/ directory and name it license.txt.
 
> --
> Stuart Bishop 

Regards,
Jamie.

> -- 
> 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: Interface for accessing /dev/net/tun

[Jamie Bennett]

On 03/09/16 at 12:45pm, Casey Marshall wrote:
> I'm trying to write a snap for OpenVPN with some wrapper scripts that automate
> PKI setup, IP masq, etc. My goal is to be able to setup an OpenVPN server with
> a single command, and then issue new clients with a single command. I'm using
> strict mode, because that's how I roll.
> 
> I've added the firewall-control and network-control plugs, and that allowed
> some things to work (like setting up IP masq, etc.). However openvpn cannot
> start up, it's getting denied from opening /dev/net/tap, https://github.com/
> cmars/easy-openvpn-pkg/blob/master/TODO.md#
> tuntap-access-for-openvpn-in-strict-mode
> 
> Would it be reasonable to contribute a patch to snapd adding the tun and/or 
> tap
> devices to the network-control interface? Or would these constitute a new
> interface?

As this interface is just a network device, albeit for user space programs, it
makes sense for this to be part of the network-control interface IMHO.

> -Casey

Regards,
Jamie.

> -- 
> 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