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
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 \
s/this is bug/this is _similar_ to/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842437
Title:
Xenial: libblkid: fix false-positive/misdetection of nilfs2
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 Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842437
Title:
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:
$
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 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
-Xenial supported releases have it.
** Patch added: "lp1842437_util-linux.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1842437/+attachment/5287043/+files/lp1842437_util-linux.debdiff
** Changed in: util-linux (Ubuntu Xenial)
Assignee: Mauricio Faria de Oli
This problem can be reproduced with a synthetic test case.
Essentially,
1) create a zero-filled disk image with one partition.
2) format it as ext4.
3) insert the nilfs2 magic bytes at the right position.
4) insert the nilfs2 bytes field at the right position.
--
Step 1)
# dd
modified package:
# dpkg -s libblkid1 | grep ^Version:
Version: 2.27.1-6ubuntu3.8+test20190903b1
# LIBBLKID_DEBUG=all udevadm test-builtin blkid /sys/block/loop0/loop0p1
...
7289: libblkid: LOWPROBE: [28] ext4:
7289: libblkid: LOWPROBE:
udev builtin blkid ignores the checksum error:
nilfs_valid_sb() @ nilfs.c:96
return blkid_probe_verify_csum(pr, crc, le32_to_cpu(sb->s_sum));
blkid_probe_verify_csum() @ probe.c:1576-1687
if (csum != expected) {
...
DBG(LOWPROBE, ul_debug(
with debug we could confirm that other fields in the backup superblock are
invalid,
such as the device size, which was not checked for not being a whole-disk
device,
and the bytes length, which is greater than the superblock structure size (8243
vs 1024).
so, the fix to check for the bytes
original package:
# dpkg -s libblkid1 | grep ^Version:
Version: 2.27.1-6ubuntu3.8
# LIBBLKID_DEBUG=all udevadm test-builtin blkid /sys/block/loop0/loop0p1
...
4924: libblkid: LOWPROBE: [28] ext4:
4924: libblkid: LOWPROBE: reuse
Problem:
- the ext4 filesystem is detected correctly at the beginning of the partition.
- the nilfs2 filesystem is detected incorrectly at the end of the partition.
- the nilfs2 checksum is invalid, but that is ignored by udev builtin blkid.
- the detection of more than one filesystems causes an
: util-linux (Ubuntu Xenial)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Also affects: util-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu)
Status: New => Fix Released
** Chan
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 :: 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 \
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 \
** 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 Ubuntu
Touch seeded
** 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 Ubuntu
Touch seeded
The ca-certificates fix for Xenial and Trusty
include the changes to build the (new) udeb.
The normal deb package has been verified for
regressions (next comments) and it is correct,
with no functional changes whatsoever.
--
You received this bug notification because you are a member of Ubuntu
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
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
** 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
** 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 Ubuntu
Touch seeded
** 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 Ubuntu
Touch seeded
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-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 Ubuntu
Touch seeded
** 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 Ubuntu
Touch seeded
autopkgtests for open-vm-tools,
failures in amd64 and i386.
These are consistently failing since May 14th, 2018
for a lot of other packages, thus not a change from
this upload.
Thanks,
Mauricio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
autopkgtests for ubuntu-fan
(triggered by this iproute2 upload)
The test failure in ubuntu-fan's lxd test (the thing
that is failing in these autopkgtests) does look flaky.
Looking at autopkgtest logs for ubuntu-fan on xenial, there's a series of
retriggers
for the _same_ version of docker.io
Verification successful on xenial-proposed.
Updated verification tags.
Steps
=
Setup 1) Enable xenial-proposed and install the iproute2 package:
---
$ echo 'deb http://archive.ubuntu.com/ubuntu xenial-proposed main restricted' |
sudo tee /etc/apt/sources.list.d/xenial-proposed.list
deb
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
Hi Eric,
Thanks for reviewing.
This is the debdiff v2, addressing the points you brought up (numbered patches,
bug-ubuntu dep3 tag).
cheers,
Mauricio
** Patch removed: "iproute2_xenial_vf-trust.debdiff"
** Patch added: "iproute2_xenial_vf-trust.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207579/+files/iproute2_xenial_vf-trust.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
[Impact]
* An VM's VF cannot receive IPv6 multicast traffic
from other VMs' VFs in the same Mellanox adapter
_if_ its VF trust setting is not enabled, and on
Xenial currently iproute2 _cannot_ enable it.
* This breaks IPv6 NDP (Neighbor Discovery Protocol)
in
Positive test results with xenial-proposed have also been verified by a
company interested in this fix, in their scenario/application.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Verification done on Xenial.
Changing verification tags.
--
Testcase)
$ cat <"
$ dpkg -s systemd | grep ^Version:
Version: 229-4ubuntu21.5
$ sudo systemctl start fail-on-restart
$ systemctl status -n0 fail-on-restart
fail-on-restart.service
Loaded: loaded
** 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 Ubuntu
Touch seeded packages, which is subscribed to s
** Patch added: "systemd-xenial_restart-failed.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795658/+attachment/5195852/+files/systemd-xenial_restart-failed.debdiff
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo
More details on the verification of test package from Launchpad PPA)
---
Test-case)
$ cat <
Sep 29 10:59:00 havers systemd[1]: Started fail-on-restart.service.
Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Main process
exited, code=exited, status=1/FAILURE
Sep 29 10:59:00 havers
tps://github.com/systemd/systemd/issues/3166
[3] https://launchpad.net/~mfo/+archive/ubuntu/sf199312
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
To
** Changed in: systemd (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1668535
Title:
Ubuntu17.04-Failed to
Thanks, @cyphermox and @smb.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1673350
Title:
dm-queue-length module is not included in installer/initramfs
Status
Patch verification on 16.04:
---
multipath-tools source package:
# sed -n '/vendor.*XtremIO/,/selector/ p' libmultipath/hwtable.c
.vendor = "XtremIO",
.product = "XtremApp",
.features = DEFAULT_FEATURES,
It's possible to reproduce this problem in a qemu-kvm guest,
with an emulated disk: force the queue-length path selector.
# name=mfo-1704
# disk=/var/lib/libvirt/images/$name.qcow2
# iso=/var/lib/libvirt/images/zesty-server-ppc64el.iso.2017-03-14
# qemu-img create -f qcow2 $disk 128g
#
Error logs:
--
This error log is seen in the installer, and multipath devices are not
created for such storage system:
...
Mar 14 06:41:54 kernel: [ 0.00] Kernel command line: tasks=standard
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
/install
-
modules udeb) in addition to 'multipath-tools'
** Description changed:
- == Comment: #0 - Mauricio Faria De Oliveira <mauri...@br.ibm.com> -
2017-03-15 09:01:18 ==
---Problem Description---
dm-queue-length module is not included in installer/initramfs
On Ubuntu, multipath devices
Patch verification on 17.04:
---
Before:
# dpkg -s multipath-tools-boot | grep ^Version:
Version: 0.6.4-3ubuntu1
# lsinitramfs /boot/initrd.img | grep dm-queue-length
#
After:
# dpkg -i multipath-tools*.deb kpartx*.deb
# dpkg -s multipath-tools-boot | grep ^Version:
For easier reading, I'll break the description field apart,
to split the comments that got merged there, into actual comments at Launchpad.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Christian,
Thanks for handling this.
> But the more that are affected the more I think then general solution
in lightdm would be the right thing to do.
Yes, that's my interpretation too -- and it was my impression from the
beginning, with your report/analysis, as I couldn't find anything we
Hi Christian,
Thanks for handling it to xenial-updates.
BTW, that point about the package to make the point release ISO is so
that people who use the ISO as package repository (which happens in some
scenarios like xCAT clusters), and not always get more updates from the
internet, can get it.
Okay, thanks again for all you (excellent) support on all this,
Christian.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
https://bugs.launchpad.net/bugs/1637601
Title:
UbuntuKVM: migration using
Okay, great! Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
https://bugs.launchpad.net/bugs/1637601
Title:
UbuntuKVM: migration using NFS mount fails #190
Status in libvirt:
Fix
Christian,
For your consideration...
Since this patch is mainly targeted at first-time installations of libvirt (so
that the uid assignment can occur), it would be great if it can make 16.04.2
now that the date slipped 2 weeks (per the public release schedule), if at all
possible... so that
Hi Christian,
Here's the patch for libvirt in Xenial.
It's the very minimal changes required from Zesty/Debian in order to set the
UID (and document the change in the NEWS file).
I didn't backport the debconf warning stuff as it's not essentially required.
Hopefully this is simple/conservative
Verification steps with just attached patch.
Test 1) new user, uid available
Result) libvirt-qemu uid is set to 64055
# id libvirt-qemu
id: ‘libvirt-qemu’: no such user
# getent passwd 64055
#
# dpkg -i
Christian,
Alright!
I'll provide the up-to-date backport for libvirt in Xenial and the SRU template.
Per Colin's comment #21 it's not required to SRU base-passwd:
> [snip] you should definitely not waste time SRUing base-passwd [snip]
Thanks.
--
You received this bug notification because you
> I still remember the internal process and its mirroring :-)
I got you now.. ;-) [1]
BTW, just checked in BTS how Guido would like to proceed w/ this one
since the last patch (v3) submission ~1.5 weeks ago. Waiting.
[1] https://insights.ubuntu.com/author/paelzer/
--
You received this bug
Hi @Christian.
Cool. good news.
BTW, I have to post some status/progress updates in this bug for
internal tracking by other people; not meant at you. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
Submitted patch v2 for Debian, addressing changes requested by Guido.
(but not yet the getent/adduser concern of debian bug 621833, which I decided
to first ask him about, so not to mix the changes upfront)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
> There was a lot of extra mirroring on this - another bugproxy issue?
Probably. Apologies for you getting that. Please disregard it. :/
> Also while I know the maintainer scripts already have the same issue
> I today accidentally came by this
>
For reference,
Debian bug for libvirt is #844339
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
https://bugs.launchpad.net/bugs/1637601
Title:
UbuntuKVM: migration using NFS mount fails #190
Status
Hi Christian Ehrhardt,
Attaching PATCH v2 for Xenial.
It only checks/sets the UID for libvirt-qemu user; no other actions/changes
performed.
** Patch added: "xenial_libvirt_uidgid_v2.debdiff"
Hi Christian Ehrhardt,
> Sorry to realize that only now, but please help me to clarify/avoid
these issues?
no problem; sure.
> #1 On a given Xenial install as of today the files are owned by
> libvirt-qemu:kvm (e.g. pools and images it creates).
> Those files will still be owned by group
Hi @paelzer,
> I meant a Debian bug against base-passwd to begin with not a libvirt bug.
> I think the Mail you have written is a good start, yet IMHO a related bug
> can't hurt t track and make them more aware.
Ah, ok. Yes, you're right. That is BTS #843881 [1].
> Yes it is primarily
this on Debian and Ubuntu, right?
For reference, this is the e-mail sent to Debian base-passwd:
Forwarded Message
Subject: request uid and gid allocation for libvirt-qemu
Date: Tue, 25 Oct 2016 09:27:00 -0200
From: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com>
To: ba
Public bug reported:
Noticed this while installing debug symbols for systemd:
# apt install systemd-dbg
...
Unpacking udev (229-3ubuntu1) over (229-2ubuntu1) ...
...
Setting up udev (229-3ubuntu1) ...
addgroup: The group `input' already exists as a system group. Exiting.
passing init= bootarg.
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
-
Contact info:
----
Manju (manju...@in.ibm.com) A.P. (apu...@us.ibm.com)
== Comment: #12 - M
Thanks, Sebastien. Yes, the changes are in wily.
For documentation purposes. The numbers in a KVM guest on POWER8 match those in
comment #2.
$ lsb_release -d
Description:Ubuntu Wily Werewolf (development branch)
$ dpkg -s openssl | grep ^Version:
Version: 1.0.2d-0ubuntu1
$ openssl speed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1311128
Title:
Please incorporate gcc 4.8 revision
Thanks, Steve.
I forwarded the request internally.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1311128
Title:
Please incorporate gcc 4.8 revision 209515
Status in
Hi Adam,
I'd be inclined to say it's too late in the cycle [...] given the
partial backports that very much touch common code, etc.
That's certainly understandable.
I believe it's possible to trim up the backports even more.
AFAICT, most changes are contained inside #ifdef HWAES_CAPABLE
Ok, the trimmed backports:
- removed the patch which touched common code w/out #ifdef blocks.
- now all changes are under #ifdef blocks, which helps analysis.
Build log:
...
ALL TESTS SUCCESSFUL.
make[2]: Leaving directory '/home/ubuntu/ss5/openssl-1.0.1f/test'
Adam,
Does it help/improve the situation at all?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1444241
Title:
Add more POWER8 optimizations
Status in openssl package
Well, a later SRU should be OK too, right? :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1444241
Title:
Add more POWER8 optimizations
Status in openssl package in
Here is the comparison / benchmarking of:
1) current package
2) current package + attached debdiff
3) upstream code
It shows that:
1) performance of current package improves a *lot* with the attached debdiff;
2) performance of current package + attached debdiff is equal to the upstream's.
$
In summary:
$ openssl speed -evp aes-128-gcm
speedup:
- 16 bytes: 3x
- 64 bytes: 6.4x
- 256 bytes: 13.8x
- 1024 bytes: 17x
- 8192 bytes: 18x
$ openssl speed -evp aes-128-ctr
Public bug reported:
There are some upstream commits that introduce optimizations with significant
performance improvement for IBM POWER8.
This patch introduces their minimal bits/changes in the source package.
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
**
In the patches, this line might not be as clear as intended:
The 'backport' keyword in 'Origin:' just indicates it isn't equal to
'upstream'.
isn't equal in the sense only the interesting changed files were kept,
but not changed, and other files were removed from the diff.
--
You received
You can find more info about that in preseed, debian installer options.
Basically boot options taken by the installer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1403982
@nio-wiklund
Hi, not sure why it didn't work for your cmdline.
If you're still interested in debugging, the option you entered is correct,
as you can see on net-retriever source code:
if db_get debian-installer/allow_unauthenticated [ $RET = true ]; then
log Not
@pitti
Hi, Martin.
Would you have any update on the process of resolving this (maybe someone/I can
help?), or its severity (what's the impact?)
Thanks a lot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in
There's a workaround available meanwhile -- if you want to use the
currently available netboot image, and can afford skipping the GPG
checks/its implications.
Append this to the kernel command line: debian-
installer/allow_unauthenticated=true
--
You received this bug notification because you
Hi Chris,
The package in -proposed fixed this bug.
Test-case from description. Details below.
root@ubuntu:~# apt-cache madison net-tools
net-tools | 1.60-25ubuntu2.1 | http://ports.ubuntu.com/ubuntu-ports/
trusty-proposed/main ppc64el Packages
[...]
301 - 387 of 387 matches
Mail list logo
