Here's the one for Bionic to the applied/ubuntu/bionic-devel branch.
** Patch added: "Overwriting the unbound.prerm file (pulled from Bionic) and
removing DEBHELPER macro"
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2072700/+attachment/5796754/+files/bionic_unbound_prerm_overwrite.
> changing this in a new package upgrade will not fix the underlying
issue, but will for the next upgrades.
No worries. Understood. Thank you for confirming that bit. Helps us set
expectations :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
No problem. Happy to help.
> Does unbound remain inactive after the upgrade, or does the postinst
maintainer script start it up again for you successfully?
The postinst script does indeed start it back up. As for timing, it was
~43 seconds between the prerm stop and postinst start in one example.
And here is the patch for the unbound.prerm file on Focal
** Patch added: "Patch file for unbound.prerm on Focal"
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2072700/+attachment/5796028/+files/focal_unbound_prerm.diff
** Description changed:
- On both Bionic (EOL, yes, but applies
Here's the Bionic prerm patch
** Patch added: "Patch file for unbound.prerm on Bionic"
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2072700/+attachment/5796027/+files/bionic_unbound_prerm.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
On both Bionic (EOL, yes, but applies to the packages available within
ESM also) and Focal, we found that the unbound package's prerm
maintainer script does not confirm whether the action is "remove" before
it stops the service, causing a service stop and unnecessary unbound
d
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065139
Title:
nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2:
Also confirming 535.183.01-0ubuntu0.22.04.1 builds successfully against
kernel 5.15.0-112-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065139
Title:
nvidia-dkms-545 545.29.06-0ubuntu0.22.0
** Also affects: nvidia-graphics-drivers-535 (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/2065139
Title:
nvidia-dkms-545 545.29.06-0ubuntu0.22.0
Thank you for adding this to Jammy!
Is it possible to bring the new version in for Bionic and Focal as well?
Thank you in advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955413
Title:
Upda
** Tags added: bionic
** Tags added: focal
** Tags added: hirsute impish jammy
** Summary changed:
- containerd 1.5.9 in bionic/focal
+ Update to containerd 1.5.9
** Description changed:
- Could containerd be updated to 1.5.9 in bionic and focal?
+ Could containerd be updated to 1.5.9?
- I
Updated the summary and title of this bug, since we would like to see
this package upgraded to version 1.5.9 now. Upgrading to 1.5.9 would not
only address the most recent CVE:
https://nvd.nist.gov/vuln/detail/CVE-2021-43816, but it would also
address https://bugs.launchpad.net/bugs/cve/2021-41190
** Summary changed:
- containerd 1.5.8 in bionic/focal
+ containerd 1.5.9 in bionic/focal
** Description changed:
- Could containerd be updated to 1.5.8 in bionic and focal?
+ Could containerd be updated to 1.5.9 in bionic and focal?
It addresses a number of CVEs compared to the current ver
13 matches
Mail list logo
