Bug#214480: apache-common: modules-config modules locations issue
reassign 214480 libapache-mod-gzip
severity 214480 normal
stop
quit
thanks
The problem is located in the 510mod_gzip.info. The LoadModule: line is
ambiguos and modules-config can't cope with it.
The first line of the .info file in each module should point to the
correct place where the module is located.
Fabio
On Mon, 6 Oct 2003, Dan Weber wrote:
> Package: apache-common
> Version: 1.3.28-1
> Severity: important
> Tags: sid
>
> modules-config currently looks libapache-mod-gzip in wrong location.
> Thus anybody who has mod-gzip on their machine will have issues
> upgradeing since apache shows errors on start saying it can't find
> mod-gzip in /usr/lib/modules/mod_gzip.so which it really is in
> /usr/lib/apache/1.3.
>
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux mirrorlynx.com 2.6.0-test6-mm4-quota #1 Mon Oct 6 15:38:15 EDT 2003 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache-common depends on:
> ii debconf 1.3.14 Debian configuration management sy
> ii libc6 2.3.2-8 GNU C Library: Shared libraries an
> ii libdb4.1 4.1.25-9 Berkeley v4.1 Database Libraries [
> ii libexpat1 1.95.6-6 XML parsing C library - runtime li
> ii mime-support 3.23-1 MIME files 'mime.types' & 'mailcap
> ii perl [perl5] 5.8.1-2 Larry Wall's Practical Extraction
>
> -- debconf information:
> * apache-common/confignotes:
> apache-shared/restart: true
> apache-shared/debconf-modules: mod_env, mod_log_config, mod_mime_magic, mod_mime, mod_negotiation, mod_status, mod_autoindex, mod_dir, mod_cgi, mod_imap, mod_userdir, mod_alias, mod_rewrite, mod_access, mod_auth, mod_auth_dbm, mod_auth_db, mod_expires, mod_unique_id, mod_setenvif, mod_perl, mod_ssl, mod_fastcgi, mod_php4, mod_speedycgi
> apache-common/old-logrotate-exists:
> * apache-common/logs:
>
>
--
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues
http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp00004.html
Reply to: