Re: Building snap from binaries
Hi Luther, yes it is possible to build snaps from binaries. If the binaries don't include dependencies you probably want to include some dependencies via stage-packages. So if you use snapcraft to build your snap instead of manually crafting a squashfs then take a look at the dump plugin: http://snapcraft.io/docs/reference/plugins/dump With it you can easily organise your files within the snap. Am 23.12.2016 um 16:32 schrieb Luther Goh Lu Feng: > 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
Re: Building snap from binaries
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 filenames. I've been unable to keep track of a spec for it, sorry, but if you snap up a simple tool and inspect the resulting squashfs image you'll probably learn all you need to know faster than I could find a reference. :) Thanks signature.asc Description: PGP signature -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Content interface `content` attribute
On 12/23/2016 01:32 PM, Zygmunt Krynicki wrote: 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 have a content attribute match in the providing snap (slot)." However, I have two snaps, provider side looking like this: slots: share-foo: content: foo interface: content read: [/] Consumer side like this: plugs: use-foo: content: foo2 interface: content target: /bar These interfaces connect fine, and I can see the contents of the This is a bug. We know about it but fixing was deferred till we can use the assertion system to control it. Currently you can connect things manually but it will not auto-connect. Is there a launchpad bug for this? Regards, /tony -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Content interface `content` attribute
On 12/23/2016 10:32 AM, Zygmunt Krynicki wrote: > >> 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 have a content attribute match in the >> providing snap (slot)." However, I have two snaps, provider side looking >> like this: >> >>slots: >> share-foo: >>content: foo >>interface: content >>read: [/] >> >> Consumer side like this: >> >>plugs: >> use-foo: >>content: foo2 >>interface: content >>target: /bar >> >> These interfaces connect fine, and I can see the contents of the > > This is a bug. We know about it but fixing was deferred till we can use the > assertion system to control it. > > Currently you can connect things manually but it will not auto-connect. Fair enough. If this worked as expected, what would it do? What functionality does that attribute provide? -- Kyle Fazzari (kyrofa) Software Engineer Canonical Ltd. k...@canonical.com 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: Is there any interface to disable the automatic update feature?
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 work, note though that this will disable also the auto-update of applications AFAIK... 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: Is there any interface to disable the automatic update feature?
> Wiadomość napisana przez Peng Liu w dniu 23.12.2016, > o godz. 19:10: > > 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? Not at present. We want to give snaps a way to control the update feature in certain specific ways (schedule usual updates and defer updates during critical sections). Stay tuned for more development towards that goal next year. Best regards ZK -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Content interface `content` attribute
> 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 have a content attribute match in the > providing snap (slot)." However, I have two snaps, provider side looking > like this: > >slots: > share-foo: >content: foo >interface: content >read: [/] > > Consumer side like this: > >plugs: > use-foo: >content: foo2 >interface: content >target: /bar > > These interfaces connect fine, and I can see the contents of the This is a bug. We know about it but fixing was deferred till we can use the assertion system to control it. Currently you can connect things manually but it will not auto-connect. > provider within $SNAP/bar of the consumer. Running snapd v2.17.1. So > unless I misunderstand the sentence from the docs, that doesn't seem > accurate, and I have no idea what this attribute does. > > Any ideas? Best regards ZK -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Content interface `content` attribute
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 have a content attribute match in the providing snap (slot)." However, I have two snaps, provider side looking like this: slots: share-foo: content: foo interface: content read: [/] Consumer side like this: plugs: use-foo: content: foo2 interface: content target: /bar These interfaces connect fine, and I can see the contents of the provider within $SNAP/bar of the consumer. Running snapd v2.17.1. So unless I misunderstand the sentence from the docs, that doesn't seem accurate, and I have no idea what this attribute does. Any ideas? -- Kyle Fazzari (kyrofa) Software Engineer Canonical Ltd. k...@canonical.com 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
Is there any interface to disable the automatic update feature?
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: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Building snap from binaries
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
Error with snapcraft part including another part
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 snapcraft on my project [2], all I get is an unhelpful red single line: 'desktop-ubuntu-app-platform' on the standard error (I reported this unhelpfulness as a bug). Can you help me spot the error, or is it that snapcraft does not yet support having the "after" statement between remote parts? Ciao, Alberto [1]: https://gitlab.com/mardy/snapcraft-webapp-helper/blob/master/snapcraft.yaml [2]: https://code.launchpad.net/~mardy/webapps-core/amazon-snap [3]: https://bugs.launchpad.net/bugs/1652290 -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Tutorial: how to give apps alias name?
2016-12-23 5:12 GMT-02:00 XiaoGuo Liu : > You need to have snap 2.20 and snapcraft 2.24 to support it. > Hi, I have a doubt; the final user is the one that has to have an updated snapd environment. Since, we cannot control this: - I guess nothing bad is going to happen if the user is still on, e.g., snap 2.17. Am I right? - is there a need to create in snapd a kind of depends keyword to assure a snap is in a "valid environment"? Thank you -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
Re: Classic image not working after upgrade on RPI 3
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 2016-12-23 16:37 GMT+08:00 Ara Pulido : > > > 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 >> thread. Does anyone suggest anything to help us to narrow down this issue? >> Thanks. >> > > Can we file a bug as well, please? > > And track progress of the bisect there. > > Thanks! > Ara. > > >> >> -Tai >> >> 2016-12-22 17:32 GMT+08:00 Sergey Borovkov : >> >>> Hello. Full dpkg list - https://hastebin.com/qofatafaxu.sql >>> And this is the output of dpkg -l | grep -e uboot -e flash-kernel -e >>> firmware -e linux-raspi2 -e u-boot: >>> root@ubuntu:/home/ubuntu# dpkg -l | grep -e uboot -e flash-kernel -e >>> firmware -e linux-raspi2 -e u-boot >>> ii flash-kernel 3.0~rc.4ubuntu64~rpi3 >>> armhfutility to make certain embedded devices bootable >>> ii linux-firmware 1.157.6 >>>all Firmware for Linux kernel drivers >>> ii linux-firmware-raspi21.20161020-0ubuntu1~0.1 >>>armhfRaspberryPi2 GPU firmware and bootloaders >>> ii linux-raspi2 4.4.0.1039.38 >>> armhfComplete Linux kernel for the BCM2709 >>> architecture. >>> ii linux-raspi2-headers-4.4.0-1009 4.4.0-1009.10 >>> armhfHeader files related to Linux kernel >>> version 4.4.0 >>> ii linux-raspi2-headers-4.4.0-1029 4.4.0-1029.36 >>> armhfHeader files related to Linux kernel >>> version 4.4.0 >>> ii linux-raspi2-headers-4.4.0-1038 4.4.0-1038.45 >>> armhfHeader files related to Linux kernel >>> version 4.4.0 >>> ii linux-raspi2-headers-4.4.0-1039 4.4.0-1039.46 >>> armhfHeader files related to Linux kernel >>> version 4.4.0 >>> ii u-boot-rpi:armhf 2016.09+dfsg1-1~rpi3.1 >>> armhfA boot loader for Raspberry PI systems >>> ii u-boot-tools 2016.09+dfsg1-1~rpi3.1 >>> armhfcompanion tools for Das U-Boot bootloader >>> >>> >>> On 22 December 2016 at 06:46, Taihsiang Ho wrote: >>> Hi, Sergey, Would you please make sure the following packages are also updated by dpkg -l | grep -e uboot -e flash-kernel -e firmware -e linux-raspi2 -e u-boot And you should get the package information like this comment https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/ 1636838/comments/20 Cheers, Taihsiang 2016-12-22 2:48 GMT+08:00 Sergey Borovkov : > Ok, so I enabled xenial proposed. > > Got following versions: > Setting up linux-firmware-raspi2 (1.20161020-0ubuntu1~0.1) ... > Setting up linux-raspi2-headers-4.4.0-1038 (4.4.0-1038.45) ... > Setting up linux-headers-4.4.0-1038-raspi2 (4.4.0-1038.45) ... > Setting up linux-image-raspi2 (4.4.0.1038.37) ... > Setting up linux-headers-raspi2 (4.4.0.1038.37) ... > Setting up linux-raspi2 (4.4.0.1038.37) ... > Setting up python3-cryptography (1.2.3-1ubuntu0.1) ... > Setting up python3-software-properties (0.96.20.5) ... > Setting up software-properties-common (0.96.20.5) ... > > > And again image does not boot after restart. Stuck in "starting > kernel". > > On 21 December 2016 at 19:20, Chris Wayne > wrote: > >> Hi Sergey, >> >> Which image are you using? Is it possible this is the same as this >> bug: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/ >> +bug/1636838 (which should now be fixed). Perhaps you could try the >> PPA listed in that bug? (Note that this is technically a bug for rpi2, >> but >> I *believe* they may share the same kernel) >> >> Thanks >> Chris >> >> On Wed, Dec 21, 2016 at 9:57 AM, Sergey Borovkov < >> serge.borov...@gmail.com> wrote: >> >>> Hi. After I did apt upgrade on classic image I can't boot my RPI >>> anymore. It's stuck on 'Starting kernel...'. >>> Tried different SD cards (on the second one I flashed out new >>> classic image and did upgrade as well) with the same result. >>> >>> -- >>> Snapcraft mailing list >>> Snapcraft@lists.snapcraft.io >>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >>> an/listinfo/snapcraft >>> >>> >> >> -- >> Snapcraft mailing list >> Snapcraft@lists.snapcraft.io >> Modify set
Re: Classic image not working after upgrade on RPI 3
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 thread. > Does anyone suggest anything to help us to narrow down this issue? Thanks. > Can we file a bug as well, please? And track progress of the bisect there. Thanks! Ara. > > -Tai > > 2016-12-22 17:32 GMT+08:00 Sergey Borovkov : > >> Hello. Full dpkg list - https://hastebin.com/qofatafaxu.sql >> And this is the output of dpkg -l | grep -e uboot -e flash-kernel -e >> firmware -e linux-raspi2 -e u-boot: >> root@ubuntu:/home/ubuntu# dpkg -l | grep -e uboot -e flash-kernel -e >> firmware -e linux-raspi2 -e u-boot >> ii flash-kernel 3.0~rc.4ubuntu64~rpi3 >> armhfutility to make certain embedded devices bootable >> ii linux-firmware 1.157.6 >>all Firmware for Linux kernel drivers >> ii linux-firmware-raspi21.20161020-0ubuntu1~0.1 >>armhfRaspberryPi2 GPU firmware and bootloaders >> ii linux-raspi2 4.4.0.1039.38 >> armhfComplete Linux kernel for the BCM2709 >> architecture. >> ii linux-raspi2-headers-4.4.0-1009 4.4.0-1009.10 >> armhfHeader files related to Linux kernel >> version 4.4.0 >> ii linux-raspi2-headers-4.4.0-1029 4.4.0-1029.36 >> armhfHeader files related to Linux kernel >> version 4.4.0 >> ii linux-raspi2-headers-4.4.0-1038 4.4.0-1038.45 >> armhfHeader files related to Linux kernel >> version 4.4.0 >> ii linux-raspi2-headers-4.4.0-1039 4.4.0-1039.46 >> armhfHeader files related to Linux kernel >> version 4.4.0 >> ii u-boot-rpi:armhf 2016.09+dfsg1-1~rpi3.1 >> armhfA boot loader for Raspberry PI systems >> ii u-boot-tools 2016.09+dfsg1-1~rpi3.1 >> armhfcompanion tools for Das U-Boot bootloader >> >> >> On 22 December 2016 at 06:46, Taihsiang Ho wrote: >> >>> Hi, Sergey, >>> >>> Would you please make sure the following packages are also updated by >>> >>> dpkg -l | grep -e uboot -e flash-kernel -e firmware -e linux-raspi2 -e >>> u-boot >>> >>> >>> And you should get the package information like this comment >>> https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/ >>> 1636838/comments/20 >>> >>> Cheers, >>> Taihsiang >>> >>> 2016-12-22 2:48 GMT+08:00 Sergey Borovkov : >>> Ok, so I enabled xenial proposed. Got following versions: Setting up linux-firmware-raspi2 (1.20161020-0ubuntu1~0.1) ... Setting up linux-raspi2-headers-4.4.0-1038 (4.4.0-1038.45) ... Setting up linux-headers-4.4.0-1038-raspi2 (4.4.0-1038.45) ... Setting up linux-image-raspi2 (4.4.0.1038.37) ... Setting up linux-headers-raspi2 (4.4.0.1038.37) ... Setting up linux-raspi2 (4.4.0.1038.37) ... Setting up python3-cryptography (1.2.3-1ubuntu0.1) ... Setting up python3-software-properties (0.96.20.5) ... Setting up software-properties-common (0.96.20.5) ... And again image does not boot after restart. Stuck in "starting kernel". On 21 December 2016 at 19:20, Chris Wayne wrote: > Hi Sergey, > > Which image are you using? Is it possible this is the same as this > bug: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/ > +bug/1636838 (which should now be fixed). Perhaps you could try the > PPA listed in that bug? (Note that this is technically a bug for rpi2, but > I *believe* they may share the same kernel) > > Thanks > Chris > > On Wed, Dec 21, 2016 at 9:57 AM, Sergey Borovkov < > serge.borov...@gmail.com> wrote: > >> Hi. After I did apt upgrade on classic image I can't boot my RPI >> anymore. It's stuck on 'Starting kernel...'. >> Tried different SD cards (on the second one I flashed out new classic >> image and did upgrade as well) with the same result. >> >> -- >> Snapcraft mailing list >> Snapcraft@lists.snapcraft.io >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/snapcraft >> >> > > -- > Snapcraft mailing list > Snapcraft@lists.snapcraft.io > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/snapcraft > > -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm an/listinfo/snapcraft >>> >> > > -- > Snapcraft mailing list > Snapcraft@lists.snapcraft.io > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > > -- Snapcraft mailing list Snapcr
