Bug#794933: apache2-suexec-custom: prompting due to modified conffiles which were not modified by the user: /etc/apache2/conf-available/security.conf
On 2015-08-08 22:34, Stefan Fritsch wrote:
> On Saturday 08 August 2015 11:38:14, Andreas Beckmann wrote:
>> This was observed while doing a wheezy -> jessie -> stretch upgrade
>> test. I did not see such behavior while testing the other apache
>> packages.
This now shows up on all (or at least a lot of) upgrade paths involving
apache packages (many php packages among them), so apache2-suexec-custom
was only the first to fail.
Always while "Setting up apache2 (2.4.16-1)".
> AFAICS, this happens when one upgrades from wheezy from a state where
> only apache2.2-common is installed but not apache2. There is a bug in
> apache2's preinst in jessie that makes it not recognize this case and
> not execute the conffile handling.
>
> While I think I have a fix, I am not not sure that I want to change
> the upgrade logic in a stable point release.
I haven't seen this bug in upgrades to jessie so far, only in the
followup upgrade to stretch. This could be the case if that conffile has
not changed between wheezy and jessie, but changes from jessie to
stretch ... (and it would blow up in jessie, too, if you would ever have
to ship an updated version of that conffile in jessie).
So maybe it is not neccessary to fix it in jessie if it can be fixed in
stretch instead.
If you have a patch, I could check the specific upgrade paths in my
piuparts setup (without uploading to sid and waiting for a migration to
testing).
> I will have to think about it. If you are at debconf, maybe we can
> talk about it there.
No, I'll be on holidays then ...
Andreas
Reply to: