RUN: /usr/share/launchpad-buildd/bin/in-target buildlivefs --backend=lxd
--series=xenial --arch=powerpc LIVEFSBUILD-167495 --project ubuntu-cpc
--datestamp 20190523 --image-format ext4
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be ins
** Summary changed:
- livecd-rootfs xenial powerpc arch builds broken
+ Ubuntu image builds broken for powerpc on xenial
** Description changed:
+ livecd-rootfs is used to build our Ubuntu images and it depends on
ubuntu-image. With ubuntu-image 1.7 being published to xenial-updates the diff
Public bug reported:
libu2f-udev in disco has out of date rules (as does eoan). The latest
upsteam (currently 1.1.10) has new rules for Solo keys
(https://docs.solokeys.io/solo/udev/) and I would like to see those
included so users can avoid the need to write udev rules themselves.
** Affects: l
** Attachment added: "libu2f-host_1.1.10.orig.tar.xz.asc"
https://bugs.launchpad.net/debian/+source/libu2f-host/+bug/1831797/+attachment/5268973/+files/libu2f-host_1.1.10.orig.tar.xz.asc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Bug watch added: Debian Bug tracker #925274
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925274
** Also affects: libu2f-host (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925274
Importance: Unknown
Status: Unknown
** Attachment added: "libu2f-host_1.1.10.o
** Attachment added: "libu2f-host_1.1.10-0ubuntu1.dsc"
https://bugs.launchpad.net/debian/+source/libu2f-host/+bug/1831797/+attachment/5268975/+files/libu2f-host_1.1.10-0ubuntu1.dsc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Attachment added: "libu2f-host_1.1.10-0ubuntu1_source.changes"
https://bugs.launchpad.net/debian/+source/libu2f-host/+bug/1831797/+attachment/5268976/+files/libu2f-host_1.1.10-0ubuntu1_source.changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "libu2f-host_1.1.10-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/debian/+source/libu2f-host/+bug/1831797/+attachment/5268974/+files/libu2f-host_1.1.10-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
The autopkgtest failure was a transient network failure during the
build. After log analysis the test was re-run and is passing. I will
perform verification tests and update the bug with results in the next
few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have added two other packages to this bug.
livecd-rootfs - For the ubuntu-server and ubuntu-cpc projects a chroot
hook should be added to create the lxd system group.
cloud-init - We have the suggestion that user creation should not
initially create user groups that do not exist. You may consi
I believe this behavior is governed by cloud-init. The network config
with the mac address is created by cloud-init. I know that cloud-init
will reconfigure networking it if believes the image is launched as a
new instance. I am not aware of the expected behavior with the removal
of the primary
Dimitri, I thought we looked into plymouth and it was doing additional
setup during boot that caused us to leave it in the image. I wish I
could recall what all that way. Anyhow, if that has changed we'd be
open to it. Can you make the description a lot more descriptive and
discuss 'why' we want
Adding the cloud-images project so that a test can be added once this
change lands in livecd-rootfs
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
When running xwayland in Hirsute I am unable to share gnome-terminal
windows from Google Meet. In Google Meet running in Chrome
v89.0.4389.82 when I select the share a window I do not see my gnome-
terminal windows listed as an option to share.
Here is what I am running with
I'm using xorg because wayland has bug #1918189 (can't share terminals
in Google Meet) blocking me from using wayland as a daily driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917926
Title:
Public bug reported:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
$ loginctl
This looks to be around the time of the issue where I disabled a VPN
connection (from syslog):
Mar 8 14:11:54 splat gnome-shell[677801]: **
Mar 8 14:11:54 splat gnome-shell[677801]:
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clut
As a workaround for anyone, you can use nmcli to bring up a VPN
connection.
Run `nmcli c` to get a list of connections, once you have the name you
can enable it with `nmcli c up $name` or disable it with `nmcli c down
$name`.
--
You received this bug notification because you are a member of Ubun
@3v1n0 (Marco Trevisan) has pointed out
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a
possible fix
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the sess
** Description changed:
[Impact]
* In cloud images, the ESP is currently mounted with default (0755)
permissions. This means anyone can read the ESP partition. This can
cause security issues as sensitive data might be put in this
partition[0]
* The root filesystem part
@gjolly,
I've taken a look at the 'Where problems could occur' section of the SRU
template and I'm concerned about the risk of regression for users
altering mount options for the root file system.
My concerns involve the root filesystem line alone. I think 'discard'
is nice-to-have but not worth
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is a problem with "# Validate the zone" logic @
https://git.launchpad.net/ubuntu/+source/ec2-instance-
connect/tree/src/bin/eic_harvest_hostkeys?h=applied/ubuntu/hirsute#n92
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
ec2-instance-connect breaks during host key harvesting for instances
launched in local zones[1]. Here are is the relevant debug data:
$ systemctl is-system-running
degraded
$ systemctl list-units --failed
UNIT LOAD ACTIVE SUBDESCRIPTION
** Bug watch added: github.com/aws/aws-ec2-instance-connect-config/issues #28
https://github.com/aws/aws-ec2-instance-connect-config/issues/28
** Also affects: ec2-instance-connect via
https://github.com/aws/aws-ec2-instance-connect-config/issues/28
Importance: Unknown
Status: Unkn
And I haven't tested, but this would also fail in Wavelength zones with
names in the form `us-east-1-wl1-bos-wlz-1`. Even if instance connect
isn't supported in wavelength zones I rather not have the service fail
and mark the system status as degraded.
--
You received this bug notification becau
Wavelength zones are described @
https://aws.amazon.com/wavelength/features/#Locations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915345
Title:
eic_harvest_hostkeys fails in local zones
To mana
I've moved this to the livecd-rootfs project which builds the images and
contains the unminimize script code.
Background: Ubuntu images themselves do install recommends for packages
in the base, so re-installing recommends was seen as appropriate to make
a stock minimized image look like the unmin
I've discussed this issue in #ubuntu-devel on IRC[1] and the feedback is
that recommends, by policy, are installed for a reason and overriding
that should not be part of the unminimize tool. But for your use case
there is a solution that could meet your needs. You can set the
following in /etc/ap
Based on my prior reply I've marked this as "Won't Fix" as it doesn't
match with our plans for the unminimized script per policy on
'recommends'.
** Changed in: cloud-images
Status: New => Won't Fix
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Won't Fix
--
You received thi
Public bug reported:
[Impact]
* Focal ubuntu-cpc:minimized builds fail (see Original Description)
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated packa
** Description changed:
+ [Impact]
+
+ * Focal ubuntu-cpc:minimized builds fail (see Original Description)
+
+ [Test Case]
+
+ * detailed instructions how to reproduce the bug
+
+ * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify
** Merge proposal linked:
https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/388320
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889470
Title:
snap seed with channel break
*** This bug is a security vulnerability ***
Public security bug reported:
Failure to install new grub core to the specified device does not
correctly prevent upgrade to incompatible modules (LP: #1889509)
$ sudo debconf-get-selections |grep sda
grub-pc grub-pc/install_devices_disks_changed mu
I'm attaching a full log from the recreate that shows additional details
** Attachment added: "grub_bug_log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+attachment/5397176/+files/grub_bug_log
** Description changed:
Failure to install new grub core to the specified device
My recreate is with an AWS EC2 instance with an NVMe root device as that
is one known way to trigger an error in cloud-init cc_grub_dpkg so that
it does not write a valid debconf for grub-pc install_devices, however
this is broader than NVMe root with cloud-init.
--
You received this bug notifica
@marin-n & @hggdh2,
I see that you have both reported failures on Azure. @marin-n, from
your grub versions it looks like you're on focal. I'd like to learn
more so I can recreate and get this addressed.
I would like to find out:
- which image release and build you are running:
$ cat /etc/lsb-re
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388423
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not fai
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889470
Title:
snap seed with channel breaks ubuntu-cpc:minimized builds on focal
To manage notifications about
Public bug reported:
We have a cloud-images qualification test for google startup scripts to
ensure that cloud-init customizations are available before the user
startup script is run. That test is failing and investigation shows
that we have a functional regression from gce-compute-image-packages
** Bug watch added: github.com/GoogleCloudPlatform/guest-agent/issues #84
https://github.com/GoogleCloudPlatform/guest-agent/issues/84
** Also affects: google-guest-agent via
https://github.com/GoogleCloudPlatform/guest-agent/issues/84
Importance: Unknown
Status: Unknown
--
You r
** Description changed:
We have a cloud-images qualification test for google startup scripts to
ensure that cloud-init customizations are available before the user
startup script is run. That test is failing and investigation shows
that we have a functional regression from gce-compute-ima
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: open-vm-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: open-v
This is fixed in devel in changes that span multiple commits and this
bit was omitted from the backport of those changes (which broke focal
images)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920043
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy verification-needed-xenial
** Tags added: verification-failed verification-failed-focal
verification-failed-groovy verification-failed-xenial
--
You received this bug notification because you are a member
I have tested in AWS local zone us-west-2-lax-1a
xenial:
image: ami-008b09448b998a562
build serial: 20201014
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~16.04.2
bionic:
image: ami-02701bcdc5509e57b
build serial: 20210224
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~18.04.2
focal:
image: ami
I've left a comment in the upstream bug https://github.com/aws/aws-ec2
-instance-connect-config/issues/28#issuecomment-816650597 regarding my
SRU test feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Changed in: simplestreams
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833435
Title:
RFC: Add url/urls/mirrors attribute for product items
To manage not
g any snap via snap_preseed will evaluate the base for each snap
and seed the appropriate base. There should be no reason to explicitly
seed the 'core' snap and with snaps moving to 'core18' this will add
'core' without need.
** Affects: livecd-rootfs (Ubuntu)
8' this will add
'core' without need.
** Merge proposal linked:
https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/382041
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: livecd-rootfs (Ubuntu)
S
*** This bug is a duplicate of bug 1871919 ***
https://bugs.launchpad.net/bugs/1871919
** This bug has been marked a duplicate of bug 1871919
images with only core18-based snaps fail to build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Also affects: chromium (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869963
Title:
Unable to install chromium-browser 20.04
To manage notifi
This would be an issue for the package, I will close the track for
cloud-images.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: livecd-rootfs (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871919
Title:
images with only core18-based snaps fail to build
To manag
Public bug reported:
A user creates an ssh key and specifies it on the cmdline with 'ssh -i
new_key user@host'. The connection fails with the message "Too many
authentication failures" displayed to the user.
This would lead the user to believe that they failed to put the public
portion of the ne
** Summary changed:
- explicit key offered after all agent keys, auth fails before explicit key used
+ explicit key offered after all agent keys, auth can fail before explicit key
used
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872485
Title:
virtualbox-guest-utils fails to install on 20.04
To manage notifications about this bug go to:
https://bugs.lau
systemd-timesyncd is conflicting with virtualbox-guest-utils but
virtualbox-guest-utils isn't providing time-daemon... debian/control in
virtualbox contains:
Package: virtualbox-guest-utils
Architecture: amd64 i386
Depends: adduser,
pciutils,
virtualbox-guest-dkms (= ${source:Ver
@xnox wrote:
> It sounds like we must remove seeded snaps from our LXD images, and not
> install
> any seeded snaps inside our container. And like only install the lxd stub deb.
> Cause it looks like seeding snaps is not supported inside classic lxd
> containers.
Let's remember that these aren'
** No longer affects: cloud-images/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569237
Title:
vagrant xenial box is not provided with vagrant/vagrant username and
password
To manage notif
Eoan arm64 container on focal amd64 host does not recreate this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881217
Title:
arm64v8 focal: lintian will get stuck with it
To manage notificat
I'm moving this from cloud-images to lintian, this is not an issue
specific to the image itself.
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I added a -d flag to the invocation of perl in the shebang line of
/usr/share/lintian/frontend/dplint Here is what I got:
# lintian --help
Loading DB routines from perl5db.pl version 1.55
Editor support available.
Enter h or 'h h' for help, or 'man perldebug' for more help.
main::(/usr/bin/lin
I've opened a track for livecd-rootfs where the minimal image is defined
and I'm going to close the cloud-images portion.
But I will add that the images themselves set the expectation about what
it is to be considered minimal as:
"This system has been minimized by removing packages and content th
Speaking of cloud-images generally I propose the following:
* Images in the ubuntu-cpc project by default should boot with an initramfs.
* Revert the livecd-rootfs change which "Unconditionally set
GRUB_FORCE_PARTUUID in cloud images"
* Images with custom kernels can boot without an initram
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863024
Title:
SRU: bootable buildd images for all releases
To manage notificatio
** Description changed:
+ [Impact]
+
+ * Building an ubuntu-cpc minimal image by default would have no snaps
+ installed. When a binary hook seeds a snap that has a core18 base
+ the build will fail when calling 'snap debug validate-seed' because
+ the snapd snap is missing.
+
+ * Additionall
** Description changed:
[Impact]
- * Building an ubuntu-cpc minimal image by default would have no snaps
+ * Building an ubuntu-cpc minimal image by default would have no snaps
installed. When a binary hook seeds a snap that has a core18 base
the build will fail when calling 'snap debu
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863024
Title:
SRU: bootable buildd images for all releases
To manage notificatio
** Also affects: livecd-rootfs (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Eoan)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: livecd-rootfs (Ubuntu Eoan)
Status: New => In Progress
--
You received th
This is great and I'd love to see us move to this from what we are
doing. Parallel builds for the ubuntu-cpc project have an absolute
requirement for cohort support; so that requirement will need to be
driven with snapd.
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf'
for use in Ubuntu cloud images. I wanted to add a config file and see
if I had done things correctly. I assumed that the files were sourced
lexographically (based on use of glob() in readconf.h) so that I
I have used livecd-rootfs 2.620.2 from proposed to build ec2 and gce
images. EC2 currently has a mix of core and core18 based snaps while
GCE has only core18 based snaps. I confirmed that snapd was seeded when
core18 was the only core snap present. Boot testing each of these
images confirmed tha
@colin-king, Can we get that config option added for this kernel?
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Drat, I see that now in sshd_config. I think I tried searching for
"first" and maybe by that point I was just looking at sshd's man page.
Okay, well then this is fine for me It's documented and stable. We
can comfortably make this change for cloud-images. Thanks Colin!
** Changed in: openss
Public bug reported:
A xenial image that preseeds a snap based on core18 will end up with
core instead and preseeding on boot will fail.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bu
** Description changed:
- A xenial image that preseeds a snap based on core18 will end up with
- core instead and preseeding on boot will fail.
+ [Impact]
+
+ * A xenial image that preseeds a snap based on core18 will
+end up with core instead and preseeding on boot will fail.
+
+
+ [Test
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Xenial)
Assignee: (unassigned) => Robert C Jennings (rcj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've looked at the ubuntu-image autopkgtest failure on ppc64el. The
failure was a network timeout on a 'pip' command. Re-running the test
has passed and this seems acceptable. I will continue testing the SRU
per the testcase in the template and update this bug.
--
You received this bug notific
Built ubuntu-cpc images and tested that images with core or core18 based
snaps build as expected. The core snap was pulled in for snaps without
an explicit base while core18 & snapd were pulled in for snaps with an
explicit core18 base, and were there were both we have core and core18
without snap
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875882
Title:
debconf attempts interactive configuration; breaks Docker image builds
To mana
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875068
Title:
Fo
Adding 'grub' project to verify and provide assistance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885571
Title:
Can't set boot kernel in GRUB on focal image
To manage notifications about this
On Thu, Apr 30, 2020 at 2:50 PM Steve Langasek
wrote:
> On Thu, Apr 30, 2020 at 05:27:49PM -, Dimitri John Ledkov wrote:
> > Looking at seeds, it seems like maybe "cloud-image" should have fdisk
> > seeded in both focal & groovy.
>
> I think this belongs in the server seed, not just cloud-ima
I've proposed https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-
rootfs/+merge/366862 for this issue for master as well as
https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-
rootfs/+merge/366863 for disco (I'll add an SRU template as well).
** Description changed:
+ [Impact]
+
Public bug reported:
[Impact]
The following targets have livecd.ubuntu-cpc.manifest (and
livecd.ubuntu-cpc.ext4) which differ in some way from the 'all'
target. They are all missing grub-efi and other modifications:
root-dir
squashfs
tarball
These targets do not depend on the 'disk-image' targe
mwhudson has requested that the make-hooks command be amended to allow
comments in series files and these series files have comments added to
the effect "# Ensure livecd.ubuntu-cpc.ext4 is consistent with other
targets"
--
You received this bug notification because you are a member of Ubuntu
Bugs
I've pushed a commit to each branch to support comments and added them
for the changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827426
Title:
ubuntu-cpc: parallel build targets produce differ
This is as expected, the root partition in the registered image will not
match the size of the disk that is deployed. It will be large enough to
contain the root partition and provide some blank space. This is by
design and allows VMs to be started with variable size disks. This is
seen early in
I have built cosmic, bionic, and xenial images in GCE with the packages
from -proposed and tested that console setup is functioning correctly
with the change. Thanks. I will be marking each of the releases as
tested.
** Tags removed: verification-needed verification-needed-bionic
verification-n
Streams uses distro-info-data which still contains an EOL date of the
17th which lp:simplestreams uses to determine the value of 'supported'
in streams. Adding distro-info package.
** Also affects: distro-info (Ubuntu)
Importance: Undecided
Status: New
** Also affects: simplestreams
Also adding the simplestreams project as our cloud-images streams are
generated by that code and 'supported' was added at the request of
multipass and is currently defined by the distro-info supported field.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
We have locally corrected the date in /usr/share/distro-info/ubuntu.csv
and streams are being regenerated, meaning we will have trusty marked as
supported until April 25, 2019 if further changes are not made.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Marking fix-released for cloud-images as streams now correctly report
trusty as supported. This was through a manual distro-info-data change
as noted in comment #3 and other changes in streams and distro-info data
are needed.
Next actions:
* distro-info-data needs an update in precise ESM to add
I've marked this as verification failed as the build is not fixed by
this change. The livecd-rootfs change looks safe enough but does not
address root cause and as such we can not complete a build to verify
this change doesn't break things further; all we can say is that it
doesn't address root ca
If I understand launchpad-buildd[1] correctly, snapd will be installed
regardless of livecd-rootfs' dependencies. The fix needs to be in snapd
for powerpc on xenial. I confirmed that with a -proposed build with
livecd-rootfs 2.408.50 we will still try to install snapd and fail the
build as before
I have built using --proposed for powerpc and amd64 using the ubuntu-cpc
project. I'm marking this as verification done.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-needed-done
--
You received this bug notification because you ar
** Tags removed: verification-needed-done
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830823
Title:
Ubuntu image builds broken for powerpc on xenial
To ma
Public bug reported:
In parallel builds where a list of image targets are provided the build
may produce binaries that are not part of the named set of targets but
are created by series dependencies. These implicitly created binaries
may be generated by multiple builds but are unused as our conve
I have attached an MP. In testing with the ubuntu-cpc project on eoan,
when building the amd64 qcow2 image target we eliminate 1.38GiB in
unnecessary transfer and storage. This saves a lot of time, storage,
and transit for each parallel build on each architecture (so it adds up
fast).
--
You re
101 - 200 of 609 matches
Mail list logo
