Ubuntu
apache2 package

Merge ~bryce/ubuntu/+source/apache2:sru-lp1565744-apache-lock-dir into ubuntu/+source/apache2:ubuntu/xenial-devel

  1. Git
  2. lp:~bryce/ubuntu/+source/apache2
  3. sru-lp1565744-apache-lock-dir
  4. Merge into ubuntu/xenial-devel
Proposed by Bryce Harrington
Status: Needs review
Proposed branch: ~bryce/ubuntu/+source/apache2:sru-lp1565744-apache-lock-dir
Merge into: ubuntu/+source/apache2:ubuntu/xenial-devel
Diff against target: 30 lines (+12/-1)
2 files modified
debian/apache2.install (+4/-1)
debian/changelog (+8/-0)
Reviewer Review Type Date Requested Status
Christian Ehrhardt  (community) Needs Information
Review via email: mp+393891@code.staging.launchpad.net

Description of the change

PPA: https://launchpad.net/~bryce/+archive/ubuntu/apache2-sru-lp1899611-conf-in/

Backports a Debian fix for installation of config files, so can avoid installing *.in templates. Fixes an issue from an earlier SRU that causes an apache2.conf.in file to get installed.

I plan to include this SRU with the xenial fix for lp #1832182 (see https://code.launchpad.net/~bryce/ubuntu/+source/apache2/+git/apache2/+merge/393678), but am MP'ing this separately for review convenience.

I haven't filled in the SRU text yet, but the bug report is pretty clear and the test case obvious. I do plan to fill in a proper SRU before upload.

To post a comment you must log in.
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Straightforward case and fix, I found no issues other than "on its own" it would be debatable if it is worth an update. But since you plan to upload the fixes together that is ok.

One question thou, since we have placed things in /etc/ they will be config files.
Therefore "not delivering" them will not remove them from disk.

Is there a chance that people started to (wrongly) use that file and it would be active?

If not I think we should we also add an rm_conffile along the fix.

review: Needs Information
Reply
Revision history for this message
Bryce Harrington (bryce) wrote :

It couldn't be active because it's not a validly formatted config file so would generate an error.

Apache by default uses apache2.conf, not apache2.conf.in. You'd really need to go out of your way to make Apache read apache2.conf.in instead. So I think the utility of removing the file is going to be pretty low. And yeah, I wouldn't have bothered with this as SRU except that I have another one it can easily ride in on.

Reply

There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches