Confirmed, reload is triggering a restart in xenial, bionic and cosmic.
It's fixed in disco.
But some care must be taken here, apparently a follow-up fix was necessary.
Upstream bugs:
- original bug: https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4108
https://github.com/NLnetLabs/unbound/co
Do we still want to have other arches failing the build if tests do not
pass?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1791018
Title:
self-test errors do not break the build
To manag
Disco (19.04) has 23.2-1:
psmisc (23.2-1) unstable; urgency=medium
* New upstream release
* killall: look at all namespaces by default
(...)
** Changed in: psmisc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server
Hm, this is complicated to manage in lp. Cosmic has the package "squid"
(not squid3), and is affected. Disco has "squid" but is NOT affected.
Xenial and Bionic have "squid3", and are affected.
** Changed in: squid3 (Ubuntu Cosmic)
Status: New => Invalid
** Changed in: squid (Ubuntu Bionic
This is fixed in disco, which ships squid 4.
** Also affects: squid3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: squid3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: squid (Ubuntu)
Importance: Undecided
Status: New
** Als
Now that disco is in feature freeze, I hope to get to it as this is a
bugfix.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1616123
Title:
rpc-svcgssd.service uses incorrrect variable SVCG
Thanks for filing this bug in Ubuntu.
You have some odd error messages in your logs:
Processing triggers for ufw (0.35-0ubuntu2) ...
Setting up openssh-client (1:7.2p2-4ubuntu2.8) ...
Setting up openssh-sftp-server (1:7.2p2-4ubuntu2.8) ...
Setting up openssh-server (1:7.2p2-4ubuntu2.8) ...
Unsafe