That file is the core part of the package. I wonder what it is supposed to do if that is missing?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/nullI'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.)
/etc/apache2/conf-available/javascript-common.confWithout 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.
OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature