Hello all,
We're almost done integrating the traditional snapcraft mailing list and
the forum.
You may still use it via email if that's your preference. For details
please see this topic:
https://forum.snapcraft.io/t/integration-of-snapcraft-mailing-list/330
--
gustavo @
Yes, I'd suggest following that thread and waiting just a little bit.
We're hoping to get these changes landed as soon as snapd 2.25.
On Mon, Apr 10, 2017 at 11:33 AM, Kyle Fazzari
wrote:
>
>
> On 04/10/2017 06:57 AM, Daniel Manrique wrote:
> > On Mon, Apr 10, 2017
Sounds sane.
Bret, Natalia, who's the best person to handle such requests after
approval? I know Jamie can edit the declarations, so he could easily do
it, but that's not entirely security related. Should we just abuse ask
whether Jamie would mind to handle those requests for now or is there a
Hi Jenny,
Yes, what you want to do is really to have both of them in the same snap.
That's super simple, and it's fine that they are different languages,
different processes, etc.
On Thu, Mar 23, 2017 at 2:36 PM, Jenny Murphy
wrote:
> Hi,
> I currently have a java
Ah, please don't worry then!
Thanks for the report. We'll get this sorted out and get back to you.
On Mon, Mar 20, 2017 at 7:41 PM, Joseph Rushton Wakeling <
joseph.wakel...@webdrake.net> wrote:
> On 20/03/17 23:14, Gustavo Niemeyer wrote:
>
>> Most likely the snap was
On Fri, Mar 17, 2017 at 8:32 PM, Joseph Rushton Wakeling <
joseph.wakel...@webdrake.net> wrote:
> Hello folks,
>
> Is there anyone here working on snapd on Arch?
>
> I ask because I recently tried it out on a fresh Arch install and ran into
> some issues.
>
> Installing snaps works fine in
Thanks for your help on this, Michael.
Yes, the fix seems pretty simple and porting to older Go releases will
ensure people are not getting those super awkward messages randomly.
I have created a Trello card with a checklist so we can track all the
distributions that we need to fix, and included
Thanks for finding and debugging this John.
I can't see how this one would be in Go. I can't think of any related
action that would disable the setuid bit on the exec syscall.
Perhaps someone from the kernel team can help here?
On Mon, Mar 13, 2017 at 9:59 AM, John Lenton
Yes, that's definitely what we want to do. Have a description in the app
section in the yaml which allows recurring execution.
On Tue, Mar 7, 2017 at 1:27 PM, Mark Shuttleworth wrote:
>
> I think scheduled tasks make sense as a first-class primitive. In the
> same way we don't
wrote:
> On Tue, 2017-02-21 at 13:23 -0300, Gustavo Niemeyer wrote:
> > Actually, we do have a mechanism that enables the automatic connections
> in
> > those cases, and we can enable it in sensible cases, even for the camera.
> >
> > The question we should ask he
Actually, we do have a mechanism that enables the automatic connections in
those cases, and we can enable it in sensible cases, even for the camera.
The question we should ask here is this: what is the snap purpose? Is it
clear from the snap name and description that this is using a camera?
If
Hi there,
The problem there is that the confined xdg-open currently depends on
snapd-xdg-open, which is a server listening on dbus for the calls.
We're changing that mechanism in the short term so snapd will implement
that logic internally, precisely to remove that extra moving piece and
Hi Max,
The problem isn't spread itself, as it won't try to communicate out of the
host by itself. The problem is that snapd's test suite expects to be able
to talk to the network.
Someone would have to go through and fix all such cases to go through the
proxy, which is perhaps more troubling
com> wrote:
> On Wed, Feb 1, 2017 at 2:02 PM, Gustavo Niemeyer <gust...@niemeyer.net>
> wrote:
> >
> > Such embedded devices are still computers on the network. We'll all be
> much
> > better off if they are running their applications confined and secured.
> &g
.
On Wed, Feb 1, 2017 at 4:37 PM, Howard Cochran <howard@badger-technologies.
com> wrote:
> On Wed, Feb 1, 2017 at 12:22 PM, Gustavo Niemeyer
> <gustavo.nieme...@canonical.com> wrote:
> > We'll probably not support completely arbitrary passthrough options as it
Yeah, besides "build-packages" there's also "stage-packages" which does
exactly that.
Please let us know how it goes.
On Wed, Feb 1, 2017 at 8:34 AM, Luca Dionisi wrote:
> This is another solution that I thought of.
> I want to put the library mylib-y (the one that is
The current behavior is to present the full configuration every time, so
it'll definitely result in a healthy configuration every time no matter
what subset has changed, assuming the whole configuration is actually
valid, because changing 2 or 10 options at once results in the same
behavior on the
Yes, that's in the plans for configuration support already. The idea is to
extend snapctl with the ability to introspect exactly which settings have
changed since the last successful run of the script, and perhaps which
values it used to hold before.
For the time being, I suggest not worrying
e same way, given that copyright owners are declared in
> the license text.
>
> [1]: https://gitlab.com/osslugaru/lugaru/blob/master/Dist/Linux/l
> ugaru.appdata.xml
>
> On Tue, Jan 31, 2017 at 2:03 PM, Gustavo Niemeyer <gust...@niemeyer.net>
> wrote:
> >
>
That's an interesting idea. Is there a known repository for license texts
which are not standard? I see SPDX uses a LicenseRef- kind of
reference, but it's not clear what that is referencing. Just another field
inside the XML in the case of AppStream, I suppose?
On Thu, Jan 26, 2017 at 9:58 PM,
The short answer is that daemons are naturally restarted, so you shouldn't
have to do anything other than ensuring you're using the proper daemon type
(simple, forking, etc). See Luca's recommended URL for more details.
On Sun, Jan 29, 2017 at 11:52 AM, Anton Smith wrote:
>
It seems that the most common way to deploy Docker is by mapping ports out
of the private IP addresses into the local host's public IP, which means
it's completely analogous to multiple processes in the same host. Even when
assigning the docker container to an external IP, a commonly recommended
Interesting.. I actually don't see that line between snaps and Docker.
Just like you can run "docker run mysql" several times, one may run
"mysnap.mysql" several times. In both cases the daemon will be visible to
the external world via a separate port of the local host's public IP
address. In both
*the local snapd
On Jan 23, 2017 8:04 PM, "Gustavo Niemeyer" <gust...@niemeyer.net> wrote:
> Indeed, that smells like a bug, certainly because snap download doesn't
> use the local snaps to actually download the file. That should be
> transparent to the CLI though
Definitely a bug. Thanks for reporting it.
On Jan 24, 2017 5:35 PM, "Alejandro J. Cura"
wrote:
> Is that the expected behavior?
>
> alecu@localhost:~$ snap list
> NameVersionRev Developer Notes
> core16.04.1976 canonical
*the local snapd
On Jan 23, 2017 8:04 PM, "Gustavo Niemeyer" <gust...@niemeyer.net> wrote:
Indeed, that smells like a bug, certainly because snap download doesn't use
the local snaps to actually download the file. That should be transparent
to the CLI though.
Can you plea
;
wrote:
> Okay, you're right. I was testing with snap download, which doesn't seem
> to use to proxy, whereas snap refresh does. Is that intended behavior, or
> should I report it somewhere?
>
> Thanks,
> Max
>
> On Mon, Jan 23, 2017 at 2:04 PM, Gustavo Niemeyer &
This should work fine across reboots.
On Jan 23, 2017 4:49 PM, "Max Brustkern"
wrote:
> So I've been able to get it to work by creating
> /etc/systemd/system/snapd.service.d/proxy.conf
> with the correct settings. Any suggestions on getting that to persist
> across
That'd be ideal, thanks!
On Mon, Jan 23, 2017 at 3:19 PM, Mike Sheldon <michael.shel...@canonical.com
> wrote:
> Okay great, should I prepare a new branch that does the renaming?
>
> On Mon, 2017-01-23 at 14:34 -0200, Gustavo Niemeyer wrote:
> > Sounds good. If you think ub
Nice change, Boris!
Would you like to submit a PR for that?
We have a CLA you can easily sign online assuming you're happy with the
terms:
https://www.ubuntu.com/legal/contributors
On Tue, Jan 17, 2017 at 11:51 AM, Boris Rybalkin wrote:
> Yes, I had to add support on
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
It's definitely possible. It's just not very convenient yet.
For tests, easiest might be to bind mount your modifications at runtime.
On Mon, Jan 23, 2017 at 2:17 PM, Luca Dionisi
wrote:
> Hi all
>
> I see that the issue has been taken care of. I will immediately
>
Super nice indeed. Thanks, Oliver!
Has anyone tried the new GL and gpios? How did it go?
Perhaps we can ask for some extra millage on the pi community list itself?
On Wed, Jan 18, 2017 at 1:59 PM, Oliver Grawert wrote:
> hi,
>
> at [1] you can now find a daily image build
This smells like an apparmor denial, which shouldn't happen inside the
classic snap itself.
Can you reproduce the issue when using the stock kernel?
On Fri, Jan 20, 2017 at 6:46 PM, Jian LUO wrote:
> Hi list,
>
> as the topic suggested I got GPG error in classic snap
Yes, it seems fine for network-control to allow it.
On Mon, Jan 23, 2017 at 10:17 AM, Oliver Grawert wrote:
> hi,
> Am Samstag, den 21.01.2017, 11:33 +0100 schrieb Luca Dionisi:
> > On Fri, Jan 20, 2017 at 6:43 PM, Oliver Grawert
> > wrote:
> > >
> > > yes,
Hi Luca,
If you look under interfaces/builtin in the source code of snapd, you'll
find some familliar names if you list *network* and *firewall* in there. I
suspect that what you want is very easy to fix by simply introducing an
additional apparmor entry in the right interface.
If you want to
First thing I would do is include whatever you need inside the snap itself,
and get things working quickly.
Then, there are a few different ways you can move from there. The first one
is actually to do nothing.. the whole snap infrastructure (snapcraft,
snapd, uploads, downloads) is becoming
It's okay that the command itself isn't super visible. The main reason it
exists is to back console-conf, which is very visible and should be
properly documented.
On Wed, Jan 18, 2017 at 3:37 PM, Manik Taneja <ma...@canonical.com> wrote:
>
>
> On Wed, Jan 18, 2017 at 4:33 AM, G
ight 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
o 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 ta
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
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
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
Does it work for you after an update?
On Tue, Jan 17, 2017 at 12:37 PM, Max Brustkern wrote:
> Excellent, thanks!
>
> On Sun, Jan 15, 2017 at 11:54 PM, Stuart Bishop <
> stuart.bis...@canonical.com> wrote:
>
>>
>>
>> On 14 January 2017 at 03:33, Max Brustkern
That sounds fine, but also like a detour from the actual goal. One way or
another, the in-tree packaging that is there for Ubuntu won't be at stake
when making it work on Debian. Also note that the in-tree debian/ directory
doesn't work even for Ubuntu, strictly speaking. We already have the 14.04
Quick update on our bug tracking practices: https://launchpad.net/snapd was
opened up, and we invite all bugs which affect snapd to be explicitly
assigned to this project.
This will make slightly easier to track and update issues which require
explicit action on snapd vs. those which target
Nice :)
On Tue, Jan 10, 2017 at 5:55 PM, Oliver Grawert wrote:
> hi,
> Am Dienstag, den 10.01.2017, 15:40 + schrieb Alan Pope:
> >
> > >
> > For archive packages being slow (as you have) I use apt-cacher-ng on
> > my laptop. It caches the debs making snapcraft builds much
Hi Ajay,
That means the communication with the local snapd daemon failed abruptly,
which is unusual.
Can you tell us a bit more about the environment this is running on, and
which image it is?
Do you have access to the underlying filesystem somehow (is it an SD card?
VM?), in which case can you
This is one area that is still super confusing, and would be worth
investing some time on soon.
We discussed this back in May on:
- clean behavior is confusing
https://bugs.launchpad.net/snapcraft/+bug/1582469
As described there, this is a rock on the most important pipeline of the
tool.
On
On Mon, Jan 9, 2017 at 5:08 PM, Zygmunt Krynicki <
zygmunt.kryni...@canonical.com> wrote:
>
> > Wiadomość napisana przez Aleix Pol w dniu
> 08.01.2017, o godz. 20:26:
> >
> > Hi everyone,
> > Last Snappy meeting we discussed several subjects and I would like to
> > know what's
One detail: note that once your snap goes into the store and passes
reviews, that issue goes away. Actual users of your snap in the wild don't
have to say --dangerous.
On Wed, Dec 14, 2016 at 12:40 AM, Gustavo Niemeyer <
gustavo.nieme...@canonical.com> wrote:
> Hey Peng,
>
> W
dro...@ubuntu.com> wrote:
> Le 05/12/2016 à 16:05, Gustavo Niemeyer a écrit :
>
> Xavier posted the exact URL of the failing snap in this thread:
>
> Note it's not *the* failing snap but *a* failing snap. Every "snap
> install" here is failing on my setup when t
Yeah, -L is the flag that makes it follow the redirect, IIRC.
On Mon, Dec 5, 2016 at 1:03 PM, Bret A. Barker <bret.bar...@canonical.com>
wrote:
> On Mon, Dec 05, 2016 at 03:52:32PM +0100, Didier Roche wrote:
> > Le 05/12/2016 à 15:38, Gustavo Niemeyer a écrit :
> > >
&
che <didro...@ubuntu.com> wrote:
> Le 05/12/2016 à 15:38, Gustavo Niemeyer a écrit :
>
>
>
> On Mon, Dec 5, 2016 at 12:23 PM, Didier Roche <didro...@ubuntu.com> wrote:
>
>> I did though write on the bug: "contrary to curl or wget which both
>> supports l
Hi Julia,
Yes, that's the goal. And soon you'll also be able to assign different
permissions to the different keys, so you can limit their scope.
On Thu, Nov 24, 2016 at 11:04 AM, Julia Palandri <
julia.palan...@canonical.com> wrote:
> Hi,
>
> On Wed, Nov 23, 2016 at 9:56 PM, Peng Liu
The problem is that snapd works in environments where the dependencies to
make the browser-launcher work aren't available.
The right fix is probably to make it a dependency of one of the debs that
are always installed on a normal desktop system, whether snapd is there or
not. It's a very minimal
Hello all,
The 2016.11.14 release of Spread is now available both as a snap and at
Travis.
There are quite a few interesting changes on this one:
- Support for fetching files generated by the remote tasks:
https://github.com/snapcore/spread#residue
- Support for "manual"
Glad you figured it out.
Note that the behavior of removing the snap from the original seed was
actually a bug we already fixed.
The stable image will be out very soon, and has that problem as well as
many others properly fixed.
On Wed, Nov 2, 2016 at 9:21 PM, Luke Williams
wrote:
> On Wed, 2016-11-02 at 20:06 -0200, Gustavo Niemeyer wrote:
> > Ok, thanks for those details. We'll look more deeply into this
> > tomorrow and try to reproduce the issue.
> >
> > To fix your problem, can you please try this simple hack to get over
> > the bug:
.
On Wed, Nov 2, 2016 at 7:53 PM, Chris <cpoll...@embarqmail.com> wrote:
> On Wed, 2016-11-02 at 18:43 -0200, Gustavo Niemeyer wrote:
> > Hi Chris,
> >
> > Can you please try updating your snapd package?
> >
> > Recent releases have a more reliable remove proced
Hi Chris,
Can you please try updating your snapd package?
Recent releases have a more reliable remove procedure that handles these
cases better.
On Wed, Nov 2, 2016 at 6:40 PM, Chris wrote:
> I went to remove a snap, viking-gps, and it just sat there doing
> nothing.
We actually have that already in the upcoming version. You'll be able to
say "snap refresh --revison=N ", similarly to how we can revert.
That said, I think the expectation exposed in the first message is a
reasonable one. We should probably not blacklist the current revision if
the snap name was
On Tue, Oct 25, 2016 at 2:37 PM, Sergio Schvezov <
sergio.schve...@canonical.com> wrote:
> This is how I do it on the fly (there was a session at the sprint for this
> to be easier)...
>
> ```
> snapcraft prime
> snap try prime --devmode
> cp /usr/bin/strace prime
> snap shell --shell
>
This is
gt; Thanks,
>
> On Fri, Oct 21, 2016, 20:41 Gustavo Niemeyer <gustavo.niemeyer@canonical.
> com> wrote:
>
>> Hey Aaron,
>>
>> The most likely cause is, as you suspected, an out of date snapd.
>> SNAP_COMMON was introduced some time after 16.04 (don't have
Hey Aaron,
The most likely cause is, as you suspected, an out of date snapd.
SNAP_COMMON was introduced some time after 16.04 (don't have exact version
at hand right now).
With recent versions of snapd, the running infrastructure was significantly
improved and simplified compared to 16.04
On Wed, Oct 5, 2016 at 11:34 PM, Spencer wrote:
> My entry into the snap world has been a tough one. There is online
> documentation, but it is not kept up-to-date. I get the feeling that the
> bar for entry is the need to be the kind of person who loves to learn
>
Hello,
On Tue, Oct 4, 2016 at 5:43 AM, Jacek Nykis
wrote:
> > Is there an example on how a filesets line may look like, a grep on the
> > playpen repository does not seem to match filesets ?
>
> https://git.launchpad.net/prometheus-snap/tree/snapcraft.yaml
Thanks
That was a good explanation indeed, thanks John.
Can we do something better than just recommend it on classic? The feature
is common enough that this should be a requirement, I think.
The problem then is how to drop the package when building the Ubuntu Core
image.
On Wed, Sep 21, 2016 at 5:39
Hello all,
GitHub has finally implemented the last few pieces missing to have sane
reviews directly on PRs, which is great for us. Most importantly, we can
now draft out a full review, including the final comments, before we ship
the comments all at once, including a verdict. The verdict may be
Thanks so much and congratulations to everybody who worked hard to put in
place this initial public release of Ubuntu Core, a minimalist Linux
distribution that uses snaps as its building blocks. Special thanks as well
to Michael, Oliver Grawert, Martin Pitt, and others who've put all the bits
in
Rather than splitting Ubuntu Core, I suggest splitting device building.
Ubuntu Core is just another distribution using snaps, so discussing the
well-being of snaps and snapd inside it sounds like a welcome topic here.
Device building and image tuning is a world on itself, though.
On Wed, Sep 7,
They can install it as devmode, and we can also introduce an
"editor-support" interface which gives global read/write access to it.
Would need to be manually connected for the time being, but assertion
control for that is coming very soon.
On Wed, Sep 7, 2016 at 7:40 AM, Matthew Williams <
Hey Martin,
Just put your files under defaults/etc/quagga, and use:
defaults:
plugin: dump
source: defaults
On Sep 2, 2016 7:36 PM, "Martin Winter"
wrote:
> So I’ve updated the quagga snap from using the copy plugin to the dump
> plugin.
>
Hi Oliver,
On Fri, Sep 2, 2016 at 4:07 AM, Oliver Grawert wrote:
>
> does it actually matter what *we* use ? its the slang of the android
>
kids, it is what they know and will use when talking about the topic of
installing local packages,
The terminology we use for our
On Fri, Sep 2, 2016 at 10:35 AM, Tony Espy <e...@canonical.com> wrote:
> On 09/01/2016 06:15 PM, Gustavo Niemeyer wrote:
>
>> Hello all,
>>
>> With assertions finally being put to great use, it's time to kill the
>> term "sideloading". That term does
Hey Victor,
On Fri, Sep 2, 2016 at 4:14 AM, Victor Palau
wrote:
> Hi,
>
> In the case of installing snaps from the local file system, where will the
> assertions require to installation reside? Also in the local file system?
>
The knowledge of which assertions are
Hello all,
With assertions finally being put to great use, it's time to kill the term
"sideloading". That term does a disservice to our conversations, because it
is vague and also limits the thinking around what is possible.
Whenever we use "sideloading", we mean one of two things:
1. The
Hello all,
The following changes have just landed in the spread repository, some of
them incompatible with the previous yaml files.
Given the incompatibility, the spread snap or the binary version used by
the snapd tests weren't updated, but this should happen at some point
tomorrow.
The main
f the package gets removed). That seems like an easy place to
> get started.
>
> Ted
>
> ¹ Not sure if upgrade is a remove/install pair, listed for completeness,
> not because we have a need for it to be distinct.
>
> On Wed, 2016-08-17 at 10:56 -0300, Gustavo Niemeyer wrote
Yeah, this is non-working remainings of something that wasn't discussed
much.
Before patching it, we need to come up with a more clear idea of how the
API looks like, how it's supposed to evolve, and what's the plan for
integration into the various aspects of the system.
On Wed, Aug 17, 2016
80 matches
Mail list logo