~brian-murray/livecd-rootfs:xnox/fix-pi-models

Last commit made on 2020-05-01
Get this branch:
git clone -b xnox/fix-pi-models https://git.launchpad.net/~brian-murray/livecd-rootfs
Only Brian Murray can upload to this branch. If you are Brian Murray please log in for upload directions.

Branch merges

Branch information

Name:
xnox/fix-pi-models
Repository:
lp:~brian-murray/livecd-rootfs

Recent commits

e25aec1... by Dimitri John Ledkov

ubuntu-image: fix focal+ pi images for armhf to use pi-armhf model name. (LP: #1876358)

6e8b5b9... by Dimitri John Ledkov

ubuntu-image: fix focal+ pi images for armhf to use pi-armhf model name.

LP: #1876358

99e129f... by Dimitri John Ledkov

Merge branch 'xnox/lp-uc20-8gb' of git+ssh://git.launchpad.net/livecd-rootfs into ubuntu/master

e013459... by Dimitri John Ledkov

Bump only the UC20 pc image to 8GB, and keep Pi images as small as possible. (LP: #1875430)

668898d... by Dimitri John Ledkov

Bump only the UC20 pc image to 8GB, and keep Pi images as small as possible.

LP: #1875430

1f120d7... by Robert C Jennings

Release 2.664

86b455c... by Robert C Jennings

Merge vagrant_40_gb into ubuntu/master [a=patviafore] [r=rcj]

Make Ubuntu Vagrant box 40G. (LP: #1580596)

Vagrant images were previously put at 10G, but this was a regression
from Trusty, in which they were 40G. This made it a tough sell for
users to upgrade if they were using a Ubuntu desktop experience.

This change does not impact disk usage as Vagrant with the virtualbox
provider dynamically allocates space with the VMDK. On a test system,
the VMDK took up 1.1G of disk space according to df, and after
creating a 2G file in Vagrant, the VMDK grew to 3.1G.

Therefore, users who are running on a system with little free space
will not see adverse effects if they upgrade to a new vagrant image

MP: https://code.launchpad.net/~patviafore/livecd-rootfs/+git/livecd-rootfs/+merge/382509

2c70ed1... by Pat Viafore

Make Ubuntu Vagrant box 40G. (LP: #1580596)

Vagrant images were previously put at 10G, but this was a regression
from Trusty, in which they were 40G. This made it a tough sell for
users to upgrade if they were using a Ubuntu desktop experience.

This change does not impact disk usage as Vagrant with the virtualbox
provider dynamically allocates space with the VMDK. On a test system,
the VMDK took up 1.1G of disk space according to df, and after
creating a 2G file in Vagrant, the VMDK grew to 3.1G.

Therefore, users who are running on a system with little free space will
not see adverse effects if they upgrade to a new vagrant image

85e91dd... by Dimitri John Ledkov

releasing package livecd-rootfs version 2.663

ad64e38... by Dimitri John Ledkov

Run snap info on the downloaded snap, rather than against the store. First of all snap info doesn't have --channel argument, thus queries the wrong channel, and depening on the cohort, a different snap might be visible too. Thus seed the base of the snap revision we dowanloaded, rather than some random one from the store.