Processing of apache2_2.0.55-4_multi.changes

2006-01-16 Thread Archive Administrator
apache2_2.0.55-4_multi.changes uploaded successfully to localhost along with the files: apache2-common_2.0.55-4_i386.deb apache2-mpm-prefork_2.0.55-4_powerpc.deb apache2-prefork-dev_2.0.55-4_powerpc.deb apache2-mpm-worker_2.0.55-4_i386.deb apache2-utils_2.0.55-4_i386.deb

Bug#307921: marked as done (apache2-prefork-dev: should mention apxs in package description)

2006-01-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Jan 2006 04:32:05 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#307921: fixed in apache2 2.0.55-4 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 now

Bug#330275: marked as done (apache2: init script exits with 0 when called incorrectly)

2006-01-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Jan 2006 04:32:05 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#330275: fixed in apache2 2.0.55-4 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 now

Bug#339323: marked as done (apache2-common: /etc/init.d/apache2 throws away error information [patch])

2006-01-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Jan 2006 04:32:05 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#339323: fixed in apache2 2.0.55-4 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 now

Bug#340761: marked as done (apache2 debian/rules missing many set -e)

2006-01-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Jan 2006 04:32:05 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#340761: fixed in apache2 2.0.55-4 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 now

Bug#345922: marked as done (options error in Apache config file)

2006-01-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Jan 2006 04:32:05 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#345922: fixed in apache2 2.0.55-4 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 now

2 neue Kontaktanzeige(n) fuer Dich

2006-01-16 Thread email-partner.com
1 Million neue Baeume fuer die Welt - jetzt dabeisein und sogar mitverdienen! http://email-partner.com/nlforestation.asp

Comunicado

2006-01-16 Thread Departamento Comercial
Estimados Señores, Martin Sons, S.L. les comunica que al instalar las nuevas herramientas de Marketing, por error hemos borrado la lista de bajas. Lamentamos todas las molestias y agradecemos que si sigue interesado en dar de baja su dirección de correo, basta enviar un e-mail a [EMAIL

Bug#348454: apache*: default logrotate conf is overkill

2006-01-16 Thread Jmax1632
Package: apache* Version: all apache versions (afaik) Severity: normal On a debian server I manage, and this one I use as a desktop, I have found that the default configuration in logrotate.d for apache install keeps logs for a year. This is overkill, imho, and has led to two servers i know of

Bug#348454: apache*: default logrotate conf is overkill

2006-01-16 Thread Andrew
I disagree regarding the over-kill. In some countries there are laws which dictate the duration that logs are kept for. Regardless, it is up to you to have good monitoring system in place. The simplest solution would be to change to log rotation configuration on your system. I am happy

Bug#348454: marked as done (apache*: default logrotate conf is overkill)

2006-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2006 14:05:04 +1100 with message-id [EMAIL PROTECTED] and subject line Bug#348454: apache*: default logrotate conf is overkill 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

Bug#348474: invoke-rc.d apache-perl restart doesn't reload perl modules

2006-01-16 Thread Geoff Crompton
Package: apache-perl Version: 1.3.33-6sarge1 Severity: normal The /etc/init.d/apache-perl script sends a signal HUP to apache-perl when called with the restart option. The apache doco says that this causes the parent to kill it's children, re-read it's config files, and re open the log files.