New snapd 2.23.1 release

Hi all, on top of 2.23 we released a small bugfix release: 2.23.1. We noticed that an incompatiblity in the content interface slipped into the 2.23 release and this is fixed now in 2.23.1. We used the opportunity to fix some more small bugs in 2.23.1, most importantly a bug that can result in an

Re: content interface, DENIED mounting $SNAP/mydir

I'd like to propose adding a way to declare in snapcraft.yaml that a folder under SNAP_COMMON (or SNAP_DATA) be created if it does not exist. Even though interface hooks (future) would seem to support this, it seems a common case so a simpler solution seems apt. The particular issue it would

Re: Updating a gadget snap

Hi, Is there a description/understanding of to expect with a time frame? This information would help Renat and others who want to be sure that products made today have an upgrade path in the field. Cheers, kyleN On 03/08/2017 05:54 AM, Ренат Галимов wrote: Thanks, Jamie. The reason we need

no option for unrevisioned home

Hello! I have seen a couple of projects that would suffer by having a revisioned $HOME, mainly because they store big files in there so during an update it would be a problem if we copy ~/snap/project/x1/ to ~/snap/project/x2. Now I'm working on the bitcoin snap, and it would mean copying 110GB,

Re: Updating a gadget snap

Hi, Also, forgot to mention that also we need a way to update the raspberry pi firmware files. Updating those files may cause the node to fail to boot. A/B system for those files is also necessary, in my opinion. Thanks, Renat On Thu, Mar 9, 2017 at 7:38 PM, knitzsche wrote: > Hi, > > Is there

Re: GEM/Ruby snapcraft plugin?

On Sat, Mar 4, 2017 at 1:55 PM, Leo Arias wrote: > Hey Justin! > > On Wed, Feb 15, 2017 at 12:45 AM, Justin McPherson > wrote: > > I had a chance to take a quick look at this; see here > > > > > > The plugin works in this case, with gist. But is not good