Package: javascript-common Version: 5 Followup-For: Bug #474913
We have a large number of virtual servers with javascript files rooted to "/javascript". The /etc/javascript-common/javascript-common.conf file overrode all of those configurations when the server was restarted. It took a little while to work out what the problem was. I'd like to suggest that such a configuration change should be made more visible to the person upgrading the system and should provide a choice about whether or not is should be enabled. Thanks Rory -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.19.1clw1206clw (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages javascript-common depends on: ii wwwconfig-common 0.1.2 Debian web auto configuration javascript-common recommends no packages. Versions of packages javascript-common suggests: ii apache2-mpm-prefork [httpd] 2.2.9-10 Apache HTTP Server - traditional n -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
