I think that’s the problem - the script doesn’t only delete or create the symlinks, but it records whether admin or maintainer did the change, and honors the choice. Otherwise the package has no way to know whether the link is missing because of the upgrade or by mistake, and recreates the links.
Ondrej -- Ondřej Surý (He/Him) > On 30. 8. 2024, at 16:52, Ralf Bergs <ralf+deb...@bergs.biz> wrote: > > >> On 2024-08-30 12:58, Ondřej Surý wrote: >> your report is missing the information on **how** did you disabled >> serve-cgi-bin.conf? > Ah, sorry. > > I manually deleted the link from conf-available/ to conf-enabled/. > > I later had some doubts whether I had asked for problems by doing so, I > checked the a2disconf script, and if I'm not mistaken it basically does the > same thing. In any case I didn't find evidence that the script "registered" > this action somewhere, which would be the precondition for not > "force-enabling" it later... >
