Re: Locally extending trusted certificates

[Manik Taneja]

hi there,

just wanted to follow-up on this query and see if we have a solution to
this problem?

/manik

On Fri, Jan 6, 2017 at 9:17 AM, Loïc Minier  wrote:

> Hi,
>
> This question came up in the context of Docker registries with self-signed
> certificates:
> http://askubuntu.com/questions/868268/add-self-signed-certif
> icate-in-ubuntu-core-16-04
> this could be addressed in ways specific to the Docker snap, but I believe
> this touches a larger question: support for extending the list of
> system-trusted certificates.
>
> Our Ubuntu Core images ship with a set of trusted certificates. These are
> inherited from the .deb world where there is a mechanism to locally extend
> the list of trusted certificates (update-ca-certificates). This mechanism
> doesn't work with core images due to read-only directories (and perhaps
> other issues as well).
>
> Here are some possible options to address this:
> 1) fix the update-ca-certificates system to also work on core images; this
> might just be a matter of making some directories bind-mounts to the
> writable space
>
> 2) implement some kind of snapd keystore feature/configs/APIs (much like
> system keystores on mobile OSes); this is likely significant work, but
> opens interesting perspectives in providing new management APIs and a more
> secure implementation. For instance, one could design this to store secrets
> in hw-specific secure stores, or offer mechanisms to roll out new
> certificates/keys via assertions, or to disable some specific CAs
>
> 3) keep the list of system certificates as static and not locally
> configurable; this will likely result in some snaps developing alternate
> keystores
>
> I'm sure there are other options and I'd to hear how people think this
> should best be addressed in the snap/snapd world.
>
> Cheers,
> - 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

Re: Classic confinement and core_dynamic_linker

[Joseph Rushton Wakeling]

On 18/01/17 13:12, Sergio Schvezov wrote:

After a quick but thorough conversation with Gustavo we agreed that this is the 
wrong path to take as it might not be deterministic or people might get 
surprised about things included that shouldn't have been.

There needs to be a clear line between `build-packages` and `stage-packages`. 
With that in mind snapcraft (even for `strict` snaps) will still crawl all the 
libraries and error on missing ones with a list of those that are missing. This 
should be something one can disable and set to ignore as some of the missing 
libraries might be provided by a content interface slot from another snap.


Well, I'm glad that my question may have led to a more rigorous and consistent 
definition of desired snapcraft behaviour, even if it means a slightly longer 
snapcraft.yaml ... :-)


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

Re: Classic confinement and core_dynamic_linker

[Joseph Rushton Wakeling]

On 18/01/17 02:21, Sergio Schvezov wrote:

The logic is still run, but the resulting binary in classic uses rpath and no 
dynamic loading so there is no resolution to a on-system library we can pick 
up. I guess we can do some magic, but it feels it might be either fragile or 
make the build process a lot slower. We will need to look into it, but not 
short term.


OK -- thanks for the explanation.  Completely understand the preference to 
require explicit staging of packages over potentially fragile automation.


Anyway, I had a go at tweaking my snap package as defined here:
https://github.com/WebDrake/ldc2.snap/pull/1/files
https://github.com/WebDrake/ldc2.snap/blob/a437ec17d50bdd767febebf5b617d7d3a716716b/snapcraft.yaml

... to use `classic` confinement and staging packages necessary for linking. 
I've posted the resulting `snapcraft.yaml` below.  The major diff apart from the 
`confinement` setting is the addition of these lines to the `ldc` part of the file:


stage-packages:
- libconfig++-dev
- libphobos2-ldc-dev

When I run `snapcraft build`, however, everything builds and links fine, but 
_nothing_ gets staged (the `stage/` and `prime/` directories both remain empty). 
 I've tried the same thing while removing the `gcc`, `gcc-wrapper`, `libc6` and 
`libc6-dev` parts, with the same result.


Any thoughts on what could be the problem here?


--- snapcraft.yaml --

name: ldc2
version: "1.1.0-beta6"
summary: D compiler with LLVM backend
description: |
LDC is a portable compiler for the D programming Language, with
modern optimization and code generation capabilities.  It uses
the official DMD compiler frontend to support the latest version
of D2, and uses the LLVM Core libraries for code generation.
confinement: classic
grade: devel

apps:
  ldc2:
command: ldc2
plugs: [home]
  ldmd2:
command: ldmd2
plugs: [home]
  ldc-profdata:
command: ldc-profdata
plugs: [home]

parts:
  ldc:
source: git://github.com/ldc-developers/ldc.git
source-tag: v1.1.0-beta6
plugin: cmake
stage:
- -etc/ldc2.conf
build-packages:
- build-essential
- ldc
- llvm-dev
- libconfig++-dev
- libedit-dev
- zlib1g-dev
stage-packages:
- libconfig++-dev
- libphobos2-ldc-dev
  ldc-config:
plugin: dump
source: ldc-config
organize:
  ldc2.conf: etc/ldc2.conf

  gcc:
plugin: nil
stage-packages: [gcc]
organize:
  usr/bin/gcc: usr/bin/gcc.real
  gcc-wrapper:
plugin: dump
source: gcc-wrapper
organize:
  gcc.wrapper: usr/bin/gcc
  libc6:
plugin: nil
stage-packages: [libc6]
  libc6-dev:
plugin: nil
stage-packages: [libc6-dev]

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

Re: Error using custom image

[Sergio Schvezov]

On Wed, 18 Jan 2017 18:42:27 +, Luke Williams wrote:
> Hello,
>
> We are trying to build a custom image with a custom kernel. The 
> kernel build and making the image goes without a hitch, however, 
> when we try to run it in Virtual Box, we get the following 
> error:
>
>
>
> And it fails to load. 
> We have tried an image built with the custom kernel, one built 
> with a yaketty kernel, and one that we just build with all stock 
> pieces. None of them can get past this part.
>
> If we use the image that we download from cdimages, that one 
> works. When we look at the images side by side, we can’t see any 
> differences. 
> Is there anything you recommend we check to see why it cannot 
> see the writable partition?

Without havig touched this in a while have you ensured you have vfat and 
squashfs either built-in or in initramfs?

-- 
Sent using Dekko from my Ubuntu device

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

Re: create-user primitive

[Manik Taneja]

On Wed, Jan 18, 2017 at 4:33 AM, Gustavo Niemeyer 
wrote:

