** Description changed:
[Impact]
* `update-grub` (actually `vgs`) complains about
'No medium found' on systems with card readers
that have no card in.
* This may confuse users who aren't sure whether
it means problems occurred with the bootloader,
and concern
Setup:
--
Add '/dev/sda' from the host to a Focal LXD container:
$ lxc launch ubuntu:focal 'focal-container'
$ lxc config device add 'focal-container' 'lxc-dev-sda' unix-block
source='/dev/sda' path='/dev/sda'
Device:
---
$ grep ^
* Changed in: lvm2 (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: lvm2 (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hey Fabio,
That happens when the package lands in -proposed.
It looks like the SRU vanguards this Wed/Thu are Robie/Lukasz,
which is good as they are familiar with the discussion/changes,
so I'll ask if they have SRU review cycles to for this upload.
Thanks for following up!
** Changed in:
Thanks for the bug report!
Changing title to indicate actual impact, and reassining to systemd as
the 'nofail' mount option (which you tried) apparently didn't work.
Per systemd.mount(5) man page:
nofail
[..] This means that the boot will continue without waiting
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1946804
Title:
ufw breaks boot on network root filesystem
Status in ufw:
Fix Committed
Thanks, Fabio!
With the regression fixed and Oracle test case working as expected,
I've updated the versioning and patch series, and uploaded for SRU.
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1802021 ***
https://bugs.launchpad.net/bugs/1802021
For documentation purposes, this issue is likely a duplicate of bug
1802021, fixed in kernel 4.15.0-47.50.
** This bug has been marked a duplicate of bug 1802021
[Hyper-V] srcu: Lock srcu_data structure
We'll have to respin/re-upload with a different version, due to the
recent security update [1].
Let's do that after the testing on Oracle, if at all possible, as that
may be asked by the SRU team for accepting it, and some members may be
busy with the jammy release, so let's save one request. :)
Hey, Fabio!
That looks good; thanks!
I have built/uploaded to ppa:mfo/lp1947099v2 and for SRU,
as the tests on Oracle have `-t` in, thus no code change
from previous tests, effectively.
Per our chat, for completeness/correctness you'll test on
oracle again, and then we can move the SRU upload
Fabio is out today, but he mentioned yesterday that the test patch
worked fine locally, and he'd get access to an oracle test system again,
for more tests.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
Hi Fabio,
> [1] But now when I try to obtain an IP using dhcp without specifying any
> timeout,
> it dumps lots of "Lowered timeout to match user request" messages.
> Is that expected?
>
> https://pastebin.ubuntu.com/p/5Tpc5Rwdkq/
No, this is a regression without `-t`, and has to be fixed
Hey Fabio,
Thanks for the lab setup for testing this!
> Anyway, if someone can build a klibc-utils package for me with the proposed
> patch,
> I can test the ipconfig behavior in this Lab.
Sure, there you go!
sudo add-apt-repository ppa:mfo/lp1947099
sudo apt install klibc-utils
> For
Seth, ack; thanks!
Matthew, I uploaded the changes to Focal; thanks for the SRU!
--
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/1960863
Title:
armv8 paca: poly1305 users
Hi @ubuntu-security,
I believe we should ask for your ack, as this is openssl.
If that's right, could you please review it and comment?
The changes look ok technically and w.r.t. test results
(details in sru template and comment above.)
Thanks!
--
You received this bug notification because
The changes look good to me.
It built correctly (ie, build-time tests) on all archs on PPAs w/ -updates and
-proposed.
It passed autopkgtests on focal/arm64 against the PPA build too.
Thus, no test regressions in our arm64 cpus, and the synthetic test
passes on newer arm64 cpu (tested by user).
** Tags added: sts-sponsor-mfo
--
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/1960863
Title:
armv8 paca: poly1305 users see segfaults when pointer authentication
in use
** Changed in: util-linux (Ubuntu)
Importance: Undecided => Wishlist
--
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/1958053
Title:
If dmesg has bug, then make popup
That isn't the case, apparently.
The file is only readable by user/group, but not others, in Impish, at
least.
Upgrade:
$ lsb_release -cs
impish
$ ls -l /var/log/dmesg
-rw-r- 1 root adm 95595 Oct 28 11:46 /var/log/dmesg
Install:
$ lsb_release -cs
impish
$ ls -l /var/log/dmesg
-rw-r-
This has been intentionally changed a while ago, please see [1]. Thanks!
[1] https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Tested with Bionic, Focal, Hirsute, and Impish
with the test steps provided, on Oracle Cloud.
All good.
With the packages in -proposed, the system can reboot correctly.
---
bionic
Version: 0.36-0ubuntu0.18.04.2
focal
Version: 0.36-6ubuntu1
hirsute
Version: 0.36-7.1ubuntu1
impish
Version:
Tested with Bionic, Focal, and Hirsute, with the test steps provided.
All good.
Bionic:
---
Before:
# dpkg -s ufw | grep Version:
Version: 0.36-0ubuntu0.18.04.1
# iptables -L ufw-user-input -n
Chain ufw-user-input (1 references)
target prot opt source destination
ACCEPT
Uploaded to H/F/B.
(debdiffs in bug 1946804)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1933117
Title:
ufw delete can confuse protocol-specific rule with otherwise
Uploaded to I/H/F/B.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1946804
Title:
ufw breaks boot on network root filesystem
Status in ufw:
Fix Committed
Status in ufw
** Patch added: "ufw-impish.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536527/+files/ufw-impish.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
** Patch added: "ufw-bionic.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536530/+files/ufw-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
** Patch added: "ufw-focal.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536529/+files/ufw-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Verified test packages (ppa:mfo/lp1946804) for
the Hirsute, Focal, and Bionic releases.
...
Without the patch:
Chain ufw-user-input (1 references)
target prot opt source destination
ACCEPT tcp -- 0.0.0.0/00.0.0.0/0tcp dpt:22
ACCEPT tcp --
** Patch added: "ufw-hirsute.debdiff"
https://bugs.launchpad.net/ufw/+bug/1946804/+attachment/5536528/+files/ufw-hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Verified test packages (ppa:mfo/lp1946804) for
the Impish, Hirsute, Focal, and Bionic releases
on Oracle Cloud's 'BM.Standard1.36' systems.
(Impish/Hirsute: Focal and do-release-upgrade.)
...
Without the patch, the system boot stalls.
With the patch, the system boot continues.
(Note:
** Description changed:
[Impact]
A system with rootfs on iSCSI stops booting when ufw.service starts.
The kernel logs iSCSI command/reset timeout until I/O fails and the
root filesystem/journal break.
The issue is that ufw_start() sets the default policy _first_, then
adds rules
** Description changed:
[Impact]
A system with rootfs on iSCSI stops booting when ufw.service starts.
The kernel logs iSCSI command/reset timeout until I/O fails and the
root filesystem/journal break.
The issue is that ufw_start() sets the default policy _first_, then
adds rules
** Description changed:
+ [Impact]
+
+ * The deletion of a rule without the 'proto' field
+that has a similar rule *with* the 'proto' field
+might delete the wrong rule (the latter).
+
+ * This might cause services to be inaccessible or
+incorrectly allowed, depending on rule
: New => In Progress
** Changed in: ufw (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: ufw (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: ufw (Ubuntu Focal)
Status: New => In Progress
** Changed in: ufw (
** Tags added: seg sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1933117
Title:
ufw delete can confuse protocol-specific rule with otherwise matching
** Tags added: sts sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1946804
Title:
ufw breaks boot on network root filesystem
Status in ufw:
Fix Committed
** Changed in: ufw (Ubuntu Bionic)
Status: New => In Progress
** Changed in: ufw (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: ufw (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: ufw (Ubuntu Focal)
St
MR for debian/master submitted [1].
Since Impish is in Final Freeze as of last week,
this would fit a post-release SRU per [2] IIUIC,
so a sync wouldn't be possible, I think.
Since the devel/J series isn't open yet, perhaps
just an Impish SRU is enough now, as the devel
release will start from
** Merge proposal linked:
https://code.launchpad.net/~mfo/ufw/+git/ufw/+merge/410152
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1946804
Title:
ufw breaks boot on
** Description changed:
[Impact]
A system with rootfs on iSCSI stops booting when ufw.service starts.
The kernel logs iSCSI command/reset timeout until I/O fails and the
root filesystem/journal break.
The issue is that ufw_start() sets the default policy _first_, then
adds rules
Merge Proposal submitted:
https://code.launchpad.net/~mfo/ufw/+git/ufw/+merge/410091
** Also affects: ufw (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ufw (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ufw (Ubuntu Impish)
Importance:
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: parted (Ubuntu)
Status: New =
Thanks again, Matthew.
I've reviewed and sponsored the new debdiff for Focal, with the existing
changes (so we have .20.04.1 and .2 in the same upload, going in focal-
proposed again.)
Further details added in bug 1912969.
--
You received this bug notification because you are a member of
Marking all other packages/dev release as Invalid.
Per previous discussion with Jay, iirc, those are
leftovers from a previously considered solution(s)
which was not the final one (in initramfs-tools.)
And just Bionic had to be patched as later releases
were not affected.
Please feel free to
Hi Matthew,
Thanks for the analysis.
We'll need such changes on top of what's in -proposed (ie, in an
incremental version), re-uploaded.
Please see `dpkg-buildpackage -v` to generate a package build including
the version in -proposed plus the new version with the workaround for
the test-case.
Hi Matthew,
I've kicked one or two rebuilds today, and still see the (same) one or
two tests failing.
I'm out this week so can't look much more into it (althogh I'm
admittedly curious about it :)
If you can take a look at these FTBFS test case failures, that would be
awesome; all archs must
Now the two tests failed again.
I have to EOD, and this might benefit from some delay, in case the transient
condition just goes away.
Also, let's not overload the riscv64 builder with this so other builds can move
on.
We have 7 days in -proposed to look at this in more detail (or the bad
Same one failure, re-building again.
** Attachment added:
"buildlog_ubuntu-focal-riscv64.librelp_1.5.0-1ubuntu2.20.04.1_BUILDING.txt.gz.3"
and now it had only 1 failure in the test suite,
thus indeed a transient/arch-specific flakiness.
re-building once again.
$ zgrep '^FAIL: .*sh$'
buildlog_ubuntu-focal-riscv64.librelp_1.5.0-1ubuntu2.20.04.1_BUILDING.txt.gz.*
buildlog_ubuntu-focal-
focal/riscv64 had 2 failures in the test suite.
i've requested a re-build so it runs again, as
it seems more related to the arch or something
transient than the patchset, as only this arch
and release hit it.
(groovy: all archs ok, focal: other archs ok)
attaching build log for ref (it's lost on
** Patch added: "lp1908473_librelp_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5453106/+files/lp1908473_librelp_focal.debdiff
** Description changed:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks file
** Patch added: "lp1908473_librelp_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5453105/+files/lp1908473_librelp_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Matthew, thanks for the great work in this bug and patches.
Uploaded to Groovy and Focal w/ trivial changes; attached.
cheers,
Mauricio
...
debdiffs:
I've modified the patch files slightly, as we discussed;
- keep the commit messages;
- use its/patch headers for DEP3, adding Origin: /
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads
** Tags removed: sts-sponsor-mfo
--
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/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of
** Tags removed: sts-sponsor-mfo
--
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/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is
Hi SRU team,
All autopkgtest failures in #4 are now passing on all architectures.
- gvfs/amd64 was flaky, passed on retry.
- openssh/* needs the test-case fix staged in bionic-proposed;
passed by adding openssh/1:7.6p1-4ubuntu0.4 to the triggers.
(Thanks @halves for spotting a
Looked at the autopkgtest regressions:
gvfs2 passed on retry.
openssh fails with -updates and -release too.
openssh is missing the test-case fix currently in -proposed
(openssh/1:7.6p1-4ubuntu0.4)
to confirm, i ran openssh autopkgtests w/ openssh from -proposed; it passes.
however, when trying
Hey Alex, thank you very much for your prompt review.
--
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/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the
Hi Ubuntu Security Team,
I've subscribed you to this bug for a patch review asked by the SRU team.
Please find a request summary below, and feel free to ask for details.
There's a change being proposed to the cryptsetup boot logic
(debdiff in comment #44) so to allow an encrypted device on
top
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 Ubuntu
Touch seeded
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
** 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 Ubuntu
Touch seeded packages, which is
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
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
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/
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/
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"
Uploaded initramfs-tools to Bionic and Xenial.
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 Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** 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 Ubuntu
Touch seeded
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 Ubuntu
Touch seeded
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 Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Tags added: sts-sponsor-mfo
--
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/1879987
Title:
machine get stuck at boot if specified 'console=ttyS* ' doesn't
** Patch added: "bionic_cryptsetup_lp1879980_V3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+attachment/5413627/+files/bionic_cryptsetup_lp1879980_V3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** 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 Ubuntu
Touch seeded packages, which is
Uploaded cryptsetup to Focal and Bionic.
Attaching the updated debdiffs for reference.
--
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/1879980
Title:
Fail to boot
** Tags added: sts-sponsor-mfo
--
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/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is
** Tags removed: sts-sponsor-mfo
--
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/1862846
Title:
Crash and failure installing focal
Status in subiquity:
Fix Released
** Tags removed: sts-sponsor-mfo
--
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/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux
** Tags removed: sts-sponsor-mfo
--
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/1858802
Title:
libblkid: no bcache UUID due to ambivalent detection of bcache and
** Tags removed: sts-sponsor-mfo
--
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/1870316
Title:
'sudo hwclock -s' fails with 'settimeofday() failed: Invalid argument'
** Tags removed: sts-sponsor-mfo
--
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/1886300
Title:
rename.ul refuses to rename links that don't resolve (regression)
** Patch added: "groovy_cryptsetup_lp1879980_V3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+attachment/5413208/+files/groovy_cryptsetup_lp1879980_V3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
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 Ubuntu
Touch seeded packages, which is subscribed to
Hi Guilherme,
I can handle that while you're out.
cheers,
Mauricio
--
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/1879980
Title:
Fail to boot with LUKS on top
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
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
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 Ubuntu
Touch seeded packages, which is
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 Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Hi Seyeong,
The proposed-migration of util-linux in groovy is blocked on one last
autopkgtest of gfs2-utils failing on ppc64el (the 'mount' test times
out; reproducible even w/ previous versions) [1, 2]
This is new and unrelated to these changes (not uploaded to groovy), but
prevents uploading
Er, actually s/Invalid/Fix Committed/, so to document that this bug
(behavior of input parameter 'tls.tlscfgcmd' not supported) will be
fixed/gets fixed on rsyslog 8.2001.0-1ubuntu1.1 (in focal-proposed.)
** Changed in: rsyslog (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags
In an interesting overnight timing event, that rsyslog upload has been
accepted to focal-proposed.
Sure enough, it built with librelp-dev_1.5.0-1ubuntu2.
And the configure stage enables the option:
checking for relpSrvSetTlsConfigCmd... yes
checking for relpSrvSetTlsConfigCmd... (cached) yes
Verification/comparison steps to ensure that the modified
rsyslog package is built and working correctly, given its
importance in the distribution:
1) Compare test suite results in build logs
2) Compare configuration options in build logs
3) Compare packages' control file and contents
All look
Hi Jorge,
Thanks for tracking this down in the build history.
> I suspect that the rsyslog package was built against and older librelp
version.
You're right, the build log shows 'librelp-dev_1.4.0-2'
in the package installs/'Build environment' section.
I slightly modified the changelog entry,
** Patch added: "lp1888926-focal-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1888926/+attachment/5399433/+files/lp1888926-focal-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in
** Changed in: util-linux (Ubuntu Groovy)
Status: Confirmed => Fix Committed
** Changed in: util-linux (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux
Hi Seyeong,
Thanks for the updated debdiffs and reporting Debian bug 966106
(Please feel free to comment in the LP bug when you report a Debian bug.)
Per the Debian maintainer, they recently stopped shipping/installing rename.ul,
on 2.35.2-5.
Fortunately this only affects Groovy and later (non
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1888926
Title:
tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
Status
101 - 200 of 387 matches
Mail list logo
