@nagendra-d, it does not look like this is a software bug, but a
configuration issue that @skliarie has faced. Feel free to
talk to him through this bug (for documenting purposes) but
I'm keeping the status here as Invalid so we can better track
things we actually have an action for.
Thank you fo
Hello Alexander,
I believe your fuzz test result was meant to the upstream project so I
moved it.
o/
** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server, which
There is a very similar (to yours) problem described here:
https://dovecot.org/pipermail/dovecot/2014-May/095998.html
one of the developers tell end-user to move away from mbox,
and there seems to exist a correct answer stating that mbox
is a supported format and there is no current documentation
Checks (a), (b), (c), (d) passed, plus the comments from others who
installed the package on their servers or test rigs. Marking the
verification as succeeded.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are
Moving back to incomplete as stated by @paelzer.
** Changed in: libseccomp (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1876486
Title:
a) Run https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript.
Full output attached.
Package from proposed is installed:
*** 0.40.0-0ubuntu0.1 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
0.39.0-1 500
Focal verification tests (b), (c) and (d) below:
a) Running script from
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript
b) Request a registration with nginx
sudo certbot -d certbot-test.justgohome.co.uk --agree-tos --staging
--register-unsafely-without-email --nginx
python3-cert
@napsty: the "workaround" (from your blog) is actually to use:
- ifupdown/bridge-utils/vlan/resolvconf for network setup OR
- use systemd-networkd DIRECTLY with the KeepConfiguration= option in .network
file
Just highlighting it here.
@ddstreet, you said you would try to come up with the
TL;DR TODO SUMMARY:
- netplan change to support KeepConfiguration= for systemd-networkd backend
(Groovy)
- backport this change: netplan for Ubuntu Focal (SRU)
- backport this change: netplan for Ubuntu Eoan (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
-