** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Changed in: sssd (Ubuntu Eoan)
Importance: Undecided => High
--
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/1723350
Title:
sssd offline on boot, stays offline forever
To manage
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
** Description changed:
[Impact]
sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
In ubuntu that file is a symlink
This is fixed in 4.12.2 uploaded to groovy, so marking that task as fix
released.
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Mustapa, about files being shown as directories, you are probably being
affected by bug
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476 which is an
in-progress SRU and has a fix uploaded to focal-proposed already.
--
You received this bug notification because you are a member of
autopackage tests are also green: https://people.canonical.com/~ubuntu-
archive/proposed-migration/focal/update_excuses.html#python-certbot-
nginx
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
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
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
** Description changed:
+ [Impact]
+ sssd can switch to an offline mode of operation when it cannot reach the
authentication or id backend. It uses several methods to assess the situation,
and one of them is monitoring the /etc/resolv.conf file for changes.
+
+ In ubuntu that file is a
** Changed in: sssd (Ubuntu Eoan)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu Eoan)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I'm trying[1] to back this out, but it will remove symbols from the
library without bumping the soname. Our next chance is when openldap 2.5
comes out, which will likely bump the soname.
1.
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/383797
--
You
Just tested and eoan is affected, focal is clear.
** Also affects: sssd (Ubuntu Eoan)
Importance: Undecided
Status: New
--
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/1723350
Ok, I have a simple way to reproduce this, and was able to test the
upstream patch. I'll polish it up and put it up for review, then prepare
the SRU paperwork.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Changed in: sssd (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug
For the SRU team reviewing this, I can confirm the bug is fixed in samba
4.12.2 which I will upload to groovy shortly:
root@groovy-samba-file-folder:~# gio info smb://127.0.0.1/testshare/123.txt |
grep '^type:'
type: regular
root@groovy-samba-file-folder:~# apt-cache policy samba
samba:
No, comment #8 shows disco is already fixed. This may be SRU material
for Bionic.
--
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/1827041
Title:
Regression in smbclient, username required
I patched the patch, ugh, but I'll think of a nice way to set this
dynamically before uploading. I'm dropping a lot of delta in the 2.4.50
merge :)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
nee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: openldap (Ubuntu)
Status: Triaged => In Progress
--
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/1875697
Title:
That comes from debian/patches/set-maintainer-name
--
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/1875697
Title:
drop fix-ldap-distribution.patch?
To manage notifications about this bug
I think dropping this delta is fine, as the "ubuntu" name will still
show as long as there is a delta. But looks like the email is wrong, we
should be showing ubuntu-devel@ there instead of the debian maintainers
list.
--
You received this bug notification because you are a member of Ubuntu
Debian tried it, and disabled this support again because it pulled in
too many dependencies: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=941654
Samba 4.12.x has another spotlight backend, elastic search:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941654
I'm not a macos user so I'm
Public bug reported:
https://launchpad.net/ubuntu/+source/memcached/1.6.5-2/
build log (warning: over 10Mb):
https://launchpad.net/ubuntu/+source/memcached/1.6.5-2/+build/19216634/+files
/buildlog_ubuntu-groovy-s390x.memcached_1.6.5-2_BUILDING.txt.gz
On s390x:
Test Summary Report
Uploaded, waiting for SRU team.
--
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/1875471
Title:
python3-certbot-nginx is incompatible with its dependencies
To manage notifications about
** Tags added: bitesize
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
To manage
** Description changed:
This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot.
[Impact]
Reguesting a certificate via the nginx
** Description changed:
This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot.
[Impact]
Reguesting a certificate via the nginx
Successful run with apache:
ubuntu@certbot-test:~$ sudo certbot -d certbot-test.justgohome.co.uk
--agree-tos --staging --register-unsafely-without-email --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new
** Description changed:
This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/Certbot.
[Impact]
Not directly applicable; see the exception
** Description changed:
- This issue only affects version 0.39.0-1 of the python-certbot-nginx
- package in Ubuntu 20.04.
+ This bug tracks an update for python-certbot from 0.39.0 to 0.40.0.
+
+ This update includes bugfixes only following the SRU policy exception
+ defined at
Staging server test worked just fine. I'll prepare the SRU paperwork.
ubuntu@certbot-test:~$ sudo certbot -d certbot-test.justgohome.co.uk
--agree-tos --staging --register-unsafely-without-email --nginx
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator
Thanks for the test update, worked great:
(...)
testing section-continuations-2525.conf...passed
testing section-empty-continuations-2731.conf...passed
testing semacode-1598.conf...passed
testing two-blocks-one-line-1693.conf...passed
Success!
Package versions tested:
certbot 0.40.0-1
letsencrypt
https://launchpad.net/~ahasenack/+archive/ubuntu/certbot-
tlssni01-1875471-d
--
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/1875471
Title:
python3-certbot-nginx is incompatible with its
That sounds good, let me prepare a separate ppa for (d)
--
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/1875471
Title:
python3-certbot-nginx is incompatible with its dependencies
To manage
The testscript at
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript no
longer works:
Cloning into '/root/gopath/src/github.com/letsencrypt/boulder'...
remote: Enumerating objects: 2676, done.
remote: Counting objects: 100% (2676/2676), done.
remote: Compressing objects: 100%
Ok, I filed bugs for the FTBFS issues, but per policy, we won't do an
update just to fix failed-to-build-from-source bugs: these should be
updated together with something else.
Thanks for all the options you outlined in comment #8, and for the check
in comment #11.
So to keep things simple:
a)
The server guide has a warning about this package being deprecated
(paride just added it):
https://ubuntu.com/server/docs/mail-postfix
"""
Deprecation warning: please note that the mail-stack-delivery metapackage has
been deprecated in Focal. The package still exists for compatibility reasons,
This was the deprecation notice sent back then:
https://lists.ubuntu.com/archives/ubuntu-server/2018-March/007682.html
some replies came back in May:
https://lists.ubuntu.com/archives/ubuntu-server/2018-May/007707.html
--
You received this bug notification because you are a member of Ubuntu
Thanks for getting back to us. I'll close the bug.
** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1876622
Title:
Can't
I think this bug is wontfix, or opinion, but we need tasks for the Focal
release notes, and the server guide. I'm failing at that, can't figure
out the UI to do it.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Also affects: samba (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu Focal)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: samba (Ubuntu Focal)
Status: New => In Progress
** Changed in: samba (Ubuntu Focal)
Quick update on the current focal situation regarding some of these
packages:
These are currently an FTBFS in focal:
- python-certbot 0.40.0-1 (build-time tests fail)
- python-acme 1.1.0-1 (build-dep python3-idna <<2.8 not satisfied. When it was
last built in focal, python3-idna was at 2.6)
-
Sorry for having gone radio silent in the past few days. I'm back on
this tomorrow.
--
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/1875471
Title:
python3-certbot-nginx is incompatible with
Sorry, "Pay close attention", not "Play" :)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1876622
Title:
Can't upgrade samba-common-bin: undefined symbol: smb_strtoul
To manage
Yeah, that was probably the cause. To finish fixing your system
regarding the samba packages, you should be able to run these now:
sudo apt update
sudo apt -f install
Play close attention to what the last one tells you ("-f" stands for "fix"). If
it doesn't look unreasonable and it's asking
You may have had an old samba from 18.04 still installing, as a result
of your release upgrade. Could you please run this command and show the
output?
dpkg -l | grep -E "(samba|smb|registry-tools|winbind|libwbclient|ctdb)"
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You
I'm adding this to my list of delta to drop in this cycle.
--
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/1875697
Title:
drop fix-ldap-distribution.patch?
To manage notifications about
Disco is EOL, marking its task as such.
** Changed in: clamav (Ubuntu Disco)
Status: Triaged => Won't Fix
--
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/1839767
Title:
apparmor
PPA with test packages: https://launchpad.net/~ahasenack/+archive/ubuntu
/certbot-tlssni01-1875471
It has python-certbot with TLSSNI01 removed, probably not necessary for
this bugfix, but it allowed me to re-introduce the build-time tests for
the python-certbot-nginx package.
Will continue
Would this commit be correct to apply on top of 0.40.0 to at least match
python-acme 1.1.0-1 that is in focal w.r.t. TLSSNI01's removal?
https://github.com/certbot/certbot/commit/4b488614cf7749c8139c11f0983fe4b71e29827f
* Remove tls sni common (#7527)
* fixes #7478
* add changelog entry
If
So python-certbot 0.40.0 still has TLSSNI01, but not acme, and so far
only python-certbot-nginx is triggering the error. Probably not worth
bumping python-certbot just to be able to run its tests correctly.
--
You received this bug notification because you are a member of Ubuntu
Server, which is
> In the current state in Focal/Groovy, the tests we include in our packages
> are broken
> for at least python-certbot, python-certbot-apache, and python-certbot-nginx.
> The python-certbot-dns-* packages themselves are working, but I didn't verify
> whether
> or not the tests are. I can if
The groovy packages are being updated, there are just too many packages
being handled and the machines are very busy.
For focal, we should take the path of updating the nginx subpackage to
0.40.0. I'll handle that and check the tests.
--
You received this bug notification because you are a
Thanks for getting back to us.
I'm going to close this bug as invalid, since the software is working as
expected.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
Have you tried smbclient with -m NT1?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
To manage
** Changed in: python-certbot-nginx (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: python-certbot-nginx (Ubuntu)
Importance: Undecided => High
** Changed in: python-certbot-nginx (Ubuntu)
Status: Confirmed => In Progress
--
You received
Bruno, no need, we reproduced the bug and will work on a fix.
--
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/1872476
Title:
Shared files are shown as folders
To manage notifications about
In fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1801442#c28
Looks like the fix for https://bugzilla.samba.org/show_bug.cgi?id=14101
which went into 4.11.6 needs to be reverted for now.
Thanks santa_ on #ubuntu-devel for the pointers!
** Bug watch added: Red Hat Bugzilla #1801442
Hello,
could you please attach the crash file about this that you likely have
in /var/crash? Without it I'm afraid there isn't much we can do.
It would also help to know if you can reliably reproduce the crash.
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received
When you are connected with the GUI and seeing all files as browsers,
can you please run smbstatus on your NAS to see what protocol version
was used?
NT1 is used for browsing when you set that option, but the client (your
machine) might switch to a higher version if the NAS says it supports
it.
In general I tend to agree with Sam. A config was changed (kdc logging
to a file in /var/log/), and for it to work fully another config needs
to be changed (systemd). FreeIPA (who made the first change) can easily
create a systemd override for this.
That being said, it's not super unreasonable
Hello,
please run:
sudo apt update
sudo apt -f install
and
dpkg -l|grep -v ^ii
** Changed in: heimdal (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to heimdal in Ubuntu.
Also relevant: https://lists.openldap.org/hyperkitty/list/openldap-
de...@openldap.org/thread/ACLFYWEWIQVUUF3JDDSV3HZZQWXKB7N7/
--
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/1868703
Title:
MIR stands for *Main* Inclusion Request. It's different from processing
a NEW package. Or else we would only accept NEW packages in Ubuntu if
they went into main.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Just a note that Jeff wasn't asking for an MIR, but an SRU.
--
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/1868882
Title:
[SRU] Put ipmctl into Bionic (and update necessary deps)
To
For reference, just because it took me a while to get the syntax right,
plus https://bugs.squid-cache.org/show_bug.cgi?id=4905 made me scratch
my head a bit wondering why it wasn't working when I used "squid"
instead of another name:
logformat custom-squid %tg{%F %H:%M:%S %z} %6tr %>a %Ss/%03>Hs
The sssd chapter in the server guide has been rewritten and the pam-
auth-update command was incorporated.
** Changed in: serverguide
Status: New => Fix Released
** Changed in: serverguide
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notifi
Sorry, forgot the url: https://discourse.ubuntu.com/t/service-sssd/11579
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1821085
Title:
Documentation: SSSD server guide recommends
I updated the guide at https://discourse.ubuntu.com/t/service-
sssd/11579/ with a section on KDC spoofing, please take a look.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/176
Title:
The original gitlab issue opened to track this is still private it
seems[1]. All other details I have are in the MP diff[2].
1. https://gitlab.isc.org/isc-projects/bind9/-/issues/1574
2. https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/3343/diffs
** Bug watch added:
Hi Andrew, I'm back on this bug since I'm updating the server guide for
the 20.04 release.
Again I didn't add krb5_validate to the guide, mostly because I had
forgotten about this bug here. The new guide is at
https://discourse.ubuntu.com/t/service-sssd/11579
Let me see if I got the attack
** Changed in: serverguide
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: serverguide
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sssd in Ubuntu.
Closing as invalid as this is the expected behavior with the current
version.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
other changes.
+
+ 1. https://downloads.isc.org/isc/bind9/9.16.2/RELEASE-NOTES-
+ bind-9.16.2.html
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: bind9 (Ubuntu)
Status: New => In Progress
--
You received this bug notifi
Public bug reported:
This affects focal which is at 9.16.1 at the moment.
Upstream MP: https://gitlab.isc.org/isc-
projects/bind9/-/merge_requests/3343
Upstream released 9.16.2 with the fix, and of course other changes.
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: apache2 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
** Description changed:
- Apache is lacking proper support for post-handhake-auth in TLSv1.3 POST
- requests using certificate authentication.
+ [Impact]
+ Apache is lacking proper support for post-handhake-auth in TLSv1.3 POST
requests using certificate authentication. This is used by freeipa,
** Description changed:
Apache is lacking proper support for post-handhake-auth in TLSv1.3 POST
requests using certificate authentication.
This was fixed in debian[1] via patches from upstream[2].
Test case:
$ lxc launch ubuntu-daily:focal ubuntu
Enter the container as root:
** Description changed:
Apache is lacking proper support for post-handhake-auth in TLSv1.3 POST
requests using certificate authentication.
This was fixed in debian[1] via patches from upstream[2].
Test case:
$ lxc launch ubuntu-daily:focal ubuntu
Enter the container as root:
** Description changed:
Apache is lacking proper support for post-handhake-auth in TLSv1.3 POST
requests using certificate authentication.
This was fixed in debian[1] via patches from upstream[2].
Test case:
$ lxc launch ubuntu-daily:focal ubuntu
Enter the container as root:
Public bug reported:
Apache is lacking proper support for post-handhake-auth in TLSv1.3 POST
requests using certificate authentication.
This was fixed in debian[1] via patches from upstream[2].
Test case:
$ lxc launch ubuntu-daily:focal ubuntu
Enter the container as root:
$ lxc exec ubuntu
Correct, closing the bug.
** Changed in: samba (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1697817
Title:
disable smb1 by default
To
Public bug reported:
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956482 and
https://lists.samba.org/archive/samba/2019-September/225824.html
** Affects: samba (Ubuntu)
Importance: Wishlist
Status: Triaged
--
You received this bug notification because you are a member of
Also updated the release notes regarding the nginx changes:
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#nginx
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1861101
Title:
[MIR]:
I updated the release notes:
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Bind_9.16
** Changed in: ubuntu-release-notes
Status: New => Fix Released
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notifi
Almost there.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1867408
Title:
openssh 8.2 waiting on libfido2 MIR
To manage notifications about this bug go to:
stracing posttls-finger:
4543 connect(3, {sa_family=AF_UNIX, sun_path="private/tlsmgr"}, 110) =
-1 ENOENT (No such file or directory)
If you cd into /var/spool/postfix and then try again, it will find the
tlsmgr socket. Further I cannot test as it seems my ISP blocks outbound
25/tcp, but in any
Do you know which sssd versions are affected? I tagged ubuntu releases
that ship 1.16
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => High
** Also affects: sssd (Ubuntu Bionic)
Importance: Undecided
Status: New
**
apt-get will be enough once it's published, and looks like it just was
published.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1862327
Title:
BIND 9.11.3 dropping queries when dhcp lease is renewed
To manage notifications about
python-maxminddb was promoted, so python-geoip2 can also be promoted
now. See comment #19 for the MIR approval.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1861101
Title:
[MIR]:
** Description changed:
Bind just released 9.16.1. Focal has 9.16.0. This release was expected
and is considered important, as it's the first point release after a new
major one, and we should have it in focal.
+
+ UPDATE: debian just updated to 9.16.1 in experimental, just the upstream
+
** Description changed:
Bind just released 9.16.1. Focal has 9.16.0. This release was expected
and is considered important, as it's the first point release after a new
major one, and we should have it in focal.
Release notes: https://downloads.isc.org/isc/bind9/9.16.1/RELEASE-NOTES-
** Description changed:
Bind just released 9.16.1. Focal has 9.16.0. This release was expected
and is considered important, as it's the first point release after a new
major one, and we should have it in focal.
Release notes: https://downloads.isc.org/isc/bind9/9.16.1/RELEASE-NOTES-
1 - 100 of 3533 matches
Mail list logo
