For those who can't wait, I've built a version with this fix in my PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422795
Title:
bash crashes often if inputrc contains revert-all-at-newline
To
It seems like the ball has been dropped on this, possibly by me. Is
there something I need to do to get someone to upload a new version
using the debdiff I provided?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I apparently forogt to actually attach the config fragment that
reproduces the problem.
** Attachment added: "Configuration fragment for test case"
https://bugs.launchpad.net/ubuntu/trusty/+source/apache2/+bug/1504354/+attachment/4497261/+files/ifdefine-test.conf
--
You received this bug
apache 2 2.4.7-1ubuntu4.8 (in trusty-proposed) both passes the test case
and fixes my original problem.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
apache 2 2.4.7-1ubuntu4.8 (in trusty-proposed) both passes the test case
and fixes my original problem.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I apparently forogt to actually attach the config fragment that
reproduces the problem.
** Attachment added: "Configuration fragment for test case"
https://bugs.launchpad.net/ubuntu/trusty/+source/apache2/+bug/1504354/+attachment/4497261/+files/ifdefine-test.conf
--
You received this bug
** Bug watch added: Debian Bug tracker #747341
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341
** Also affects: bash (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
This was reported to the bug-bash mailing list and has been fixed
upstream, but there doesn't appear to be a bug tracker.
** Also affects: gnubash
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This was fixed in 4.3-8 and so is already fixed in utopic and later. It
will require an SRU to fix in trusty. I've attached a debdiff
containing the needed change.
** Description changed:
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341
The Debian bug includes complete
On Tue, 2015-10-13 at 11:00 +, Robie Basak wrote:
> Fix -D[efined] or [d] variables lifetime across restarts. This
> fixes incorrect processing of configuration files on reload (LP:
> #1504354).
>
> If you let me know that you're happy with that text then I can just
> change it when I upload
On Tue, 2015-10-13 at 11:00 +, Robie Basak wrote:
> Fix -D[efined] or [d] variables lifetime across restarts. This
> fixes incorrect processing of configuration files on reload (LP:
> #1504354).
>
> If you let me know that you're happy with that text then I can just
> change it when I upload
2.4.7-1ubuntu4.7 fixes my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1445914
Title:
Secure web socket proxy does not work in Apache 2.4.7
To manage notifications about this bug
2.4.7-1ubuntu4.7 fixes my problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1445914
Title:
Secure web socket proxy does not work in Apache 2.4.7
To manage notifications about
Public bug reported:
A bug in the Apache2 HTTP server results in invalid memory references
in the ap_server_config_defines array after a graceful restart. This
can result in server config variables defined by means of the Define
directive appearing to be undefined after a graceful restart. This
** Patch added: "debdiff containing the upstream patch"
https://bugs.launchpad.net/apache2/+bug/1504354/+attachment/4489268/+files/server_config_defines.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
** Patch added: "debdiff containing the upstream patch"
https://bugs.launchpad.net/apache2/+bug/1504354/+attachment/4489268/+files/server_config_defines.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A bug in the Apache2 HTTP server results in invalid memory references
in the ap_server_config_defines array after a graceful restart. This
can result in server config variables defined by means of the Define
directive appearing to be undefined after a graceful restart. This
Try this one. Note I omitted the Author tag. It's not clear to me that
it's intended to name the author of the upstream patch, which in any
case is available in the upstream bug, the upstream commit, and the
debian/changelog entry. I myself have no authorship stake in this
patch.
Note that
Try this one. Note I omitted the Author tag. It's not clear to me that
it's intended to name the author of the upstream patch, which in any
case is available in the upstream bug, the upstream commit, and the
debian/changelog entry. I myself have no authorship stake in this
patch.
Note that
The upstream patch (see attached debdiff) corrects the problem for me,
for an internal test case that is unfortunately too complex to share.
** Patch added: "debdiff containing the upstream patch"
The upstream patch (see attached debdiff) corrects the problem for me,
for an internal test case that is unfortunately too complex to share.
** Patch added: "debdiff containing the upstream patch"
Public bug reported:
The IMAP QUOTA extension permits the list of resource-usage-limit tuples
in an untagged QUOTA response to be empty (see RFC2087 section 5.1,
which states The list contains zero or more triplets. This happens
when the server supports quotas, but no quota is set on a
** Description changed:
The IMAP QUOTA extension permits the list of resource-usage-limit tuples
in an untagged QUOTA response to be empty (see RFC2087 section 5.1,
which states The list contains zero or more triplets. This happens
when the server supports quotas, but no quota is set on
** Description changed:
The IMAP QUOTA extension permits the list of resource-usage-limit tuples
in an untagged QUOTA response to be empty (see RFC2087 section 5.1,
which states The list contains zero or more triplets. This happens
when the server supports quotas, but no quota is set on
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1204195
Title:
OpenAFS Security Advisories 2013-0003 and 2013-0004
To manage
Yes, the patch updates the package to 1.6.1-6. That actually seems
appropriate to me in this case. The only code changes since 1.6.1-1 are the
(four!) security patches in 1.6.1-6, only one of which is the one mentioned in
this bug. Other changes relate only to packaging:
- Update to
The following patch fixes the problem by *not* replacing ntp servers
with an address beginning with 127.
No, it doesn't. It masks the problem by removing only servers with a
name or address that starts with something other than a '1', followed by
something other than a '2', followed by
The following patch fixes the problem by *not* replacing ntp servers
with an address beginning with 127.
No, it doesn't. It masks the problem by removing only servers with a
name or address that starts with something other than a '1', followed by
something other than a '2', followed by
This was never in precise; it was fixed upstream in 1.4.4, so doesn't
affect anything newer than lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/857663
Title:
cups crashes on SIGHUP if printer
need is an awfully strong word.
As documented, the resolution mechanism compares priorities on the
affected modules to determine which one to use in case of a conflict.
That's what guarantees the result is what you want, or at least what the
package maintainers wanted the default behavior to be
That's all very nice, but what about the underlying problem?
The problem is not fixed; it is merely masked. See my comments #6, 7, 8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/663319
sigh /
The symbol mentioned in the original error message (oid_id_pkcs3_rc2_cbc) comes
from libasn1.so.8. The actual cause of this problem is that that symbol, along
with several others, were renamed (a backward-incompatible ABI change) without
a corresponding change in soname. Since
It's been suggested that I point out the only viable solution here is to
reintroduce the missing symbols in libasn1.so.8. While it would have
been reasonable to bump the soname version before releasing the
backward-incompatible library in the first place, the only way now to
fix the problem
As noted, this is really due to a backward-incompatible ABI change in
libasn1-8-heimdal
** Package changed: libpam-heimdal (Ubuntu) = heimdal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
34 matches
Mail list logo
