uploaded to kinetic!
And *ahem* maybe one of you should think about applying for coredev
soon, you know just in case i get hit by a bus or something :-)
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe :
** Changed in: openssl (Ubuntu)
Assignee: Nicolas Bock (nicolasbock) => (unassigned)
** Changed in: openssl (Ubuntu Bionic)
Assignee: Nicolas Bock (nicolasbock) => Bruce Elrick (virtuous-sloth)
** Changed in: openssl (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Tags
uploaded to bionic queue, thanks!
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1940141
Title:
OpenSSL servers can send a non-empty status_request in a
CertificateRequest
Status in
If you'd rather remove the opt-in part, that's fine with me; I can
sponsor the debdiff then with the opt-in parts left out, if that works
for you Bruce and Nicolas.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
@ubuntu-security since this is openssl, could you give the debdiff a
review? I can sponsor it as a normal SRU if you have no objections (and
the changes look ok to you), as it doesn't really seem like it would
specifically need to go to the -security pocket.
--
You received this bug notification
> It's not needed for actual functionality of the backport but that
assumes that any future backports or fixes don't break this backport
yes i get that, my comment is about whether or not the patch changes any
code *outside* of the self-tests, e.g. the TLSProxy perl code changes.
If that's *only*
The 2nd upstream patch appears to add new functionality, for actually
parsing a certificate request; is that actually needed (outside of the
self-tests)? If not, it shouldn't be included in the backport.
--
You received this bug notification because you are a member of STS
Sponsors, which is
> I've changed it for testing and MAAS didn't work properly.
did you investigate why? did you also adjust the code as i mentioned in
comment 22?
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
@seyeongkim did you have a chance to look at using echo=False in the
VirshSSH() class?
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1921658
Title:
Can't compose kvm host with lvm storage
> the additional information contains valid data.
then I think SRU'ing this would cause a behavior change that could
possibly break someone, which isn't something we should do.
I'd suggest putting the fix behind some opt-in mechanism, so anyone who
is affected can opt-in to the fixed behavior,
> Can you try changing the VirshSSH() class constructor so that it
passes echo=False to its superclass constructor, and see if that helps?
also - it seems like the class is trying to work around the fact it's
not disabling echo, by eliding the first line of the reply, in the run()
method - that
@seyeongkim, after reviewing this bug and looking at some of the data as
well as maas and pexpect code, it seems to me like this isn't related to
readline, I think the problem is maas is using pexpect without disabling
echo.
Can you try changing the VirshSSH() class constructor so that it passes
@nicolasbock before sponsoring, can you cover a few of the steps in the
SRU process:
1) The SRU template in the description isn't actually filled in, I think
you simply copy-n-pasted the actual template text in...it does need to
be actually filled out
2) This is marked as affecting f/h/i, but
for later reference, i'd discussed this with nick and asked him to check
if the 'status_request' reply contained any kind of valid data in the
specific cases where this patch will disable it; my concern is if there
is valid data in it, it's possible there are applications out there that
might
I'm unsubscribing sts-sponsors for now, please feel free to resubscribe
once this is ready for review/spsonsoring to focal.
Note that my understanding on this is that due to the added complexity
of the release and then revert of glibc in focal, due to bug 1914044,
any further upgrades to glibc
** Tags removed: sts-sponsor-ddstreet
** Tags added: sts-sponsor-dgadomski
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1921658
Title:
Can't compose kvm host with lvm storage on maas
sorry, @dgadomski has been out on vacation, i'll pick up the sponsoring
work for this while he's out.
@seyeongkim, can you please clean up the sru template information? @racb
is correct that the current info in the sru template doesn't explain
anything about what the actual readline bug is or how
@seyeongkim could you add the SRU template to the bug description?
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1921658
Title:
uploaded to b/f queues, thanks!
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1939853
Title:
mysqli: Using a cursor with get_result() and prepared statements
causes a segmentation fault
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1939853
Title:
mysqli: Using a cursor with get_result() and prepared statements
causes a segmentation
On Mon, Jul 12, 2021 at 7:49 AM Dariusz Gadomski
wrote:
>
> Hey Matthew,
> Despite not being called by name, I've decided to cut in, since I've been
> following the case anyway.
>
> I'll review and sponsor it for you.
Thanks @dgadomski!
Also @mruffell FYI you can just subscribe 'sts-sponsors'
** No longer affects: requests (Ubuntu)
** No longer affects: requests (Ubuntu Impish)
** No longer affects: requests (Ubuntu Hirsute)
** No longer affects: requests (Ubuntu Groovy)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug
** Description changed:
[Impact]
- somehow port is unbounded, then neutron-openvswitch-agent raise
+ somehow port is unbounded, then neutron-openvswitch-agent raise
OVSFWTagNotFound, then creating new instance will be failed.
[Test Plan]
1. deploy bionic openstack env
2. launch
On Thu, Apr 29, 2021 at 8:13 PM Matthew Ruffell
wrote:
>
> Hi Security Team,
>
> VISA opened a case, SF308725 - "openssl unable to process the certificate on
> Ubuntu 20.0" [1], about a minor regression in openssl 1.1.1f that affects
> both Focal and Groovy.
>
> [1]
>
** Description changed:
[Impact]
A connection session is opened, but the TLS parameters (timeout, ca,
cert and key) are not actually set for the session. This prevents use
of TLS for the etcd3gw package.
[Test Plan]
- # Create self signed certs
+ # Create self signed certs,
** Description changed:
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot
reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
minor comment, for systemd (and really all packages) I like to name the
patches with the lp bug number, so i changed your patch name to add the
lp1911187- prefix.
also another minor comment, as we'd discussed before I made a slight
change to the comment in the patch for clarification:
@joalif, one thing I noticed, that isn't important for this SRU, is that
the !ENABLE_LOGIND case still has a log message indicating shutdown will
happen immediately, i.e.:
int logind_schedule_shutdown(void) {
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => Ioanna Alifieraki (joalif)
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to t
** Changed in: systemd (Ubuntu Focal)
Assignee: Ioanna Alifieraki (joalif) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1911187
Title:
scheduled reb
** Tags removed: sts-sponsor-ddstreet
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820083
Title:
TLS params not set for session
Status in
** Tags removed: sts-sponsor-volunteer
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820083
Title:
TLS params not set for session
Status in
the python-oslo.vmware failures are almost certainly the same as bug
1912792
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1906720
Title:
Fix the disable_ssl_certificate_validation option
Review: Approve
LGTM, uploaded, thanks!
--
https://code.launchpad.net/~halves/ubuntu/+source/gnupg2/+git/gnupg2/+merge/396408
Your team STS Sponsors is requested to review the proposed merge of
~halves/ubuntu/+source/gnupg2:lp1910432-bionic into
ubuntu/+source/gnupg2:ubuntu/bionic-devel.
--
** Tags removed: sts-sponsor-ddstreet
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1906720
Title:
Fix the disable_ssl_certificate_validation option
** Changed in: gnupg2 (Ubuntu Groovy)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1910432
Title:
dirmngr doesn't work with kernel parameter
uploaded to f/g/h, thanks @halves!
One more minor comment for b added in the MR
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1910432
Title:
dirmngr doesn't work with kernel parameter
Review: Needs Fixing
one more minor comment inline below
Diff comments:
> diff --git
> a/debian/patches/dirmngr-handle-EAFNOSUPPORT-at-connect_server.patch
> b/debian/patches/dirmngr-handle-EAFNOSUPPORT-at-connect_server.patch
> new file mode 100644
> index 000..d926add
> --- /dev/null
>
Review: Approve
LGTM, uploaded to focal, thanks!
--
https://code.launchpad.net/~halves/ubuntu/+source/gnupg2/+git/gnupg2/+merge/396406
Your team STS Sponsors is requested to review the proposed merge of
~halves/ubuntu/+source/gnupg2:lp1910432-focal into
Review: Approve
LGTM, uploaded to g, thanks!
--
https://code.launchpad.net/~halves/ubuntu/+source/gnupg2/+git/gnupg2/+merge/396531
Your team STS Sponsors is requested to review the proposed merge of
~halves/ubuntu/+source/gnupg2:lp1910432-groovy into
ubuntu/+source/gnupg2:ubuntu/groovy-devel.
Review: Approve
LGTM, uploaded to h, thanks!
--
https://code.launchpad.net/~halves/ubuntu/+source/gnupg2/+git/gnupg2/+merge/396407
Your team STS Sponsors is requested to review the proposed merge of
~halves/ubuntu/+source/gnupg2:lp1910432-devel into
ubuntu/+source/gnupg2:ubuntu/devel.
--
attached updated debdiff with just minor adjustments:
- added tag "LP: #1906720" to changelog entry
- ran 'quilt refresh' on patch to fix offsets
- added DEP3 fields to patch (https://dep-team.pages.debian.net/deps/dep3/)
(in general, at least Origin: and Bug-Ubuntu: fields should be added)
-
** Tags added: sts sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1906720
Title:
Fix the disable_ssl_certificate_validation option
Status in python-httplib2 package in
sorry didn't click the checkbox on my inline comment last time
Diff comments:
> diff --git a/debian/changelog b/debian/changelog
> index fe05c72..6ada1d4 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +gnupg2 (2.2.19-3ubuntu3) focal; urgency=medium
as focal is an
Review: Needs Fixing
looks good, minor issue with version number bump
--
https://code.launchpad.net/~halves/ubuntu/+source/gnupg2/+git/gnupg2/+merge/396406
Your team STS Sponsors is requested to review the proposed merge of
~halves/ubuntu/+source/gnupg2:lp1910432-focal into
Review: Needs Fixing
looks good, minor issue with needing separate MR for groovy and hirsute.
Diff comments:
> diff --git a/debian/changelog b/debian/changelog
> index 974065a..493cd72 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +gnupg2 (2.2.20-1ubuntu2)
Review: Needs Fixing
Looks like this doesn't compile; the v4_valid and v6_valid variables aren't
present in the bionic code. However, it looks fairly simple to adjust for the
older code; can you take a look at it?
--
Oh and also openvswitch, bug 1906280
To summarize, here are all the applications (found so far) that thought
they needed to lock all their current and future memory:
slick-greeter (bug 1902879)
lightdm-gtk-greeter (bug 1890394)
corosync (bug 1911904)
openvswitch (bug 1906280)
--
You received
found another 'special' application that thinks it needs all its memory
locked: corosync.
opened bug 1911904
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting
** Tags added: sts sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1900617
Title:
gateway error detail is not passed along in raised exception
Status in python-etcd3gw
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1903733
Title:
Out of memory issue for websocket client
Status in python-tornado package in Ubuntu:
Fix
To clarify, the regression appears to be the same problem that the
rlimit increase is fixing, but the applications failing now are simply
bigger. In general, any application that calls mlockall() with
MCL_FUTURE, but doesn't adjust its rlimit (or change its systemd service
file to adjust
gt; fixed via SRU,
> > > > > without any concerns.
> > > > >
> > > > > Would you please evaluate this w/ customer/Lukasƶ on Monday?
> > > > >
> > > > >
> > > > > A bit on libkmod2 change:
> > > > >
> >
Hi Matthew,
As @mfo has done work in this (installer image) area before (LP:
#1807023) I asked him to take a look; I'm cc'ing our sts sponsors
email list (which includes Mauricio) also.
I think he's handling the sponsoring, so hopefully it'll make it for
the point release!
Thanks!
On Fri, Jul
** Also affects: nss (Ubuntu Groovy)
Importance: Medium
Assignee: Dariusz Gadomski (dgadomski)
Status: In Progress
** Also affects: nss (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: nss (Ubuntu Focal)
Assignee: (unassigned) => Dariusz Gadomski
marking verification-done-focal as i mentioned in comment 71
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Thanks @nicolasbock @mruffell! I think the latest changes make sense
and I think the shorter wait time in Xenial is ok, as systemd should
continue to restart it until it's successful.
I rebased @mruffell's debdiffs on the -proposed versions, and added a
short changelog entry, and uploaded to
uploaded to x/b/e/f/g, thanks!
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861177
Title:
seccomp_rule_add is very slow
Status in snapd:
Invalid
Status in libseccomp package in
> In addition I am uncertain why the service doesn't use
> `Type=notify` as in the later versions. Rabbitmq-server-3.6.10
> understands what `sd_notify` is and I would have thought that this
> implies that we should be able to use `Type=notify` on Bionic
our goal is to make the version in Bionic
> In the context of the issues we are seeing with charms the 10 minute
> timeout should be sufficient.
right, but this isn't just changing rabbitmq-server used by charms, this
is changing the behavior for *all* Ubuntu users of rabbitmq-server, as
well as upstream. Since upstream did accept it, my
@mruffell thanks! Only a few comments below:
> Note because of this bug, groovy and upstream has now been changed to
10 min timeout, down from 1hr.
We should decide if this is really what we want to do. And if it should
revert to the longer 1hr timeout, propose that upstream.
I don't really
@sil2100, last time I talked to @nicolasbock he was unclear on why it
was failing in bionic and passing in focal. I think probably the best
thing to do at this point is reject the versions in -proposed for x/b/f,
or just leave them in -proposed indefinitely, and he can take more time
to come up
@nicolasbock as we talked about, you can't just throw new changes into
Bionic without working on Focal/Groovy (and upstream) first.
Additionally, to address the actual change, I'm concerned you are adding
a config file to get the mnesia and rabbitmq timeouts to match - that
doesn't help anyone
Hi @nicolasbock, it looks like the latest debdiff is adding in a new
config file, and that change doesn't appear to be upstream, or even in
focal or groovy...can you clarify what that config file is needed and if
you'll work to get it upstream before it goes into bionic?
--
You received this bug
** Changed in: nfs-utils (Ubuntu Groovy)
Status: Fix Committed => In Progress
** Changed in: nfs-utils (Ubuntu Eoan)
Status: New => In Progress
** Changed in: nfs-utils (Ubuntu Bionic)
Status: New => In Progress
** Changed in: nfs-utils (Ubuntu Focal)
Assignee:
with the minor d/watch tweak we talked about in irc, LGTM thanks
@nicolasbock! Uploaded to groovy.
** Changed in: rabbitmq-server (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug
** Tags removed: sts-sponsor-slashd
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1878049
Title:
Upgrade rabbitmq-server to v3.8.3 from upstream
Status
** Summary changed:
- Update debian/watch file to download from GitHub
+ Upgrade rabbitmq-server to v3.8.3 from upstream
** Description changed:
- The current debian/watch file downloads from an outdated location.
+ rabbitmq-server FTBFS in Groovy, and needs to be upgraded to latest from
+
for groovy, the upstream merge is being worked in bug 1878049
** Changed in: rabbitmq-server (Ubuntu Groovy)
Assignee: (unassigned) => Nicolas Bock (nicolasbock)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
> - apart from feedback given by @mruffell, to also check if any of
librcu consumers are depending on a full membarrier - driven by kernel -
for ** shared pages among different processes **
this is a good point, although I don't think liburcu makes guarantees
like that, for memory barriers
@james-page, it looks like elixir-lang in groovy has exceeded the limit
that rabbitmq-server wants to build with; since our rabbitmq-server is
newer than Debian, I'm not sure what your merge process from upstream
is. Can you do another upstream merge please so rabbitmq-server is
buildable in
excellent analysis, thanks @mruffell!
uploaded to the bionic queue.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1876230
Title:
liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to
Hi @mruffell,
two questions for this sru:
1) it looks like static libs are built/provided by this package:
$ pull-lp-debs liburcu bionic ; for p in *.deb ; do echo "$p:" ; dpkg-deb -c $p
| grep -E '*\.a' ; done
Found liburcu 0.10.1-1 in bionic
Using existing file liburcu-dev_0.10.1-1_amd64.deb
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1876230
Title:
liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address
performance problems with
** Description changed:
[Impact]
In Linux 4.3, a new syscall was defined, called "membarrier". This
systemcall was defined specifically for use in userspace-rcu (liburcu)
to speed up the fast path / reader side of the library. The original
implementation in Linux 4.3 only supported
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1874075
Title:
rabbitmq-server startup timeouts differ between SysV and systemd
Status in rabbitmq-server
since this is in the Bionic unapproved upload queue already, i'm
removing ubuntu-sponsors. I'm leaving sts-sponsors subscribed to help
nudge the upload through until it reaches bionic-updates.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to
** Changed in: rabbitmq-server (Ubuntu Disco)
Status: Confirmed => Won't Fix
** Changed in: rabbitmq-server (Ubuntu Focal)
Assignee: (unassigned) => Nicolas Bock (nicolasbock)
** Changed in: rabbitmq-server (Ubuntu Eoan)
Assignee: (unassigned) => Nicolas Bock (nicolasbock)
**
Us to help with their own review/sponsoring practice, would
> >> help! :-)
> >>
> >> cheers,
> >>
> >> On Fri, Mar 27, 2020 at 10:50 PM Eric Desrochers
> >> wrote:
> >> >
> >> > I like the tag idea. What about &q
going thru my old watched bugs, here are some bugs that should be easy
to handle. Maybe we should figure out a LP bug tag to use for bugs
that we find that are good for potential sponsors, like seyeongkim, to
take?
https://bugs.launchpad.net/ubuntu/bionic/+source/nvme-cli/+bug/1800544
-super
** Description changed:
- [Description]
+ [Impact]
Systemd crashes when logging very long messages. This regression was
introduced with
upstream commit d054f0a4d451 [1] due to xsprintf.
- Commits e68eedbbdc98 [2] and 574432f889ce [3] replace some uses of xsprintf
with
+ Commits
** Tags removed: sts-sponsor-ddstreet
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847924
Title:
Introduce broken state parsing to mdadm
Status in mdadm
** Tags added: ddstreet-next
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1860548
Title:
systemd crashes when logging long message
Status in systemd package in Ubuntu:
Fix Released
re-uploaded the V3 to Bionic and Eoan, @rbasak @sil2100 does this change
address your concerns?
As this removes (comments out) the patches from bug 1850540, it no
longer needs to be blocked until a new kernel is released, as @gpiccoli
explains in comment 21.
--
You received this bug
Uploaded mdadm with V2 patches to B/D/E, however please note as I just
updated this bug description to explain, all future updates to mdadm are
now temporarily blocked due to the mdadm changes from bug 1850540
requiring corresponding kernel patches that are not yet released. I've
added the
uploaded to b/d/e, and i'll look at merging f next week and including
this patch.
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847924
Title:
** Description changed:
[Impact]
* Currently, mounted raid0/md-linear arrays have no indication/warning
when one or more members are removed or suffer from some non-recoverable
error condition. The mdadm tool shows "clean" state regardless if a
member was removed.
* The patch
** Bug watch added: Debian Bug tracker #943520
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943520
** Also affects: mdadm (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943520
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: mdadm (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847924
Title:
Introduce broken state parsing to mdadm
Status in
Thanks @gpiccoli; I can't sponsor this now, since Eoan is in final
freeze, but once it's released I'll be happy to sponsor.
** Changed in: mdadm (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: mdadm (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: mdadm
uploaded dbus and systemd to xenial queue, thanks!
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus
The patches are on the medium-to-large size, but I have reviewed them
and as far as I can tell they appear correct. The systemd patch is
needed to fix the cgroup-agent from overrunning the dbus socket
connection queue, and the dbus patches are needed to prevent a highly
loaded dbus message queue
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: dbus (Ubuntu)
Importance: Undecided => Medium
** Changed in: dbus (Ubuntu Xenial)
Importance: Undecided => Medium
** Tags added:
sponsored asterisk, prayer, and mailsync for e/d/b
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
Status in asterisk
sponsored for e,d,b,x
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1835818
Title:
snmpd causes autofs mount points to be mounted on service
start/restart
Status in net-snmp package in
** Tags added: sts-sponsor sts-sponsor-ddstreet
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1835818
Title:
snmpd causes autofs mount points to be mounted on service
start/restart
The systemd in eoan-proposed was version 243-rc1, which contained this,
but that has been reverted and the current version is back to 240, which
doesn't contain this. Discussion in #ubuntu-devel indicates eoan should
eventually have at least version 241, so I'm going to wait for that, and
then
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1668771
Title:
[SRU] systemd-resolved negative caching for
> Test with an IP address should not send SNI per the patch,
> so it should fail with the certificate verification error:
just to clarify as I was not clear at first:
-with TLSv1.3, some servers (as listed in description, e.g. gmail) require SNI
-if the client is accessing the server via DNS
** Also affects: uw-imap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916041
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
1 - 100 of 187 matches
Mail list logo
