New all-snap images available
Kai Heng Feng
kai.heng.feng at canonical.com
Fri Jan 15 12:01:38 UTC 2016
Just noticed that I replied to you directly but not the mailing list...
On Fri, Jan 15, 2016 at 6:24 PM, Michael Vogt <mvo at ubuntu.com> wrote:
> On Thu, Jan 14, 2016 at 05:05:22PM +0800, Kai Heng Feng wrote:
>> Hi Michael,
> Hi Kai-Heng Feng,
>
> thanks for your mail!
>
>> Thanks for the great work!
>>
>> I am just wondering, will there be any official BeagleBone Black image
>> in the future?
>
> The future of the beagleboneblack image is a bit uncertain. I will
> clarify with my manager. AIUI the plan is to only have the pi2 as an
> officially supported image on arm(32bit).
Thanks for the clarification.
>
> Building a beaglebone image is pretty trivial though so if there is
> interesst (and if its useful for you or your team) I can just build
> one and put the snaps into my own (.mvo) namespace.
That would be great!
>
> Cheers,
> Michael
>
Thanks,
Kai-Heng Feng
>
>> Thanks,
>> Kai-Heng Feng
>>
>>
>> On Wed, Jan 13, 2016 at 10:24 PM, Michael Vogt
>> <michael.vogt at canonical.com> wrote:
>> > Hi,
>> >
>> > I'm happy to announce a new set of images for the all-snap
>> > architecture.
>> >
>> > The images are available here:
>> >
>> > https://people.canonical.com/~mvo/all-snaps/ [1]
>> >
>> > together with the matching ubuntu-device-flash based on
>> > lp:~snappy-dev/goget-ubuntu-touch/all-snaps.
>> >
>> > The difference from the previous all-snap images is that the goal is
>> > to keep them upgradable on amd64 all the way to 16.04-final.
>> >
>> > The highlights:
>> > - Uses kernel/OS snaps with the final names [2]
>> > - Uses /snaps as the base location for all installed snaps
>> > - Uses squashfs snaps only
>> >
>> > The switch to squashfs only is important for us. But it does mean that
>> > for some days the store support will be limited until the store is
>> > updated. Until this update is rolled out you can upload either to
>> > 15.04 or rolling. There is no support for snaps with the same name
>> > that support both releases. As an easy workaround you can sideload to
>> > your 16.04 image or just use a different name for the snap in the
>> > store until the store implements support for having different snaps
>> > for the different releases (it won't take very long).
>> >
>> > Existing xenial system-image based images will not receive updates
>> > anymore but will continue to work.
>> >
>> > Please let us know if you notice any issues!
>> >
>> > Cheers,
>> > Michael
>> >
>> > [1] Hashes:
>> > d8596380187880859fd6f390d56b854dc1cd0052e4067114dc9c195fe9a133a4 amd64-all-snap.img.xz
>> > 5085009f88243be2a5a63e8d16003324452ccc01258aafff9807ac7e46aacc50 rpi2-all-snap.img.xz
>> > 40931075520bf3d59c0feefd1fa7ec7eb33eb885103281cda44f2ac757df00a9 ubuntu-device-flash
>> >
>> > [2] The pi2 image contains an "ubuntu-core-armhf" OS snap that we will
>> > be renamed to ubuntu-core once the store supports that.
>> > --
>> > snappy-devel mailing list
>> > snappy-devel at lists.ubuntu.com
>> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
>> >
More information about the snappy-devel
mailing list