Bug#438152: apache2-utils: htpasswd, htpasswd.1.gz in several packages

2007-08-15 Thread Christopher Wood
Package: apache2-utils Version: 2.2.4-3 Severity: normal I received this error when trying to install apache2, without first uninstalling thttpd and thttpd-util: dpkg: error processing /var/cache/apt/archives/apache2-utils_2.2.4-3_i386.deb (--unpack): trying to overwrite `/usr/bin/htpasswd',

Processed: Re: Bug#438152: apache2-utils: htpasswd, htpasswd.1.gz in several packages

2007-08-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 438152 thttpd-util Bug#438152: apache2-utils: htpasswd, htpasswd.1.gz in several packages Bug reassigned from package `apache2-utils' to `thttpd-util'. found 438152 2.23beta1-7 Bug#438152: apache2-utils: htpasswd, htpasswd.1.gz in several

Bug#438152: apache2-utils: htpasswd, htpasswd.1.gz in several packages

2007-08-15 Thread Stefan Fritsch
reassign 438152 thttpd-util found 438152 2.23beta1-7 thanks thttpd-util version 2.23beta1-5 (in etch) has thtpasswd instead of htpasswd. So this was changed to htpasswd in thttpd-util version 2.23beta1-7 (possibly by accident, it is not noted in the changelog). Reassigning to thttpd-util.

apache2_2.2.3-4+etch1_i386.changes INSTALLED into stable

2007-08-15 Thread Debian Installer
Installing: apache2-doc_2.2.3-4+etch1_all.deb to pool/main/a/apache2/apache2-doc_2.2.3-4+etch1_all.deb apache2-mpm-event_2.2.3-4+etch1_i386.deb to pool/main/a/apache2/apache2-mpm-event_2.2.3-4+etch1_i386.deb apache2-mpm-perchild_2.2.3-4+etch1_all.deb to

Bug#301702: marked as done (apache2 start failed during restart when logs rotated)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#425248: marked as done (apache2.2-common: apache2 may be killed by logrotate job)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#298689: marked as done (apache2: logrotate script and new init script break ssl certificates with passphrase)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#400455: marked as done (apache2.2-common: /etc/init.d/apache2 restart can kill apache)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#314878: marked as done (apache2-common: Do 'reload' instead of 'restart' in logrotate.d/apache2)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#334824: marked as done (logrotate: Postrotate documentation - Why restart?)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#398223: marked as done (apache2: [notice] caught SIGTERM, shutting down)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#325594: marked as done (apache2: Unable to restart after security upgrade)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#429516: marked as done (apache2-common logrotate : could reload be used instead of restart ?)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#423653: marked as done (apache2.2-common: mod_disk_cache fills /var after etch upgrade)

2007-08-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Aug 2007 22:01:20 + with message-id [EMAIL PROTECTED] and subject line Bug#423653: fixed in apache2 2.2.3-4+etch1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

The status of libapache2-mod-perl2

2007-08-15 Thread Gunnar Wolf
Hi all, I'm sending this mail as an answer to #438168 - A user (understandably) fed up by what seems to be lack of attention to a package that is core to many people's work, libapache2-mod-perl2. I send this mail with some fear, of course, as I do not really want to adopt it - but... Well, the

Re: The status of libapache2-mod-perl2

2007-08-15 Thread Steinar H. Gunderson
On Wed, Aug 15, 2007 at 09:32:30PM -0500, Gunnar Wolf wrote: Of course, before any action, I'd like to hear Thom's or Andres' points of view. You probably want to hear my input too. :-) At Debconf5, I was more or less persuaded into taking the package (up to the level where I actually had the

Re: The status of libapache2-mod-perl2

2007-08-15 Thread Don Armstrong
On Wed, 15 Aug 2007, Gunnar Wolf wrote: - Should we hijack/adopt the package, or will its current maintainers stand up and get it back to life? I also found myself looking at this package recently too; whether it's under the perl group, debian-apache, or some other team, I'd be happy to