The new upstream bug (88844) is unfortunately private and I can't see
its state.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to mysql-5.7 in Ubuntu.
Matching subscriptions: main
https://bugs.launchpad.net/bugs/1729536
Title:
InnoDB:
Upstream server about using IP_FREEBIND:
https://bugzilla.mindrot.org/show_bug.cgi?id=2512
** Bug watch added: OpenSSH Portable Bugzilla #2512
https://bugzilla.mindrot.org/show_bug.cgi?id=2512
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=2512
Importance:
** Description changed:
[Availability]
Package is in universe since trusty:
$ rmadison http-parser
http-parser | 2.1-2 | trusty/universe | source
http-parser | 2.1-2 | xenial/universe | source
http-parser | 2.1-2 | artful/universe | source
http-parser | 2.7.1-2 |
** Tags removed: zesty
** Tags added: 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/1638957
Title:
[MIR] http-parser, dependency of sssd
To manage notifications about this bug go
** Description changed:
Please enable the sssd-secrets service. This needs the MIR for http-
parser (#1638957) to pass.
+ [Rationale]
+ From the MIR bug (#1638957):
+ The Debian sssd package has the secrets service enabled, and disabling it in
the Ubuntu package is part of the delta we
I've marked this incomplete until we can recreate it.
** Changed in: python-cryptography (Ubuntu Bionic)
Status: Fix Released => Incomplete
** No longer affects: python-cryptography (Ubuntu Artful)
** No longer affects: python-cryptography (Ubuntu)
** No longer affects:
Public bug reported:
Please enable the sssd-secrets service. This needs the MIR for http-
parser (#1638957) to pass.
[Rationale]
>From the MIR bug (#1638957):
The Debian sssd package has the secrets service enabled, and disabling it in
the Ubuntu package is part of the delta we carry.
The
Hi Graham,
I don't think this is a dependency issue. I'm going to back out the
changes I made earlier as I pulled the trigger too quickly with those.
What would be good to know is what 'buf' is set to in your scenario.
Here's a little script that hits the same path your traceback goes down.
It
** Description changed:
[Availability]
Package is in universe since trusty:
$ rmadison http-parser
http-parser | 2.1-2 | trusty/universe | source
http-parser | 2.1-2 | xenial/universe | source
http-parser | 2.1-2 | artful/universe | source
http-parser | 2.7.1-2 |
** Description changed:
[Availability]
Package is in universe since trusty:
$ rmadison http-parser
http-parser | 2.1-2 | trusty/universe | source
http-parser | 2.1-2 | xenial/universe | source
http-parser | 2.1-2 | artful/universe | source
http-parser | 2.7.1-2 |
** Description changed:
[Availability]
Package is in universe since trusty:
$ rmadison http-parser
http-parser | 2.1-2 | trusty/universe | source
http-parser | 2.1-2 | xenial/universe | source
http-parser | 2.1-2 | artful/universe | source
http-parser | 2.7.1-2 |
** Description changed:
[Availability]
Package is in universe since trusty:
$ rmadison http-parser
http-parser | 2.1-2 | trusty/universe | source
http-parser | 2.1-2 | xenial/universe | source
http-parser | 2.1-2 | artful/universe | source
http-parser | 2.7.1-2 |
** Description changed:
[Availability]
Package is in universe since trusty:
$ rmadison http-parser
- http-parser | 2.1-2 | trusty/universe | source
- http-parser | 2.1-2 | xenial/universe | source
- http-parser | 2.1-2 | artful/universe | source
- http-parser | 2.7.1-2 |
13 matches
Mail list logo
