On Fri, Dec 1, 2017 at 12:15 AM, Jim Davis <jim.ep...@gmail.com> wrote: > > If I run /snap/bin/snapcraft --version now on that Ubuntu 16.04 VM I > am getting 2.36+git2.ae61453.
Yep, the edge channel follows the bleeding edge: $ snap info snapcraft ... channels: stable: 2.35 (794) 53MB classic candidate: ↑ beta: 2.36.1 (876) 53MB classic edge: 2.36.1+git6.3524514 (895) 53MB classic you better switch to beta (and then stable when 2.36.1 gets promoted there): $ snap refresh --beta snapcraft > I noticed that if I tried to make snap-pkg with the O=/some/dir option > the tar step failed but the rest of the build continued, and seems to > have finished successfully. Should the snap-pkg target stop after a > tar failure? That is weird, how did you do that? My experience with the O=... option (that mimicks the other rpm-pkg and deb-pkg targets) is that, you first create the dir, copy there the .config and it builds fine: ~/linux $ mke defconfig ... ~/linux $ mkdir /tmp/foobar ~/linux $ mv .config /tmp/foobar ~/linux $ git clean -ffdx ~/linux $ make O=/tmp/foobar snap-pkg ... Snapped kernel_4.14.0+_amd64.snap ~/linux $ ls -la /tmp/foobar/snap/ -rw-r--r-- 1 flag flag 14114816 dic 5 12:41 kernel_4.14.0+_amd64.snap drwxrwxr-x 3 flag flag 4096 dic 5 12:38 parts drwxrwxr-x 4 flag flag 4096 dic 5 12:41 prime drwxrwxr-x 3 flag flag 4096 dic 5 12:38 snap -rw-rw-r-- 1 flag flag 274 dic 5 12:38 snapcraft.yaml drwxrwxr-x 3 flag flag 4096 dic 5 12:41 stage -- bye, p.
