Looks like upstream no longer needs this since they have embedded the
lens they need, so no point backporting this fix to stable releases. It
is fixed in the development release for the future.
** Changed in: augeas (Ubuntu Vivid)
Importance: High => Low
** Changed in: augeas (Ubuntu Wily)
Looks like upstream no longer needs this since they have embedded the
lens they need, so no point backporting this fix to stable releases. It
is fixed in the development release for the future.
** Changed in: augeas (Ubuntu Vivid)
Importance: High => Low
** Changed in: augeas (Ubuntu Wily)
** Also affects: augeas (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: augeas (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: augeas (Ubuntu)
Status: New => Triaged
** Changed in: augeas (Ubuntu Vivid)
Status: New => Triaged
** Also affects: augeas (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: augeas (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: augeas (Ubuntu)
Status: New => Triaged
** Changed in: augeas (Ubuntu Vivid)
Status: New => Triaged
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
We can't bump augeas in Vivid and Wily as they are already released, but
it looks like it should be fairly easy to cherry-pick just this fix
without regressing existing users. Is this accurate?
In this case, if
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
We can't bump augeas in Vivid and Wily as they are already released, but
it looks like it should be fairly easy to cherry-pick just this fix
without regressing existing users. Is this accurate?
In this case, if
Importance: High because I think it's important to the Ubuntu Server
Team to help ensure that Let's Encrypt works well on Ubuntu. Find me
(rbasak) in #ubuntu-server on Freenode during UK working hours if you
need any help.
** Changed in: augeas (Ubuntu)
Importance: Undecided => High
** Tags
Importance: High because I think it's important to the Ubuntu Server
Team to help ensure that Let's Encrypt works well on Ubuntu. Find me
(rbasak) in #ubuntu-server on Freenode during UK working hours if you
need any help.
** Changed in: augeas (Ubuntu)
Importance: Undecided => High
** Tags
I'm attaching the trio of commits to fix the bug in a single patch,
rebased on top of the upstream 1.3.0 release. Hopefully somebody can
use this as the basis of a patch against the package itself.
Locally it seems to resolve parsing of the ssl.conf file at
I'm attaching the trio of commits to fix the bug in a single patch,
rebased on top of the upstream 1.3.0 release. Hopefully somebody can
use this as the basis of a patch against the package itself.
Locally it seems to resolve parsing of the ssl.conf file at
With regards to manual regression testing for a stable update, I'd
suggest running "augtool print /files/etc/apache2" (with Apache, mod_ssl
and optionally, other Apache modules installed) to check if any files
that used to parse now fail in any way. Hopefully the number of errors
will be reduced.
With regards to manual regression testing for a stable update, I'd
suggest running "augtool print /files/etc/apache2" (with Apache, mod_ssl
and optionally, other Apache modules installed) to check if any files
that used to parse now fail in any way. Hopefully the number of errors
will be reduced.
The attachment "Patch against upstream release-1.3.0" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user
The attachment "Patch against upstream release-1.3.0" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user
This bug was fixed in the package augeas - 1.3.0-0ubuntu2
---
augeas (1.3.0-0ubuntu2) xenial; urgency=medium
* Fix parsing of Apache httpd ssl.conf files by cherry-picking three
commits from upstream (LP: #1510318):
- d/p/Httpd-Do-not-pass-empty-as-body-to-section.patch
This bug was fixed in the package augeas - 1.3.0-0ubuntu2
---
augeas (1.3.0-0ubuntu2) xenial; urgency=medium
* Fix parsing of Apache httpd ssl.conf files by cherry-picking three
commits from upstream (LP: #1510318):
- d/p/Httpd-Do-not-pass-empty-as-body-to-section.patch
> or just manually grab the .deb files from Xenial and install it on
Wily if you like - that should work
I should add that if you do this you should manually downgrade back to
packages from Wily later, to make sure that you receive any future
security updates.
--
You received this bug
> or just manually grab the .deb files from Xenial and install it on
Wily if you like - that should work
I should add that if you do this you should manually downgrade back to
packages from Wily later, to make sure that you receive any future
security updates.
--
You received this bug
Thanks Dominic. I've uploaded this to Xenial, which as it is for the
development release I don't have to worry as much about regressing
existing users.
Can someone confirm that the problem with letsencrypt is fixed with
Xenial, please (or just manually grab the .deb files from Xenial and
install
Thanks Dominic. I've uploaded this to Xenial, which as it is for the
development release I don't have to worry as much about regressing
existing users.
Can someone confirm that the problem with letsencrypt is fixed with
Xenial, please (or just manually grab the .deb files from Xenial and
install
20 matches
Mail list logo
