Last commit made on 2020-07-21
Get this branch:
git clone -b wip/ubuntu/focal/studio
Members of Ubuntu Core Development Team can upload to this branch. Log in for directions.

Branch merges

Branch information


Recent commits

54508e6... by Iain Lane

Hack seeding of linux kernel in ubuntustudio/focal

ubuntustudio-default-settings in focal release has a Recommends to this
kernel, which makes it impossible to update the kernel later on, since
we would install the -updates and release kernel, which isn't allowed
and causes FTBFS. Hack out the focal-release kernel and let the rest of
the build process pull in the right one.

LP: #1884915

e611dfc... by Łukasz Zemczak

Enable overrides of UC20 grade dangerous channels

cd098e7... by Philip Roche

Revert of initramfs package removal in KVM image (LP: #1880170)

It was reported and confirmed in LP bug #1875400
( that on the public
KVM cloud image there exists a large list of packages marked for auto-removal.

This should never be the case on a released cloud image.

These packages are marked for auto-removal because in the KVM image binary hook
we removed both initramfs-tools and busybox-initramfs packages. Due to package
dependencies this also removed:

busybox-initramfs* cloud-initramfs-copymods* cloud-initramfs-dyn-netconf*
cryptsetup-initramfs* initramfs-tools* initramfs-tools-core* multipath-tools*
overlayroot* sg3-utils-udev* ubuntu-server*

But it did not remove all the packages that the above list depended on.
This resulted in all those packages being marked for auto-removal because they
were not manually installed nor did they have any manually installed packages
that depended on them.

The removal of initramfs-tools and busybox-initramfs was to avoid the
generation of initramfs in images that should boot initramfsless.

This requirement is obsolete now because the initramfsless boot handling
is now handled via setting GRUB_FORCE_PARTUUID in /etc/default/grub.d/40-force-partuuid.cfg.

In test images I have verified that GRUB_FORCE_PARTUUID is set and that
boot speeds have not regressed.

LP: #1880170

225f2fe... by Łukasz Zemczak

Fix indentation.

0a2fbb8... by Dimitri John Ledkov

releasing package livecd-rootfs version 2.664.1

54b8e73... by Dimitri John Ledkov

ubuntu-image: drop ubuntu-image dep on riscv64, as not installable yet.

LP: #1876359
(cherry picked from commit 282c5a5bd50f9844cc077823b39550c663a013c3)

2d5f958... by Dimitri John Ledkov

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

LP: #1876358
(cherry picked from commit 6e8b5b94c4a9f8db4afbaf566ebdb36110f08592)

dc456c2... by Dimitri John Ledkov

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

LP: #1875430
(cherry picked from commit 668898d92c1a48ac4901661d0e5d7e4b117b09c0)

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