> Don't see a reason to go beyond not listing it. The command works fine,
> including proper help and reasonable error messages.
>
> The reason it prevents creating users when one already exists is so we
> don't see scripts opening back doors by mistake. As Michael points out,
> this may be overriden with --force-managed.
>
> i would suggest that we document this somewhere. the only way i knew about
its existence was the fact that i had seen the primitive in an earlier
version of snapd. for others who are not familiar, this might not even show
up on their radar.

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

Re: Hi

[Manik Taneja]

Sunny,

Can you please mail your request in to .

/Manik

On Tue, Jan 17, 2017 at 10:54 PM, Sunny Bhayani <
sunny.bhay...@einfochips.com> wrote:

> Hi Manik,
>
>
> Thank you for your time.
>
>
> Actually, we have some technical query, related to the ubuntu-image binary
> which builds the ubuntu-os.
>
>
> So is this the right forum ?
>
> If not, then I request you to please connect me to the right person.
>
>
> I have already posted my query on the Rocketchat #snapcraft and #snappy
> channels for the same, but the query is open.
>
>
> Keeping in loop my manager Mr. Ajay Pandey.
>
>
> Thanks & Regards,
> *Sunny Bhayani*
> Solution Consultant | Solutions
> Tel: - | Cell: 919909705699
> Product Engineering Services
> Software | System | Silicon | Mechanical
>
> www.einfochips.com | sunny.bhay...@einfochips.com
> 
> 
> 
> 
> 
> 
> 
> 20 Years of Engineering Innovation & Excellence
> Recognized as 'Leader' in Zinnov's Global Service Providers Rating-2015
>
> --
> *From:* Manik Taneja 
> *Sent:* Wednesday, January 18, 2017 7:12:50 AM
> *To:* Sunny Bhayani
> *Cc:* Prakash Advani
> *Subject:* Hi
>
> Hi Sunny,
>
> Hope this email finds you well. Thanks for reaching out on linkedin. I was
> wondering as to where are you based and if you were connected to Prakash,
> our Dir of Sales India. In any case, please let us know how we can help.
>
> Regards,
> Manik
> 
> 
> * eInfochips Business Disclaimer:
> This e-mail message and all attachments transmitted with it are intended
> solely for the use of the addressee and may contain legally privileged and
> confidential information. If the reader of this message is not the intended
> recipient, or an employee or agent responsible for delivering this message
> to the intended recipient, you are hereby notified that any dissemination,
> distribution, copying, or other use of this message or its attachments is
> strictly prohibited. If you have received this message in error, please
> notify the sender immediately by replying to this message and please delete
> it from your computer. Any views expressed in this message are those of the
> individual sender unless otherwise stated. Company has taken enough
> precautions to prevent the spread of viruses. However the company accepts
> no liability for any damage caused by any virus transmitted by this email.
> 
> 
> *
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: [announce] twistypuzzle snap

[Spencer Parkin]

Thank you for the bug report and the feedback!  I think I know how to fix
that bug.

The .yaml file is here...

https://github.com/spencerparkin/TwistyPuzzle/blob/stable-release/Snap/snapcraft.yaml

Compared to Microsoft's "snapping process," Ubuntu snaps are infinitely
better.  I have actually never successfully gotten through Microsoft's
process.

On Wed, Jan 18, 2017 at 1:52 AM, Jamie Bennett 
wrote:

> 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
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Naming for the Ubuntu Download Manager interface

[Mike Sheldon]

Ah, my mistake. I'd suspect UDM is less likely to change since it's
already a public facing API being used in third party apps. But it
sounds like we don't lose anything if we start it off as unity8-
download-manager whilst bundled with unity8 if we can then add an
additional interface once its distributed in its own snap (although I
guess that snap would have to advertise itself as providing both
interfaces to keep compatibility with existing snaps). 

I'm not sure if we gain much in this particular case though since we'd
need to be maintaining a stable API to work with existing apps
regardless?

