Augeas 1.3 can't read some conf files

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 somebody can prepare and test a backported patch for 1.3.0-0ubuntu1, I will be happy to help drive this to a fix in Wily, Vivid and Xenial which all currently are on that version.

I will need a commitment from someone to verify the fix for each release as even though I appreciate there is an automated test case, we do still require manual verification for updates to stable releases in order to minimise risk of regression to existing users.

If you're interested in the process, it is documented at https://wiki.ubuntu.com/StableReleaseUpdates

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.

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 https://github.com/letsencrypt/letsencrypt/issues/981#issuecomment-148485384.

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 owned by ~brian-murray, for any issues please contact him.]

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 it on Wily if you like - that should work)? As I'm just blindly cherry-picking patches here, I'd prefer if someone affected could confirm, and then I'll upload SRUs for Vivid and Wily.

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
    - d/p/Httpd-Make-illegal-in-char_arg_dir.patch
    - d/p/Httpd-Properly-manage-eol-after-opening-tag.patch

 -- Robie Basak <email address hidden> Tue, 27 Oct 2015 12:26:38 +0000

> 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.

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.