Package: apache2-mpm-prefork Version: 2.0.50-8 Severity: important mod_userdir is forcibly enabled when apache2 is upgraded. This should not happen because it should be up to the admin to decide whether they want a module enabled especially on an upgrade which has the potential to break things. It is very annoying to have to manually disable userdir after the upgrade. I can think of no good reason for doing this as mod_userdir is not required for the default apache.conf to work.
-- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686-smp Locale: LANG=en_NZ, LC_CTYPE=en_NZ Versions of packages apache2-mpm-prefork depends on: ii apache2-common 2.0.50-8 Next generation, scalable, extenda ii libapr0 2.0.50-8 The Apache Portable Runtime ii libc6 2.3.2.ds1-15 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-16 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.6-8 XML parsing C library - runtime li ii libldap2 2.1.30-3 OpenLDAP libraries ii libssl0.9.7 0.9.7d-5 SSL shared libraries ii zlib1g 1:1.2.1.1-5 compression library - runtime -- no debconf information