On Wed, 2017-01-18 at 14:24 -0200, Gustavo Niemeyer wrote:
> Sorry for not being clear. In addition to the suggestion about
> ubuntu-download-manager, I also wrote this:
> 
> "Note that part of the rationale of having unity8-contacts and
> unity8-calendar named like that was that these interfaces are likely
> to change in meaningful and incompatible ways in the near future. If
> the download manager is going to be bundled with unity8, it may be
> wise to do the same. We can always introduce a more general interface
> later.. not so nice to get out of a general interface that doesn't
> work."
> 
> What's your take on it?
> 
> 
> 
> On Wed, Jan 18, 2017 at 2:15 PM, Mike Sheldon  cal.com> wrote:
> > Sorry, that was my entire point, I guess I should have expanded on
> > it a
> > bit. I agree with ubuntu-download-manager as a name, since that's
> > the
> > name developers will be interacting with if they're using our SDK.
> > For
> > example under QML they're importing Ubuntu.DownloadManager and the
> > C++
> > namespace is Ubuntu::DownloadManager. So the interface being named
> > ubuntu-download-manager seems perfectly natural to me (in fact this
> > was
> > the initial name I proposed for it, before it was suggested that
> > download-manager might be a better name).
> > 
> > On Wed, 2017-01-18 at 13:22 -0200, Gustavo Niemeyer wrote:
> > > The second part of the point was cut out. Can you please at least
> > let
> > > us know how you feel about it, so we can be in sync about the
> > right
> > > decision.
> > >
> > > On Jan 18, 2017 1:02 PM, "Mike Sheldon"  > l.co
> > > m> wrote:
> > > ubuntu-download-manager makes sense as a name to me, especially
> > as
> > > it's
> > > one of the APIs in the Ubuntu SDK.
> > >
> > > On Wed, 2017-01-18 at 12:34 -0200, Gustavo Niemeyer wrote:
> > > >
> > > > The real issue with download-manager is that it's too general.
> > We
> > > all
> > > > have several download managers in our systems, so this gives no
> > > hint
> > > > of what it's really talking about.
> > > >
> > > > We can call it ubuntu-download-manager if that's how the
> > software
> > > was
> > > > named. Note that part of the rationale of having unity8-
> > contacts
> > > and
> > > > unity8-calendar named like that was that these interfaces are
> > > likely
> > > > to change in meaningful and incompatible ways in the near
> > future.
> > > If
> > > > the download manager is going to be bundled with unity8, it may
> > be
> > > > wise to do the same. We can always introduce a more general
> > > interface
> > > > later.. not so nice to get out of a general interface that
> > doesn't
> > > > work.
> > > >
> > > >
> > > >
> > > > On Wed, Jan 18, 2017 at 11:47 AM, Mike Sheldon  > @can
> > > on
> > > > ical.com> wrote:
> > > > > Hi all,
> > > > >
> > > > >  Currently the interface for UDM (Ubuntu Download Manager)
> > has
> > > been
> > > > > named unity8-download-manager. It's my understanding that
> > whilst
> > > we
> > > > > might initially be bundling UDM within the unity8 snap to
> > make
> > > the
> > > > > first stages of development easier (e.g. so it can talk
> > directly
> > > to
> > > > > unity8's transfer indicator), the long term plan would be for
> > it
> > > to
> > > > > be
> > > > > available separately.
> > > > >
> > > > >  Having UDM permanently tied to unity8 would seem to add a
> > strong
> > > > > disincentive for app developers to make use of it at all, as
> > > their
> > > > > apps
> > > > > would then no-longer be portable across different desktop
> > > > > environments.
> > > > >
> > > > >  As such, I'm wondering if the naming of this interface is
> > > perhaps
> > > > > misleading?
> > > > >
> > > > > Thanks,
> > > > >  Mike
> > > > >
> > > > > --
> > > > > Snapcraft mailing list
> > > > > Snapcraft@lists.snapcraft.io
> > > > > Modify settings or unsubscribe at: https://lists.ubuntu.com/m
> > ailm
> > > an
> > > > > /listinfo/snapcraft
> > > > >
> > > >
> > > >
> > > > -- 
> > > >
> > > > gustavo @ http://niemeyer.net
> > > > -- 
> > > > Snapcraft mailing list
> > > > Snapcraft@lists.snapcraft.io
> > > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mai
> > lman
> > > /l
> > > > istinfo/snapcraft
> > >
> > > --
> > > Snapcraft mailing list
> > > Snapcraft@lists.snapcraft.io
> > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> > an/l
> > > istinfo/snapcraft
> > >
> >

Re: Naming for the Ubuntu Download Manager interface

[Gustavo Niemeyer]

Sorry for not being clear. In addition to the suggestion about
ubuntu-download-manager, I also wrote this:

"Note that part of the rationale of having unity8-contacts and
unity8-calendar named like that was that these interfaces are likely to
change in meaningful and incompatible ways in the near future. If the
download manager is going to be bundled with unity8, it may be wise to do
the same. We can always introduce a more general interface later.. not so
nice to get out of a general interface that doesn't work."

What's your take on it?



On Wed, Jan 18, 2017 at 2:15 PM, Mike Sheldon  wrote:

> Sorry, that was my entire point, I guess I should have expanded on it a
> bit. I agree with ubuntu-download-manager as a name, since that's the
> name developers will be interacting with if they're using our SDK. For
> example under QML they're importing Ubuntu.DownloadManager and the C++
> namespace is Ubuntu::DownloadManager. So the interface being named
> ubuntu-download-manager seems perfectly natural to me (in fact this was
> the initial name I proposed for it, before it was suggested that
> download-manager might be a better name).
>
> On Wed, 2017-01-18 at 13:22 -0200, Gustavo Niemeyer wrote:
> > The second part of the point was cut out. Can you please at least let
> > us know how you feel about it, so we can be in sync about the right
> > decision.
> >
> > On Jan 18, 2017 1:02 PM, "Mike Sheldon"  > m> wrote:
> > ubuntu-download-manager makes sense as a name to me, especially as
> > it's
> > one of the APIs in the Ubuntu SDK.
> >
> > On Wed, 2017-01-18 at 12:34 -0200, Gustavo Niemeyer wrote:
> > >
> > > The real issue with download-manager is that it's too general. We
> > all
> > > have several download managers in our systems, so this gives no
> > hint
> > > of what it's really talking about.
> > >
> > > We can call it ubuntu-download-manager if that's how the software
> > was
> > > named. Note that part of the rationale of having unity8-contacts
> > and
> > > unity8-calendar named like that was that these interfaces are
> > likely
> > > to change in meaningful and incompatible ways in the near future.
> > If
> > > the download manager is going to be bundled with unity8, it may be
> > > wise to do the same. We can always introduce a more general
> > interface
> > > later.. not so nice to get out of a general interface that doesn't
> > > work.
> > >
> > >
> > >
> > > On Wed, Jan 18, 2017 at 11:47 AM, Mike Sheldon  > on
> > > ical.com> wrote:
> > > > Hi all,
> > > >
> > > >  Currently the interface for UDM (Ubuntu Download Manager) has
> > been
> > > > named unity8-download-manager. It's my understanding that whilst
> > we
> > > > might initially be bundling UDM within the unity8 snap to make
> > the
> > > > first stages of development easier (e.g. so it can talk directly
> > to
> > > > unity8's transfer indicator), the long term plan would be for it
> > to
> > > > be
> > > > available separately.
> > > >
> > > >  Having UDM permanently tied to unity8 would seem to add a strong
> > > > disincentive for app developers to make use of it at all, as
> > their
> > > > apps
> > > > would then no-longer be portable across different desktop
> > > > environments.
> > > >
> > > >  As such, I'm wondering if the naming of this interface is
> > perhaps
> > > > misleading?
> > > >
> > > > Thanks,
> > > >  Mike
> > > >
> > > > --
> > > > Snapcraft mailing list
> > > > Snapcraft@lists.snapcraft.io
> > > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> > an
> > > > /listinfo/snapcraft
> > > >
> > >
> > >
> > > --
> > >
> > > gustavo @ http://niemeyer.net
> > > --
> > > Snapcraft mailing list
> > > Snapcraft@lists.snapcraft.io
> > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman
> > /l
> > > istinfo/snapcraft
> >
> > --
> > Snapcraft mailing list
> > Snapcraft@lists.snapcraft.io
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/l
> > istinfo/snapcraft
> >
> > --
> > Snapcraft mailing list
> > Snapcraft@lists.snapcraft.io
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/l
> > istinfo/snapcraft
>
> --
> 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: Naming for the Ubuntu Download Manager interface

[Mike Sheldon]

Sorry, that was my entire point, I guess I should have expanded on it a
bit. I agree with ubuntu-download-manager as a name, since that's the
name developers will be interacting with if they're using our SDK. For
example under QML they're importing Ubuntu.DownloadManager and the C++
namespace is Ubuntu::DownloadManager. So the interface being named
ubuntu-download-manager seems perfectly natural to me (in fact this was
the initial name I proposed for it, before it was suggested that
download-manager might be a better name).

On Wed, 2017-01-18 at 13:22 -0200, Gustavo Niemeyer wrote:
> The second part of the point was cut out. Can you please at least let
> us know how you feel about it, so we can be in sync about the right
> decision.
> 
> On Jan 18, 2017 1:02 PM, "Mike Sheldon"  m> wrote:
> ubuntu-download-manager makes sense as a name to me, especially as
> it's
> one of the APIs in the Ubuntu SDK.
> 
> On Wed, 2017-01-18 at 12:34 -0200, Gustavo Niemeyer wrote:
> >
> > The real issue with download-manager is that it's too general. We
> all
> > have several download managers in our systems, so this gives no
> hint
> > of what it's really talking about.
> >
> > We can call it ubuntu-download-manager if that's how the software
> was
> > named. Note that part of the rationale of having unity8-contacts
> and
> > unity8-calendar named like that was that these interfaces are
> likely
> > to change in meaningful and incompatible ways in the near future.
> If
> > the download manager is going to be bundled with unity8, it may be
> > wise to do the same. We can always introduce a more general
> interface
> > later.. not so nice to get out of a general interface that doesn't
> > work.
> >
> >
> >
> > On Wed, Jan 18, 2017 at 11:47 AM, Mike Sheldon  on
> > ical.com> wrote:
> > > Hi all,
> > >
> > >  Currently the interface for UDM (Ubuntu Download Manager) has
> been
> > > named unity8-download-manager. It's my understanding that whilst
> we
> > > might initially be bundling UDM within the unity8 snap to make
> the
> > > first stages of development easier (e.g. so it can talk directly
> to
> > > unity8's transfer indicator), the long term plan would be for it
> to
> > > be
> > > available separately.
> > >
> > >  Having UDM permanently tied to unity8 would seem to add a strong
> > > disincentive for app developers to make use of it at all, as
> their
> > > apps
> > > would then no-longer be portable across different desktop
> > > environments.
> > >
> > >  As such, I'm wondering if the naming of this interface is
> perhaps
> > > misleading?
> > >
> > > Thanks,
> > >  Mike
> > >
> > > --
> > > Snapcraft mailing list
> > > Snapcraft@lists.snapcraft.io
> > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an
> > > /listinfo/snapcraft
> > >
> >
> >
> > -- 
> >
> > gustavo @ http://niemeyer.net
> > -- 
> > Snapcraft mailing list
> > Snapcraft@lists.snapcraft.io
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman
> /l
> > istinfo/snapcraft
> 
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/l
> istinfo/snapcraft
> 
> -- 
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/l
> istinfo/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

[Dave Morley]

On Wed, 18 Jan 2017 10:47:27 -0500
Mark Shuttleworth  wrote:

> On 18/01/17 06:41, Dave Morley wrote:
> > Not so happy on 14.04 paste.ubuntu.com/23821653/ I get a
> > segfault :(   
> 
> Can you report a bug and include 'snap --version' please?
> 
> Thank you!
> Mark
> 

Done
https://bugs.launchpad.net/ubuntu/+source/asciinema/+bug/1657504

-- 
You Make It, I'll Break It!

I Love My Job :)

http://www.canonical.com
http://www.ubuntu.com


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

Pi2 and 3 image improvements (GLES, GPIO)

[Oliver Grawert]

hi,

at [1] you can now find a daily image build for the Pi2 and Pi3 that
both have full GLES support and all 26 GPIOs exposed through
interfaces, some test feedback would be nice :)

the GPIO numbering and pin mapping follows the community map at [2] and
looks like [3] in the "snap interfaces" output now.

ciao
oli

[1] http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/
[2] http://pinout.xyz/#
[3] http://paste.ubuntu.com/23822613/

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: Please test my asciinema snap

[Mark Shuttleworth]

On 18/01/17 06:41, Dave Morley wrote:
> Not so happy on 14.04 paste.ubuntu.com/23821653/ I get a segfault :( 

Can you report a bug and include 'snap --version' please?

Thank you!
Mark



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: Naming for the Ubuntu Download Manager interface

[Gustavo Niemeyer]

The second part of the point was cut out. Can you please at least let us
know how you feel about it, so we can be in sync about the right decision.

On Jan 18, 2017 1:02 PM, "Mike Sheldon" 
wrote:

ubuntu-download-manager makes sense as a name to me, especially as it's
one of the APIs in the Ubuntu SDK.

On Wed, 2017-01-18 at 12:34 -0200, Gustavo Niemeyer wrote:
>
> The real issue with download-manager is that it's too general. We all
> have several download managers in our systems, so this gives no hint
> of what it's really talking about.
>
> We can call it ubuntu-download-manager if that's how the software was
> named. Note that part of the rationale of having unity8-contacts and
> unity8-calendar named like that was that these interfaces are likely
> to change in meaningful and incompatible ways in the near future. If
> the download manager is going to be bundled with unity8, it may be
> wise to do the same. We can always introduce a more general interface
> later.. not so nice to get out of a general interface that doesn't
> work.
>
>
>
> On Wed, Jan 18, 2017 at 11:47 AM, Mike Sheldon  ical.com> wrote:
> > Hi all,
> >
> >  Currently the interface for UDM (Ubuntu Download Manager) has been
> > named unity8-download-manager. It's my understanding that whilst we
> > might initially be bundling UDM within the unity8 snap to make the
> > first stages of development easier (e.g. so it can talk directly to
> > unity8's transfer indicator), the long term plan would be for it to
> > be
> > available separately.
> >
> >  Having UDM permanently tied to unity8 would seem to add a strong
> > disincentive for app developers to make use of it at all, as their
> > apps
> > would then no-longer be portable across different desktop
> > environments.
> >
> >  As such, I'm wondering if the naming of this interface is perhaps
> > misleading?
> >
> > Thanks,
> >  Mike
> >
> > --
> > 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/l
> istinfo/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

Re: Naming for the Ubuntu Download Manager interface

[Dave Morley]

On Wed, 18 Jan 2017 15:01:34 +
Mike Sheldon  wrote:

> ubuntu-download-manager makes sense as a name to me, especially as
> it's one of the APIs in the Ubuntu SDK.
> 
> On Wed, 2017-01-18 at 12:34 -0200, Gustavo Niemeyer wrote:
> > 
> > The real issue with download-manager is that it's too general. We
> > all have several download managers in our systems, so this gives no
> > hint of what it's really talking about.
> > 
> > We can call it ubuntu-download-manager if that's how the software
> > was named. Note that part of the rationale of having
> > unity8-contacts and unity8-calendar named like that was that these
> > interfaces are likely to change in meaningful and incompatible ways
> > in the near future. If the download manager is going to be bundled
> > with unity8, it may be wise to do the same. We can always introduce
> > a more general interface later.. not so nice to get out of a
> > general interface that doesn't work.
> > 
> > 
> > 
> > On Wed, Jan 18, 2017 at 11:47 AM, Mike Sheldon
> >  wrote:
> > > Hi all,
> > > 
> > >  Currently the interface for UDM (Ubuntu Download Manager) has
> > > been named unity8-download-manager. It's my understanding that
> > > whilst we might initially be bundling UDM within the unity8 snap
> > > to make the first stages of development easier (e.g. so it can
> > > talk directly to unity8's transfer indicator), the long term plan
> > > would be for it to be
> > > available separately.
> > > 
> > >  Having UDM permanently tied to unity8 would seem to add a strong
> > > disincentive for app developers to make use of it at all, as their
> > > apps
> > > would then no-longer be portable across different desktop
> > > environments.
> > > 
> > >  As such, I'm wondering if the naming of this interface is perhaps
> > > misleading?
> > > 
> > > Thanks,
> > >  Mike
> > > 
> > > --
> > > 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/l istinfo/snapcraft  
> 

Go down the ufw Route and just call it uncomplicated download manager
then it isn't restricted to Ubuntu as a distro or a desktop variant

-- 
You Make It, I'll Break It!

I Love My Job :)

http://www.canonical.com
http://www.ubuntu.com


pgpKUrEIiaBut.pgp
Description: OpenPGP digital signature
-- 
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

[Dave Morley]

On Wed, 18 Jan 2017 14:43:30 +
Dan Watkins  wrote:

> On 18/01/17 14:38, Dave Morley wrote:
> > https://asciinema.org/a/c7ohu56eupwnq6noyua2k0eum  
> 
> https://asciinema.org/a/3ymbowr1pk6usww8v1iyveai9
> 

https://asciinema.org/a/0o2pajjotf3k9fnv80btm26qx

-- 
You Make It, I'll Break It!

I Love My Job :)

http://www.canonical.com
http://www.ubuntu.com


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

Re: Naming for the Ubuntu Download Manager interface

[Mike Sheldon]

ubuntu-download-manager makes sense as a name to me, especially as it's
one of the APIs in the Ubuntu SDK.

On Wed, 2017-01-18 at 12:34 -0200, Gustavo Niemeyer wrote:
> 
> The real issue with download-manager is that it's too general. We all
> have several download managers in our systems, so this gives no hint
> of what it's really talking about.
> 
> We can call it ubuntu-download-manager if that's how the software was
> named. Note that part of the rationale of having unity8-contacts and
> unity8-calendar named like that was that these interfaces are likely
> to change in meaningful and incompatible ways in the near future. If
> the download manager is going to be bundled with unity8, it may be
> wise to do the same. We can always introduce a more general interface
> later.. not so nice to get out of a general interface that doesn't
> work.
> 
> 
> 
> On Wed, Jan 18, 2017 at 11:47 AM, Mike Sheldon  ical.com> wrote:
> > Hi all,
> > 
> >  Currently the interface for UDM (Ubuntu Download Manager) has been
> > named unity8-download-manager. It's my understanding that whilst we
> > might initially be bundling UDM within the unity8 snap to make the
> > first stages of development easier (e.g. so it can talk directly to
> > unity8's transfer indicator), the long term plan would be for it to
> > be
> > available separately.
> > 
> >  Having UDM permanently tied to unity8 would seem to add a strong
> > disincentive for app developers to make use of it at all, as their
> > apps
> > would then no-longer be portable across different desktop
> > environments.
> > 
> >  As such, I'm wondering if the naming of this interface is perhaps
> > misleading?
> > 
> > Thanks,
> >  Mike
> > 
> > --
> > 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/l
> istinfo/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

[Dan Watkins]

On 18/01/17 14:38, Dave Morley wrote:
> https://asciinema.org/a/c7ohu56eupwnq6noyua2k0eum

https://asciinema.org/a/3ymbowr1pk6usww8v1iyveai9



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: Please test my asciinema snap

[Dave Morley]

On Wed, 18 Jan 2017 06:34:26 -0500
Mark Shuttleworth  wrote:

> On 18/01/17 06:12, Sergio Schvezov wrote:
> > On Wed, 18 Jan 2017 10:40:47 +, Jamie Bennett wrote:  
> >> 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.  
> > Working fine for me as well!  
> 
> 
> Thank you. Loving this :)
> 
> Mark
> 
> 

https://asciinema.org/a/c7ohu56eupwnq6noyua2k0eum

-- 
You Make It, I'll Break It!

I Love My Job :)

http://www.canonical.com
http://www.ubuntu.com


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

Re: Naming for the Ubuntu Download Manager interface

[Gustavo Niemeyer]

The real issue with download-manager is that it's too general. We all have
several download managers in our systems, so this gives no hint of what
it's really talking about.

We can call it ubuntu-download-manager if that's how the software was
named. Note that part of the rationale of having unity8-contacts and
unity8-calendar named like that was that these interfaces are likely to
change in meaningful and incompatible ways in the near future. If the
download manager is going to be bundled with unity8, it may be wise to do
the same. We can always introduce a more general interface later.. not so
nice to get out of a general interface that doesn't work.



On Wed, Jan 18, 2017 at 11:47 AM, Mike Sheldon <
michael.shel...@canonical.com> wrote:

> Hi all,
>
>  Currently the interface for UDM (Ubuntu Download Manager) has been
> named unity8-download-manager. It's my understanding that whilst we
> might initially be bundling UDM within the unity8 snap to make the
> first stages of development easier (e.g. so it can talk directly to
> unity8's transfer indicator), the long term plan would be for it to be
> available separately.
>
>  Having UDM permanently tied to unity8 would seem to add a strong
> disincentive for app developers to make use of it at all, as their apps
> would then no-longer be portable across different desktop environments.
>
>  As such, I'm wondering if the naming of this interface is perhaps
> misleading?
>
> Thanks,
>  Mike
>
> --
> 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

Naming for the Ubuntu Download Manager interface

[Mike Sheldon]

Hi all,

 Currently the interface for UDM (Ubuntu Download Manager) has been
named unity8-download-manager. It's my understanding that whilst we
might initially be bundling UDM within the unity8 snap to make the
first stages of development easier (e.g. so it can talk directly to
unity8's transfer indicator), the long term plan would be for it to be
available separately.

 Having UDM permanently tied to unity8 would seem to add a strong
disincentive for app developers to make use of it at all, as their apps
would then no-longer be portable across different desktop environments.

 As such, I'm wondering if the naming of this interface is perhaps
misleading?

Thanks,
 Mike

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

[Sergio Schvezov]

On Wed, 18 Jan 2017 11:41:49 +, Dave Morley wrote:
> On Wed, 18 Jan 2017 04:16:45 -0500
> Mark Shuttleworth  wrote:
>
>> Hi folks
>> 
>> (For those of you who Gmail does not filter this email on
>> as-yet-unexplained-grounds :))
>> 
>> Please could you test my asciinema snap? Asciinema is a console video
>> recording utility that's great for CLI-diven demos. If you want to
>> make a quick web video of a CLI / console journey, asciinema is the
>> ticket.
>> 
>> An older version (0.9.8) is in 16.04. The new 1.3.0 version is now a
>> snap, and it should work on 16.04. I am also interested in feedback on
>> 14.04 for those of you on Trusty steeds who are blazing the
>> snaps-on-trusty trail.
>> 
>> 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.
>> 
> Not so happy on 14.04 paste.ubuntu.com/23821653/ I get a segfault :(

Looking at the snap itself, I see it is python3 and using the in-core python3 
which leads to

$ readelf -a /snap/core/current/usr/bin/python3 |grep INTERP -A2
  INTERP 0x0238 0x00400238 0x00400238
 0x001c 0x001c  R  1
  [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]

`stage-packages` that provide runnables will also have this problem; the 
solution is to use a python3 part (Zygmunt is working on some python parts, he 
started with python0 though).

/brainstorming-mode on
It would be interesting to bring back the snapcraft concept of `provides` which 
has plugin specific meaning, here's an example (made up sources):

parts:
python3:
source: https://python.org/python3.tar.gz
plugin: autotools
provides: [python3]
environment:
PYTHONUSERBASE: ...
PYTHONHOME: ...
asciinema:
source: https://sourceforge.org/asciinema.tar.gz
plugin: python
after: [python3]

How will this work, in the general scenario, the `python` plugin will just use 
its built in logic to obtain python3 (which is through use of `stage-packages`) 
but given that the part comes `after` the `python3` part and that `python3` 
part provides `python3` the plugin will no fetch python3 and use the defined 
`environment` to work it out.

Then again, this might be all to complex and a custom plugin that overrides the 
`python` plugin's `pull` step might be an easier concept. But here is another 
option:

parts:
python3:
source: https://python.org/python3.tar.gz
plugin: autotools
asciinema:
source: https://sourceforge.org/asciinema.tar.gz
plugin: python
environment:
PYTHONUSERBASE: $SNAPCRAFT_STAGE
after: [python3]
stage:
- -$python3-runtime  # defined in filesets
filesets:
python-runtime: [  ]

Other ideas anyone?

-- 
Sent using Dekko from my Ubuntu device

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

Re: create-user primitive

[Gustavo Niemeyer]

Don't see a reason to go beyond not listing it. The command works fine,
including proper help and reasonable error messages.

The reason it prevents creating users when one already exists is so we
don't see scripts opening back doors by mistake. As Michael points out,
this may be overriden with --force-managed.




On Wed, Jan 18, 2017 at 6:10 AM, Evan Dandrea 
wrote:

> On Tue, 17 Jan 2017 at 23:31 Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
>
>> Well snap create-user is mostly there exactly so that console-conf can
>> invoke it. That's also why it's hidden from snap help!
>>
>
> If it's mostly not intended to be used by humans, would it be reasonable
> to have it print a warning?
>
> --
> 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: Serial Port Plug/Interface issue with Ubuntu-core 16.04 (#2557)

[Oliver Grawert]

hi,
Am Mittwoch, den 18.01.2017, 13:26 +0100 schrieb Simon Fels:
> 
> $ snap download pi3
> $ unsquashfs pi3_*.snap
> # Do any modifications to squashfs-root/meta/snap.yaml
> $ snapcraft snap squashfs-root
> # Now you have a new .snap file snapcraft generated for you
> $ ubuntu-image ... --extra-snaps my-gadget.snap ... my-model.assert
> 
better do:

$ git clone https://github.com/snapcore/pi3-gadget
$ cd pi3-gadget

# make your changes in snapcraft.yaml to add the slots you need

then just run:

$ snapcraft

# .. and use ubuntu-image as described above ...

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: Serial Port Plug/Interface issue with Ubuntu-core 16.04 (#2557)

[Simon Fels]

The gadget snap itself is pretty well explained on
https://docs.ubuntu.com/core/en/guides/build-device/gadget which also links
to the official supported gadget snaps you can use for your experiements.

The slot definition can then be added to one of these as explained above.

Another option is that you download one of these gadget snaps from the
store via the snap download command, modify it and then repack it and
generate a new image via ubuntu-image out of it:

$ snap download pi3
$ unsquashfs pi3_*.snap
# Do any modifications to squashfs-root/meta/snap.yaml
$ snapcraft snap squashfs-root
# Now you have a new .snap file snapcraft generated for you
$ ubuntu-image ... --extra-snaps my-gadget.snap ... my-model.assert

Hope that helps.

regards,
Simon


On Tue, Jan 17, 2017 at 10:06 PM, Mritunjai Singh  wrote:

> Can anyone please guide me how to start writing gadget snap which gives me
> access to serial port interface on my Raspberry Pi board and x86_64 ubuntu
> machine.
>
>
>
> Regards,
>
> Mritunjai
>
>
>
> *From:* Mritunjai Singh
> *Sent:* Thursday, January 12, 2017 10:06 AM
> *To:* 'Snapcraft' 
> *Subject:* RE: Serial Port Plug/Interface issue with Ubuntu-core 16.04
> (#2557)
>
>
>
> *@Simon Fels*, thanks for the pointer. It would be great if you can
> further guide me writing the gadget snap. I have a Ubuntu x86_64
> machine(VM) to which I will be connecting our RF Mesh network card through
> USB. The network card connects over serial and exposes a /dev/ttys0 port to
> work with. So do I need to write gadget snap for my network card or for my
> Ubuntu machine on which I have already installed snapcraft.
>
>
>
> Please guide and do let me know should you require any further information.
>
>
>
> Regards,
>
> Mritunjai
>
>
>
> *From:* snapcraft-boun...@lists.snapcraft.io [mailto:snapcraft-bounces@
> lists.snapcraft.io ] *On Behalf Of 
> *Simon
> Fels
> *Sent:* Thursday, January 12, 2017 12:58 AM
> *To:* Snapcraft 
> *Subject:* Re: Serial Port Plug/Interface issue with Ubuntu-core 16.04
> (#2557)
>
>
>
> You can add a serial port slot to a gadget snap.yaml like this:
>
>
>
> ttyS4:
>
>   interface: serial-port
>
>   path: /dev/ttyS4
>
>
>
> This only applies to static serial port nodes. If you have one provided by
> an USB device you have to user a slightly different slot definition which
> refers the USB product/vendor id of your USB device:
>
>
>
> my-usb-serial:
>
>   interface: serial-port
>
>   usb-product: 0x
>
>   usb-vendor: 0x
>
>   path: /dev/my-usb-serial-port
>
>
>
> With the path attribute you can select a static path for the serial port
> node which your snap then gets access to once you connected the plug and
> the slot. The path needs to start with /dev/ and afterwards you're free to
> select a free node name. Internally the interface implementation will link
> the right /dev/ttyUSB* node to the specified path.
>
>
>
> Please note that you can define such a slot only on a gadget snap! So if
> you don't have your own gadget snap today, you need to create one for your
> device in order to get access to the serial port.
>
>
>
> I hope that helps.
>
>
>
> regards,
>
> Simon
>
>
>
>
>
> On Wed, Jan 11, 2017 at 7:37 PM, Oliver Grawert  wrote:
>
> hi,
> Am Mittwoch, den 11.01.2017, 17:59 + schrieb 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.
>
> note that all our gadgets offer a console on serial by default, if you
> drive some external device via serial you might want to drop this
> console tty option.
>
> all our official gadgets are under https://github.com/snapcore/ ..
> namely the pi2-gadget, pi3-gadget, pc-gadget and dragonboard-gadget
> sub-trees if you want to take a look ...
>
> 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
>
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Classic confinement and core_dynamic_linker

[Sergio Schvezov]

On Wed, 18 Jan 2017 08:58:00 -0200, Gustavo Niemeyer wrote:
> Hi Sergio,
>
> The question asked was actually how to get snapcraft to include
> dependencies *inside the snap* so that it works as it does with strict
> snaps, bundling the dependencies.

The recomended way to add a library to your snap is to either build/stage it 
through a part or to add a stage-packages entry with the package that would 
include the needed library.

-- 
Sent using Dekko from my Ubuntu device

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

Re: Classic confinement and core_dynamic_linker

[Sergio Schvezov]

On Tue, 17 Jan 2017 23:17:27 +0100, Joseph Rushton Wakeling wrote:
> On 17/01/17 22:22, Sergio Schvezov wrote:
> >
>  
>
> Is that a work in progress constraint, or is it the intended long term 
> behaviour?  (I'll try it out shortly in any case.)
>
> I ask because currently, if a package is explicitly stated as a build 
> dependency, then with `strict` confinement it's automatically 
> included in the 
> final snap where necessary.  What makes `classic` confinement unable to 
> automatically handle the inclusion of build dependencies in the same way?

After a quick but thorough conversation with Gustavo we agreed that this is the 
wrong path to take as it might not be deterministic or people might get 
surprised about things included that shouldn't have been.

There needs to be a clear line between `build-packages` and `stage-packages`. 
With that in mind snapcraft (even for `strict` snaps) will still crawl all the 
libraries and error on missing ones with a list of those that are missing. This 
should be something one can disable and set to ignore as some of the missing 
libraries might be provided by a content interface slot from another snap.

-- 
Sent using Dekko from my Ubuntu device

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

[Dave Morley]

On Wed, 18 Jan 2017 04:16:45 -0500
Mark Shuttleworth  wrote:

> Hi folks
> 
> (For those of you who Gmail does not filter this email on
> as-yet-unexplained-grounds :))
> 
> Please could you test my asciinema snap? Asciinema is a console video
> recording utility that's great for CLI-diven demos. If you want to
> make a quick web video of a CLI / console journey, asciinema is the
> ticket.
> 
> An older version (0.9.8) is in 16.04. The new 1.3.0 version is now a
> snap, and it should work on 16.04. I am also interested in feedback on
> 14.04 for those of you on Trusty steeds who are blazing the
> snaps-on-trusty trail.
> 
> 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.
> 
> Thanks!
> 
> Mark
> 
> 
> 
> 

Not so happy on 14.04 paste.ubuntu.com/23821653/ I get a segfault :(

-- 
You Make It, I'll Break It!

I Love My Job :)

http://www.canonical.com
http://www.ubuntu.com


pgp30nSQFPsc9.pgp
Description: OpenPGP digital signature
-- 
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

[Mark Shuttleworth]

On 18/01/17 06:12, Sergio Schvezov wrote:
> On Wed, 18 Jan 2017 10:40:47 +, Jamie Bennett wrote:
>> 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.
> Working fine for me as well!


Thank you. Loving this :)

Mark


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

[Sergio Schvezov]

On Wed, 18 Jan 2017 10:40:47 +, Jamie Bennett wrote:
> 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.

Working fine for me as well!

-- 
Sent using Dekko from my Ubuntu device

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

Re: Classic confinement and core_dynamic_linker

[Sergio Schvezov]

On Wed, 18 Jan 2017 08:58:00 -0200, Gustavo Niemeyer wrote:
> Hi Sergio,
>
> The question asked was actually how to get snapcraft to include
> dependencies *inside the snap* so that it works as it does with strict
> snaps, bundling the dependencies.
>
> Your response was about system libraries rather than bundled
> in-snap libraries, I believe.
>
> This should definitely work fine, right?

Yes, there is a gotcha though wrt the question asked. Using `build-packages`, 
which install on the host -the usual `-dev` ones- means that the libraries they 
bring in need to be added as `stage-packages`. We added an optimization here 
where we crawl all elf files in `prime` and `ldd` them to see if anything would 
resolve outside the snap and bring those libraries in. This is not as easy with 
classic confinement as all those elf files are runpathed. I have slept on it 
though and think there is a way to do it, but it won't be as straightforward.

-- 
Sent using Dekko from my Ubuntu device

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

Re: Classic confinement and core_dynamic_linker

[Gustavo Niemeyer]

Hi Sergio,

The question asked was actually how to get snapcraft to include
dependencies *inside the snap* so that it works as it does with strict
snaps, bundling the dependencies.

Your response was about system libraries rather than bundled
in-snap libraries, I believe.

This should definitely work fine, right?



On Tue, Jan 17, 2017 at 11:21 PM, Sergio Schvezov <
sergio.schve...@canonical.com> wrote:

> On Tue, 17 Jan 2017 23:17:27 +0100, Joseph Rushton Wakeling wrote:
> > On 17/01/17 22:22, Sergio Schvezov wrote:
> 
> 
> >
> >
> > Is that a work in progress constraint, or is it the intended long term
> > behaviour?  (I'll try it out shortly in any case.)
> >
> > I ask because currently, if a package is explicitly stated as a build
> > dependency, then with `strict` confinement it's automatically
> > included in the
> > final snap where necessary.  What makes `classic` confinement unable to
> > automatically handle the inclusion of build dependencies in the same way?
>
> The logic is still run, but the resulting binary in classic uses rpath and
> no dynamic loading so there is no resolution to a on-system library we can
> pick up. I guess we can do some magic, but it feels it might be either
> fragile or make the build process a lot slower. We will need to look into
> it, but not short term.
>
> --
> Sent using Dekko from my Ubuntu device
>
> --
> 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: Serial Port Plug/Interface issue with Ubuntu-core 16.04 (#2557)

[Mritunjai Singh]

Can anyone please guide me how to start writing gadget snap which gives me 
access to serial port interface on my Raspberry Pi board and x86_64 ubuntu 
machine.

Regards,
Mritunjai

From: Mritunjai Singh
Sent: Thursday, January 12, 2017 10:06 AM
To: 'Snapcraft' 
Subject: RE: Serial Port Plug/Interface issue with Ubuntu-core 16.04 (#2557)

@Simon Fels, thanks for the pointer. It would be great if you can further guide 
me writing the gadget snap. I have a Ubuntu x86_64 machine(VM) to which I will 
be connecting our RF Mesh network card through USB. The network card connects 
over serial and exposes a /dev/ttys0 port to work with. So do I need to write 
gadget snap for my network card or for my Ubuntu machine on which I have 
already installed snapcraft.

Please guide and do let me know should you require any further information.

Regards,
Mritunjai

From: 
snapcraft-boun...@lists.snapcraft.io
 [mailto:snapcraft-boun...@lists.snapcraft.io] On Behalf Of Simon Fels
Sent: Thursday, January 12, 2017 12:58 AM
To: Snapcraft 
mailto:snapcraft@lists.snapcraft.io>>
Subject: Re: Serial Port Plug/Interface issue with Ubuntu-core 16.04 (#2557)

You can add a serial port slot to a gadget snap.yaml like this:

ttyS4:
  interface: serial-port
  path: /dev/ttyS4

This only applies to static serial port nodes. If you have one provided by an 
USB device you have to user a slightly different slot definition which refers 
the USB product/vendor id of your USB device:

my-usb-serial:
  interface: serial-port
  usb-product: 0x
  usb-vendor: 0x
  path: /dev/my-usb-serial-port

With the path attribute you can select a static path for the serial port node 
which your snap then gets access to once you connected the plug and the slot. 
The path needs to start with /dev/ and afterwards you're free to select a free 
node name. Internally the interface implementation will link the right 
/dev/ttyUSB* node to the specified path.

Please note that you can define such a slot only on a gadget snap! So if you 
don't have your own gadget snap today, you need to create one for your device 
in order to get access to the serial port.

I hope that helps.

regards,
Simon


On Wed, Jan 11, 2017 at 7:37 PM, Oliver Grawert 
mailto:o...@ubuntu.com>> wrote:
hi,
Am Mittwoch, den 11.01.2017, 17:59 + schrieb 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.

note that all our gadgets offer a console on serial by default, if you
drive some external device via serial you might want to drop this
console tty option.

all our official gadgets are under https://github.com/snapcore/ ..
namely the pi2-gadget, pi3-gadget, pc-gadget and dragonboard-gadget
sub-trees if you want to take a look ...

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: 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: ubuntu core + snap + gpios

[Oliver Grawert]

hi,
Am Dienstag, den 17.01.2017, 23:31 + schrieb Luís Martins:
> Hi, I was trying to build a simple snap to test the ubuntu core
> raspberry pi 3 gpios [1] but for some reason the app does not seem
> allowed to write into /sys/class/gpio/ within my snap.
> 
> I declared the "plugs: [gpio]" in the snapcraft.yaml and the app is a
> simple qt5/c++ program using std::ifstream/std::ofstream to
> read/write to the files.
> 
> However, using the latest stable ubuntu core image, the "snap
> interfaces" command does not list the "gpio" as an available
> interface, is this normal ?
> 
no, this is a bug, i have something nearly ready and can land it later
today in the edge channel, i'll notify the list once it is there and
also trigger a rebuild of the daily images (so you dont need to roll
your own image)

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: Please test my asciinema snap

[Mark Shuttleworth]

... you may also need to enable xenial-proposed main in
/etc/apt/sources.list to make sure you have the very latest snapd.

Mark

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

Please test my asciinema snap

[Mark Shuttleworth]

Hi folks

(For those of you who Gmail does not filter this email on
as-yet-unexplained-grounds :))

Please could you test my asciinema snap? Asciinema is a console video
recording utility that's great for CLI-diven demos. If you want to make
a quick web video of a CLI / console journey, asciinema is the ticket.

An older version (0.9.8) is in 16.04. The new 1.3.0 version is now a
snap, and it should work on 16.04. I am also interested in feedback on
14.04 for those of you on Trusty steeds who are blazing the
snaps-on-trusty trail.

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.

Thanks!

Mark




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

Re: Yet more issues snapping

[gareth . france]

On 2017-01-18 08:41, Evan Dandrea wrote:

On Tue, 17 Jan 2017 at 02:08 Gareth France
 wrote:

On 16/01/17 23:58, Loïc Minier wrote:
I suggest you try running your Travis build inside a 16.04
environment; it seems this is achieved by running the 16.04 Docker
container.
Thank you, but how do I do that?

This will guide you through it:
http://snapcraft.io/docs/build-snaps/ci-integration [1]

If you run into any problems, please do let me know. 


Links:
--
[1] http://snapcraft.io/docs/build-snaps/ci-integration


It is ok now thank you. I have had some excellent help and can use what 
I now have to aid me going forward. It is those first few steps that 
seem impossible.


--
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: Yet more issues snapping

[Evan Dandrea]

On Tue, 17 Jan 2017 at 02:08 Gareth France 
wrote:

>
> On 16/01/17 23:58, Loïc Minier wrote:
> > I suggest you try running your Travis build inside a 16.04
> > environment; it seems this is achieved by running the 16.04 Docker
> > container.
> Thank you, but how do I do that?
>

This will guide you through it:
http://snapcraft.io/docs/build-snaps/ci-integration

If you run into any problems, please do let me know.
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft