The problem appears to come down to the a2dismod being called inside a check for "purge" in the prerm script.
prerm does not get called for "purge", only "remove". postrm gets called with "purge" or with "remove". https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-mscriptsinstact prerm cannot expect to be called with "purge", that is not Policy Compliant. * uwsgi needs to use a2dismod in prerm upon the "remove" (and "deconfigure") command as that is when the .so is removed, leaving the dangling symlink which trips up Apache. This is how wsgi does it. * uwsgi may also (like wsgi) choose to use a2dismod upon "purge" in the postrm. So this is a packaging bug in uwsgi - the a2dismod is never called. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
pgp1FPglpkZQx.pgp
Description: OpenPGP digital signature
