On Fri, Dec 23, 2016 at 03:32:19PM +, Luther Goh Lu Feng wrote:
> If I am building a snap, and for some reason, I wish to not snap it from
> source, but from a compiled binary, is it allowed? Thanks.
Luther, it is allowed; snaps are just squashfs filesystems with some
metadata in expected
Am Freitag, den 23.12.2016, 12:10 -0600 schrieb Peng Liu:
> Hi Folks,
>
> There used to be a command to disable the automatic update feature of
> ubuntu-core on 15.04 release. Is such interface still available for
> 16.04?
>
something like:
sudo systemctl disable snapd.refresh.timer
should
> Wiadomość napisana przez Kyle Fazzari w dniu
> 23.12.2016, o godz. 19:27:
>
> Hey all.
>
> I'm trying to figure out what the `content` attribute is for in the
> content interface. The docs say "The content attribute specified of the
> consuming snap (plug) must
Hi Folks,
There used to be a command to disable the automatic update feature of
ubuntu-core on 15.04 release. Is such interface still available for 16.04?
Thanks.
Peng
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
If I am building a snap, and for some reason, I wish to not snap it from
source, but from a compiled binary, is it allowed? Thanks.
-- Luther
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
Hi all!
I've just added another part in the wiki, you can see it as the last
one here:
https://wiki.ubuntu.com/snapcraft/parts
It's the webapp-helper part. As you can see from its definition [1],
it's meant to be built after the 'desktop-ubuntu-app-platform' part.
But when I run
Hi,
I could NOT reproduce this issue by 4.4.0-1029-raspi2 and
4.4.0-1034-raspi2. That is, this issue happens with the latest kernel in
updated pocket.(4.4.0-1038-raspi2)
I have filed this bug report
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270
Cheers,
Taihsiang
On Fri, Dec 23, 2016 at 6:42 AM, Taihsiang Ho wrote:
> Hello, I tried to update the system without enabled proposed pocket today,
> and I CAN reproduce this issue on pi3. Let me bisect the kernel version to
> have a preliminary check, and will update the test soon in this