@slashd thanks for the pointers.
Yesterday/today I worked on understanding and providing a workaround for this,
but a more complete solution (more updates to secure-boot related packages)
is already in the works (in cyphermox's PPAs) and should be rolled out soon,
according to him.
Once that
The secure boot packages on trusty-proposed are now correct (LP: #1708245),
and the d-i rebuild on amd64 is in progress (verified successfully on PPA).
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Hi Eric,
This is the v3 debdiff with the patches updated to apply with no offset
messages per your request.
Thanks,
Mauricio
--
Applying patch debian/patches/1008-vf_trust_dddf1b44126e.patch
patching file include/linux/if_link.h
Applying patch debian/patches/1009-vf_trust_b6d77d9ee312.patch
Oops, I'll add the Debina/Ubuntu-Bug: DEP-3 tags in the debdiffs.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1803385
Title:
fetch-url does not use --no-check-certificate on HTTP to
Er, I mean, the right LP bug numbers in changelog,
and fix the version suffixes for Bionic and Cosmic,
as reported by slashd in IRC (thanks!)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Eric,
Just updated the attached debdiffs w/ the fixes for the points listed.
Thanks for reviewing; nice catch in the Cosmic/Bionic version suffixes
(I have verified them with dpkg --compare-versions, all good this time).
cheers,
Mauricio
--
You received this bug notification because you are a
** Patch added: "bionic_di-utils_httpsredir.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1803385/+attachment/5212731/+files/bionic_di-utils_httpsredir.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed
** Patch added: "trusty_di-utils_httpsredir.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1803385/+attachment/5212733/+files/trusty_di-utils_httpsredir.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed
** Patch added: "cosmic_di-utils_httpsredir.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1803385/+attachment/5212730/+files/cosmic_di-utils_httpsredir.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed
** Patch removed: "disco_di-utils_httpsredir.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1803385/+attachment/5212693/+files/disco_di-utils_httpsredir.debdiff
** Patch removed: "cosmic_di-utils_httpsredir.debdiff"
** Changed in: systemd (Ubuntu)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Package Contents :: Xenial
==
No regressions in ca-certificate DEB file
after the changes to build the UDEB file.
The only difference is due to the changes
in changelog file and package version.
dpkg-deb -c (content listing)
---
$ dpkg-deb -c
Testing :: Trusty
=
original
wget http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main
/installer-amd64/20101020ubuntu318.44/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
~ # cat /etc/default-release
trusty
~ # ls -d /usr/lib/ssl/certs
ls:
Testing :: Xenial
=
original
wget http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main
/installer-amd64/20101020ubuntu451.26/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
~ # cat /etc/default-release
xenial
~ # ls -d /usr/lib/ssl/certs
ls:
** Patch added: "lp1807023-debian-installer-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220102/+files/lp1807023-debian-installer-xenial.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Patch added: "lp1807023-debian-installer-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220104/+files/lp1807023-debian-installer-trusty.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Description changed:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that
Package Contents :: Trusty
==
No regressions in ca-certificate DEB file
after the changes to build the UDEB file.
The only difference is due to the changes
in changelog file and package version.
dpkg-deb -c (content listing)
---
$ dpkg-deb -c
** Patch added: "lp1807023-ca-certificates-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220173/+files/lp1807023-ca-certificates-xenial.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Patch added: "lp1807023-ca-certificates-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220172/+files/lp1807023-ca-certificates-trusty.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
Verification :: disco-proposed
---
Okay, not strictly required as not yet a Stable Release, but doing anyway.
Successful.
$ wget http://archive.ubuntu.com/ubuntu/dists/disco-proposed/main
/installer-amd64/20101020ubuntu560/images/netboot/ubuntu-
Verification :: bionic-proposed
---
Successful.
$ wget http://archive.ubuntu.com/ubuntu/dists/bionic-proposed/main
/installer-amd64/20101020ubuntu543.4/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
$ virt-install \
--name bionic \
--vcpus 2 \
Verification :: cosmic-proposed
---
Successful.
$ wget
http://archive.ubuntu.com/ubuntu/dists/cosmic-proposed/main/installer-amd64/20101020ubuntu557.1/images/netboot/ubuntu-installer/amd64/{linux,initrd.gz}
$ virt-install \
--name cosmic \
--vcpus 2 \
** Patch added: "lp1807023-ca-certificates-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220103/+files/lp1807023-ca-certificates-trusty.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Patch added: "lp1807023-ca-certificates-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220101/+files/lp1807023-ca-certificates-xenial.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Patch added: "cosmic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5267256/+files/cosmic_partman-iscsi.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Hi Eric,
Nice catch. Sorry about that!
Sure, just attached the partman-iscsi debdiffs with the LP bug mentioned
in changelog.
Thanks,
Mauricio
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
verification done for disco/hw-detect.
disk-detect found the iscsi target/lun configured in ibft.
$ wget http://boot.ipxe.org/ipxe.lkrn
$ wget
http://archive.ubuntu.com/ubuntu/dists/disco/main/installer-amd64/20101020ubuntu570/images/netboot/ubuntu-installer/amd64/{linux,initrd.gz}
$ python3
verification done for disco/partman-iscsi.
Use of partman-iscsi/iscsi_auto correctly writes /etc/iscsi/iscsi.initramfs
with either ISCSI_AUTO=true or iSCSI LUN details with the right MAC address.
~ # grep 'retrieving partman-iscsi' /var/log/syslog
Jun 6 14:04:03 anna[1582]:
verification done for cosmic/partman-iscsi.
Use of partman-iscsi/iscsi_auto correctly writes /etc/iscsi/iscsi.initramfs
with either ISCSI_AUTO=true or iSCSI LUN details with the right MAC address.
~ # grep 'retrieving partman-iscsi' /var/log/syslog
Jun 6 14:20:51 anna[1521]:
verification done for bionic/partman-iscsi.
Use of partman-iscsi/iscsi_auto correctly writes /etc/iscsi/iscsi.initramfs
with either ISCSI_AUTO=true or iSCSI LUN details with the right MAC address.
~ # grep 'retrieving partman-iscsi' /var/log/syslog
Jun 6 15:01:20 anna[1605]:
Dan,
Very good point.
Access by IP address didn't work before -- I just checked w/ Xenial / OpenSSL
1.0.0,
and it fails with certification verification error too.
IIUIC this seems reasonable - as the default certificate is the only thing the
server
could send to the client without SNI (which
For documentation purposes,
Test with an IP address should not send SNI per the patch,
so it should fail with the certificate verification error:
$ mailutil check {imap.gmail.com:993/imap/ssl}INBOX
{cb-in-f108.1e100.net/imap} username:
$ host imap.gmail.com | grep -m1 address
Verification done for bionic:
---
'mailutil check' successfully connects to gmail,
and prompts for an username, using openssl1.1.1.
$ lsb_release -cs
bionic
$ sudo apt-get install libc-client2007e uw-mailutils
...
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64
Thanks for verifying bionic-proposed @pataquets!
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
Status in asterisk
Attaching updated debdiff for asterisk on Eoan,
which changed versions while we waited uw-imap.
** Patch removed: "asterisk_eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/uw-imap/+bug/1834340/+attachment/5282373/+files/asterisk_eoan.debdiff
** Patch added: "asterisk_eoan.debdiff"
Eric, thanks for reporting that.
I couldn't reproduce the build failure on LXC with apt dist-upgrade on
xenial-updates nor xenial-proposed, and it built successfully on PPAs a
while ago (for the test packages), so it seems something changed in the
PPA builders.
I'll investigate this as per our
The problem is reproducible in the sbuild-launchpad-chroot for xenial/amd64,
using the source package for util-linux currently in xenial-updates
(i.e., no regression from debdiff, as expected since changes/error are
unrelated)
The minimal command-line for that is:
$
s/this is bug/this is _similar_ to/
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842437
Title:
Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
with udev
Status
Ah, this is bug 1843674, checking for similar fixes.
(thanks Matthew Ruffell for pointing it out on IRC.)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842437
Title:
Xenial: libblkid: fix
Workaround of disabling the 4 tests in the 'script' component
(which calls openpty() upfront and thus cause the failure)
makes the test-suite finish successfully.
$ ./tests/run.sh \
--srcdir=/build/util-linux-kzgHhT/util-linux-2.27.1 \
--builddir=/build/util-linux-kzgHhT/util-linux-2.27.1 \
The reporter confirmed the boot problem doesn't happen anymore.
Moving forward with the SRU.
** Changed in: util-linux (Ubuntu Xenial)
Assignee: Guilherme G. Piccoli (gpiccoli) => Mauricio Faria de Oliveira
(mfo)
** Tags added: sts
--
You received this bug notification because
Eric, thanks! Really appreciate your help debugging this issue.
Per Colin's comment, he mentions on #launchpad-ops (internal)
when there are launchpad chroot changes -- so we can confirm
it's been updated after the package becomes Fix Released.
--
You received this bug notification because you
The real fix for the openpty() problem on Launchpad xenial buildd
is in livecd-rootfs currently in xenial-proposed, and is verified.
(LP 1844504 comment 15)
Once the Launchpad builders are updated with that, we can proceed
with another build attempt, and hopefully move this SRU forward.
Thanks
The autopkgtests regression on docker.io are unrelated to this change.
The failure is on debian/tests/basic-smoke; it happens because
'debootstrap stable ' fails the gpg verification of the Release
file -- the keys used for the Buster stable release are not found in
Xenial's
The remaining autopkgtests regressions (nplan/amd64 and gvfs/s390x) are
also unrelated to this change.
- nplan/amd64 passed with 3 retests:
Before:
test_mix_bridge_on_bond (__main__.TestNetworkManager) ... FAIL
...
integration.py FAIL non-zero exit status 1
After:
Verification done on xenial-proposed.
With the new systemd and dbus packages, there are no leaked sessions
after the test-case of ssh loop.
The autopkgtests regressions reported previously are unrelated to this
change (comments #11 to #16).
cheers,
Mauricio
Setup
---
$ sudo snap install
For documentation purposes,
The systemd upload for this LP bug also resolves LP bug 1847512
(xenial: leftover scope units for Kubernetes transient mounts).
Verification steps posted on that bug.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed
** Description changed:
[Impact]
* After an update of ghostscript but not cups-filters
(which is possible, including via Landscape tooling)
users may hit errors printing PDF files (LP#1828401).
* Landscape allows packages updates to USN-only thus
ghostscript is
** Description changed:
[Impact]
* After an update of ghostscript but not cups-filters
- (which is possible, including via Landscape tooling)
+ (which is possible; eg unattended-upgrade/landscape)
users may hit errors printing PDF files (LP#1828401).
- * Landscape allows
The approach to fix/deliver this is under discussion for a bit.
We'll move forward once that's more clearly defined.
** Patch removed: "lp1848210_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297380/+files/lp1848210_bionic.debdiff
** Patch
Status: New => Invalid
** Changed in: cups-filters (Ubuntu Bionic)
Status: New => Invalid
** Changed in: cups-filters (Ubuntu Xenial)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: cups-filters (Ubuntu Bionic)
Assignee: Mauricio
** Patch added: "lp1848210_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297502/+files/lp1848210_bionic.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
After discussing this with Eric (slashd) and Marc (mdeslaur),
it seems like the Breaks: approach is indeed the way to go.
Nonetheless, it doesn't warrant an USN notice (security-only),
which is the bit that could make Landscape (problem trigger)
to pick up the new ghostscript fix then update
** Description changed:
[Impact]
* After an update of ghostscript but not cups-filters
-(which is possible)
users may hit errors printing PDF files (LP#1828401).
+
+ * This is possible as Landscape does not consider the
+-security pocket (has both ghostscript/cups-filters)
** Description changed:
[Impact]
* After an update of ghostscript but not cups-filters
- (which is possible; eg unattended-upgrade/landscape)
+(which is possible)
users may hit errors printing PDF files (LP#1828401).
-
- * Landscape and unattended-upgrade allows packages
-
Summary of autopkg regressions
systemd:
- most tests passed on retest (thanks ddstreet)
- still failing: gvfs/s390x, docker.io/all archs but armhf, nplan/amd64
dbus:
- no new failures.
Looking at the pending failures/regressions.
systemd
--
umockdev/0.8.11-2 (i386)
passed on retest.
And this debdiff / util-linux on xenial builds fine again!
Built on all architectures on PPA [1].
cheers,
Mauricio
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1842437
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Eric,
The fix to xenial livecd-rootfs / launchpad buildd chroot has been
rolled out.
I just confirmed that /dev/ptmx is OK with a test package build on
Launchpad PPA.
...
dh_clean
# Check /dev/ptmx|pts/
ls -l /dev/ptmx
crw-rw-rw- 1 root root 5, 2 Oct 4 08:13 /dev/ptmx
ls -l
SRU team,
The autopkgtests regressions reported for the three releases
(xenial/bionic/eoan)
were all* transient issues resolved with re-runs (see 'pass' status records
below).
(*) The only the exception (not a transient issue) is gnocchi/bionic/armhf,
which is _not_ a regression either as the
xenial:
- nplan/0.32~16.04.7 (amd64)
- 0.32~16.04.7util-linux/2.27.1-6ubuntu3.10 2020-01-28 11:12:12 UTC
0h 24m 52s mfo pass
- mysql-5.7/5.7.28-0ubuntu0.16.04.2 (i386, ppc64el, amd64)
- (new version in -updates fixed issues.)
- 5.7.29-0ubuntu0.16.04.1
Verification done on bionic-proposed.
Now libblkid1 detects only the bcache superblock and prints udev/uuid variables.
$ lsb_release -cs
bionic
$ DISK_IMG=disk.img
$ rm -f $DISK_IMG
$ dd if=/dev/zero of=$DISK_IMG bs=1G count=0 seek=1
$ BACKING_DEV=$(sudo losetup --find --show $DISK_IMG)
$ sudo
Verification done on xenial-proposed.
Now libblkid1 detects only the bcache superblock and prints udev/uuid variables.
$ lsb_release -cs
xenial
$ DISK_IMG=disk.img
$ rm -f $DISK_IMG
$ dd if=/dev/zero of=$DISK_IMG bs=1G count=0 seek=1
$ BACKING_DEV=$(sudo losetup --find --show $DISK_IMG)
$ sudo
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash and failure installing focal
Status in subiquity:
New
Status in curtin package in
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863232
Title:
daemon rotates socket on restart
Status in mod-wsgi package in Ubuntu:
Fix Released
Status in
Dariusz,
As part of my learning homework to be able to
technically review the patch in this proposal,
I came across three things that may be useful
for the bug description/SRU template, so I'll
just add them, if you don't mind.
1) Understanding the scenario where the bug
happens (mod-wsgi
Steps to reproduce/verify on Bionic:
===
Similarly to steps described for Xenial.
Skipping the identical steps.
$ lxc launch ubuntu:bionic lp1863232b
$ lxc exec lp1863232b -- su - ubuntu
One connection/Two requests (added timestamps to check timeout values)
---
$ (cat http-request; sleep 1;
** Patch added: "lp1863232_xenial_mod-wsgi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1863232/+attachment/5329327/+files/lp1863232_xenial_mod-wsgi.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug
** Patch added: "lp1863232_bionic_mod-wsgi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1863232/+attachment/5329326/+files/lp1863232_bionic_mod-wsgi.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug
Steps to reproduce/verify on Xenial:
===
References:
-
https://modwsgi.readthedocs.io/en/develop/user-guides/quick-configuration-guide.html
-
https://modwsgi.readthedocs.io/en/develop/user-guides/quick-configuration-guide.html#delegation-to-daemon-process
-
Attaching the updated debdiffs for reference.
They build successfully on a PPA for all architectures,
and have been used on steps to reproduce/verify (below.)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Hi Dariusz,
I reviewed the debdiffs, they look good overall.
I just had some minor changes to reflect review
practices/comments that I have been thru myself:
- Nice catch on updating the Maintainers field.
- Changelog order of patch file/description:
I changed to file first, description
Uploaded changes to B/X.
There are no other mod-wsgi uploads in the unapproved queue nor waiting
in -proposed/pending SRU.
mod-wsgi (source)
4.5.17-1ubuntu1 mainpython medium ubuntu-server
Proposed56 seconds ago
mod-wsgi (source)
4.3.0-1.1ubuntu1
** Description changed:
[Impact]
- * Lack of option for disabling wsgi socket rotation leads to errors on
graceful restarts, making them not as graceful.
- * This change introduces a new config option WSGISocketRotation that allows
to disable the rotation.
+ * Lack of option for
LP#1845529 is now fix released (thanks @sil2100), and the SRUs for E/B/X have
been uploaded.
(The SRU for D is skipped as D will be EOL in 7 days, the time needed to stay
in -proposed.)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the
The uploads to stable releases are blocked on LP#1845529 currently in
eoan-proposed.
It was pending analysis of autopkgtest failures as well, and I provided those
today.
(cyphermox removed the tag 'verification-needed' from that bug, so maybe it'll
move.)
--
You received this bug notification
The autopkgtest failures for focal are unrelated to this upload.
- piuparts/1.1.0:
There's changes from piuparts 1.1.0 to 1.1.1 (released a few hours ago)
that resolved the issues, as seen in the autopkgtests page for piuparts.
Requested re-runs.
- openjdk:
The failing test timed-out on armhf
The only autopkgtest 'regression' is openjdk-8/8u252-b07-1/armhf,
which is a flaky test. Triggering a re-run. Error in test logs:
> jdk FLAKY timed out
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
The autopkgtests failures for sbuild on focal-proposed
are all addressed/passed; the Pending SRU page is clear
for focal/deboostrap. [1]
Thanks @mruffell for the ping to re-trigger the sbuild
failed tests (that debootstrap groovy) now that groovy's
procenv has the fix for GCC 10.
cheers,
Hey Alex, thank you very much for your prompt review.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Thanks for verifying focal-proposed (and adding the tag.)
Oh, I forgot to mark Groovy as Fix Released on comment #15; doing it
now.
** Changed in: util-linux (Ubuntu Groovy)
Status: Fix Committed => Triaged
** Changed in: util-linux (Ubuntu Groovy)
Status: Triaged => Fix Released
Groovy now has the fix released in util-linux 2.36-2ubuntu1. Focal can
now move on.
I've changed the debdiff slightly on the DEP3 headers and version
number, small nitpicks.
The package builds fine on all architectures in a PPA, and testing is
successful:
focal-release / fail:
$ dpkg -s
Uploaded to Focal.
Seyeong, could you please update the Test Case section of the SRU template
to reflect the usage of Ubuntu commands and not upstream/built commands?
Thanks,
Mauricio
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug
This should be fixed with rsyslog 8.2001.0-1ubuntu1.1 in focal-updates.
** Changed in: rsyslog (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Autopkgstests failures:
- gfs2-utils/ppc64el: unrelated; I'll take a look (it held groovy's proposed
migration weeks ago.)
- systemd: likely unrelated, see bug 1892358 (success rate dropped)
- tracker: flaky; now passing.
- kopanocore: flaky; now passing.
--
You received this bug notification
Verification done for bionic:
bionic-updates:
- boots fine w/ console=ttyS0, can ssh in 10 seconds.
- boot fails w/ console=ttyS1, cannot SSH, qemu on 100% CPU (initramfs-tools
looping)
bionic-proposed:
- boots fine w/ console=ttyS0, can ssh in 10 seconds. (no regression)
- boots fine w/
Hi Łukasz,
Thanks for accepting initramfs-tools for now; it's much appreciated.
I'm not sure the security team reviewed this; but I can't confirm.
I'll try to find a reviewer there, to check the concerns you have.
Could you please confirm/correct/add the concerns/review points?
1) Behavior
This has been verified successfully on Bionic by @jvosburgh
on a (complex) internal test setup for 3-netdev naming work.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Patch added: "focal_cryptsetup_lp1879980_V3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+attachment/5413626/+files/focal_cryptsetup_lp1879980_V3.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to
Uploaded initramfs-tools to Bionic.
Attaching the updated debdiff for reference.
(Rebased on top of the more recent -updates.)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1879980
Title:
Uploaded initramfs-tools to Bionic.
Attaching the updated debdiff for reference.
(Rebased on top of the more recent -updates.)
** Patch added: "bionic_initramfs-tools_lp1879980_V3.debdiff"
** Patch added: "bionic_initramfs-tools_lp1879980_V3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5413639/+files/bionic_initramfs-tools_lp1879980_V3.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
Uploaded initramfs-tools to Bionic.
Attaching the updated debdiff for reference.
(Rebased on top of the more recent -updates.)
** Tags added: sts-sponsor-mfo
** Patch added: "bionic_initramfs-tools_lp1879980_V3.debdiff"
** Patch added: "bionic_initramfs-tools_lp1879980_V3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+attachment/5413638/+files/bionic_initramfs-tools_lp1879980_V3.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
Verification done for xenial:
xenial-updates:
- boots fine w/ console=ttyS0, can ssh in 10 seconds.
- boot fails w/ console=ttyS1, cannot SSH, qemu on 100% CPU (initramfs-tools
looping)
xenial-proposed:
- boots fine w/ console=ttyS0, can ssh in 10 seconds. (no regression)
- boots fine w/
In the benefit of the initramfs-tools upload to move on:
I have verified that it has no regressions with current
cryptsetup in bionic-updates and works as expected with
the patched version (in upload queue, not -proposed yet.)
Verification details in the next comment and detailed
topology and
** Attachment added: "lp1879980 verification-bionic.log"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+attachment/5414278/+files/lp1879980%20verification-bionic.log
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the
1) There are no changes with the cryptsetup in bionic-updates.
This is expected, because the changes in initramfs-tools
are gated by a file introduced in the patched cryptsetup.
Thus no regression from the initramfs-tools side.
...
And, additional testing with the _patched_ cryptsetup,
just in
Hi Guilherme,
I can handle that while you're out.
cheers,
Mauricio
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is
Hi Eric,
I just updated the changelog with a more detailed description per file.
If it looks good to you for Groovy I'll update the stable releases too.
Thanks!
Mauricio
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
1 - 100 of 299 matches
Mail list logo
