Le 03/05/2025 à 16:22, Pirate Praveen a écrit :
On Sun, 27 Apr 2025 17:29:03 +0200 Chris Hofstaedtler <z...@debian.org>
wrote:
Here's a scripted reproducer:
mmdebstrap --variant=apt --chrooted-customize-hook='cd / && apt
download javascript-common && dpkg -i ./javascript-common_*.deb &&
rm /etc/apache2/conf-available/javascript-common.conf && apt install -
y apache2 && dpkg -i ./javascript-common_*.deb' stable /dev/null
I'll note this already happens with the version in stable.
Raising severity to serious, as per my understanding of the policy,
removing a conffile is a supported action, and maintainer scripts must
not fail in this case.
A workaround should be:
dpkg -i --reinstall ./javascript-common_*.deb
(Which should restore the missing conffiles.)
That file is the core part of the package. I wonder what it is supposed
to do if that is missing?
/etc/apache2/conf-available/javascript-common.conf
Without this file, the package becomes useless (if using apache2). Does
it really make sense to ignore this missing conf file in maintscripts?
This looks to me like a user error.
If that file is really mandatory, maybe installing the package should
create/recreate it then? If not, what package is supposed to create the
file?
In the current state, the package can't even be reinstalled because the
file is not created by the package but the script depends on it. Can't
see the logic here.
