[Bug 387189] Re: /dev/null corrupted (/dev/null.1)

[Jonathan Marsden]

OK.  Do we have a test case for which my patch fails?

If the remaining issue is that my patch contains a closing '}', that is
easily "solved", because the {} around the variable name are only there
for style reasons, and are not required.

Here is a modified patch without the {} .  Is there a test case for
which this one fails?

If this issue is deemed significant enough to SRU for Hardy and Lucid,
then it seems easier to me to get a small patch to one script accepted,
than to get a newer version of logrotate accepted.

Is it better to backport the logrotate patch?  To do both the logrotate
patch *and* fix the apache2 logrotate script?

** Patch added: "modified patch that contains no brackets"
   https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/387189/+attachment/1818595/+files/logrotate-apache2-no-brackets.diff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
https://bugs.launchpad.net/bugs/387189

Title:
  /dev/null corrupted (/dev/null.1)