Bug#396162: /etc/init.d/apache2 still has wrong logic in PID detection

Package: apache2-common Version: 2.2.3-2 Severity: important Tags: patch In /etc/init.d/apache2 (my comments are after # sign): pidof_apache() { ... # This loop returns from procedure with first PID it encounters in # existing .pid file no matter PidFile is from the right source or not.

Processed: tagging bugs that are closed by packages in NEW as pending

Processing commands for [EMAIL PROTECTED]: > # the following bugs are closed by packages in NEW > # > tags 316858 pending Bug#316858: should not die in case of broken link There were no tags set. Tags added: pending > tags 349016 pending Bug#349016: apache2: deflate.conf default There were no tag

apache2_2.2.3-3_amd64.changes is NEW

apache2-doc_2.2.3-3_all.deb to pool/main/a/apache2/apache2-doc_2.2.3-3_all.deb apache2-mpm-event_2.2.3-3_amd64.deb to pool/main/a/apache2/apache2-mpm-event_2.2.3-3_amd64.deb apache2-mpm-perchild_2.2.3-3_all.deb to pool/main/a/apache2/apache2-mpm-perchild_2.2.3-3_all.deb apache2-mpm-prefork_2.

Re: Bug#395936: Apache2 SSL service stopped working since upgrade to 2.2.3-2

Sorry, that didn't solve the problem. Relevant vhost config follows. Notice; this config did work with the previous version of apache2 in Debian testing. SSLRandomSeed startup builtin SSLRandomSeed connect builtin AddType application/x-x509-ca-cert .crt AddType applicati

Processing of apache2_2.2.3-3_amd64.changes

apache2_2.2.3-3_amd64.changes uploaded successfully to localhost along with the files: apache2_2.2.3-3.dsc apache2_2.2.3-3.diff.gz apache2.2-common_2.2.3-3_amd64.deb apache2-mpm-worker_2.2.3-3_amd64.deb apache2-mpm-prefork_2.2.3-3_amd64.deb apache2-mpm-event_2.2.3-3_amd64.deb apache2-

Processed: tagging 395828, merging 391918 395828

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > tags 395828 + pending Bug#395828: apache2.2-common: suexec is not detected by apache2 There were no tags set. Tags added: pending > merge 391918 395828 Bug#391918: apache2.2-common:

Bug#238051: marked as done (apache2-common: mod_disk_cache causes segfaults for apt queries)

Your message dated Sun, 29 Oct 2006 21:30:50 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#238051: apache2-common: mod_disk_cache causes segfaults for apt queries has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#354393: marked as done ("/etc/init.d/apache2 stop" shows error if apache2/conf.d is empty)

Your message dated Sun, 29 Oct 2006 20:54:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#354393: "/etc/init.d/apache2 stop" shows error if apache2/conf.d is empty has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#351858: marked as done (apache2: invalid HTML default directory listings)

Your message dated Sun, 29 Oct 2006 20:57:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#351858: apache2: invalid HTML default directory listings 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 n

Bug#274891: apache2-mpm-worker: mod_autoindex listings show incorrect last-modified date

* Mark Lord | mod_autoindex in Apache2 shows incorrect datestamps for last-modified | when displaying directory names as part of a directory index. | Files appear to display with the correct last-modified, but many | directories on my system all just show up with "11-Aug-2004 23:40", | including

Bug#350119: marked as done (apache2-common: better pidfile search (patch provided))

Your message dated Sun, 29 Oct 2006 20:48:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Script rewritten in 2.2.3-2 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 your respon

Bug#252465: marked as done ([Apache2] Wrong MIME type for .tgz)

Your message dated Sun, 29 Oct 2006 20:40:11 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 2.2 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 your responsibility to reo

Bug#364182: marked as done (apache2.conf: .tgz cannot be x-tar)

Your message dated Sun, 29 Oct 2006 20:40:11 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 2.2 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 your responsibility to reo

Bug#395828: apache2.2-common: suexec is not detected by apache2

retitle 395828 suexec: suexec wrapper has wrong permissions thanks. The Suexec wrapper and module are in the right path. The permissions are wrong: $ ls -la "/usr/lib/apache2/suexec" -rwxr-xr-x 1 root root 12776 Oct 7 00:10 /usr/lib/apache2/suexec ^^ no, and NO!

Bug#291514: marked as done (apache2-mpm-prefork segfaults since python2.3 upgrade)

Your message dated Sun, 29 Oct 2006 20:31:28 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#291514: apache2-mpm-prefork segfaults since python2.3 upgrade has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#395976: marked as done (apache2.2-common: missing mod_auth_ldap)

Your message dated Sun, 29 Oct 2006 19:58:43 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#395976: apache2.2-common: missing mod_auth_ldap 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 ca

Bug#395936: Apache2 SSL service stopped working since upgrade to 2.2.3-2

* Daan Willems | Apache2 error.log shows: [client ] Invalid method in request | \x16\x03\x01 This sounds like you're missing an SSLEnable for the vhost in question. Can you please check that, and if not, send us the relevant vhost config? -- Tollef Fog Heen

Re: Is it safe to purge apache2-common?

* Mike Bird | In light of recent reports of symlinks being removed[1], and | the statement that apache2.2 takes care of it if apache2 is | *not* purged[2], is it now safe to purge apache2-common? Should be. If not, it's a bug we'd very much like to get reported and fixed. -- Tollef Fog Heen

Bug#395854: marked as done (apache2.2-common: does not run cgi-bin files anymore)

Your message dated Sat, 28 Oct 2006 16:25:58 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#395854: apache2.2-common: does not run cgi-bin files anymore 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

Bug#393913: This line was deleted...

Hi, I've made a diff between apache2.conf and apache2.conf.dpkg-old and it results that the next line was deleted : [EMAIL PROTECTED]:/etc/apache2 $ diff -u apache2.conf.dpkg-old apache2.conf | grep DirectoryIndex -DirectoryIndex index.html index.cgi index.pl index.php index.xhtml Please add

Bug#395853: apache2-common: removes symlinks on upgrade

> > How does it do that? > It does rm -f /var/lib/dpkg/info/apache2-common.postrm in its preinst. Ok. > Oh, but they were created by apache2-common. Sorry, but that's not true. /etc/apache2/conf.d/mediawiki1.7 is created by calling "ln -s" inside mediawiki1.7's postinst. Besides, apache ain't t

Bug#395853: apache2-common: removes symlinks on upgrade

Thomas Schoepf skrev: Then don't purge it before installing apache2.2. apache2.2-common works around this. How does it do that? It does rm -f /var/lib/dpkg/info/apache2-common.postrm in its preinst. As this seems to be an user error rather than an error in the package, there's nothing we c

Processed: Re: Re: Bug#392646: apache2.2-common: doesn't start, child processes segfault

Processing commands for [EMAIL PROTECTED]: > severity #392646 serious Bug#392646: apache2.2-common: doesn't start, child processes segfault Bug#392049: libapr1: Does not work with a 2.4 kernel Bug#392373: apache2-mpm-prefork: does not start on a 2.4 kernel (segmentation fault) because epoll_creat

Bug#395853: "Help, I purged a package and now my configuration is gone."

Peter Samuelson wrote: > > It seems reasonable to purge apache2-common _after_ apache 2.2 is > installed. That will work. But you apparently purged it _before_ > upgrading to apache 2.2. That is not reasonable, and will not work. Unfortunately, "apt-get --purge dist-upgrade" will do just this,

Bug#392646: Re: Bug#392646: apache2.2-common: doesn't start, child processes segfault

severity #392646 serious thanks On Thu, Oct 12, 2006 at 08:33:40PM +0200, Tollef Fog Heen wrote: > John Fry skrev: > >Since I upgraded to apache2 on unstable, apache fails to start after > >trying to spawn a bunch of child processes. Here's a snippet from > >/var/log/apache2/error.log: > > Kno

Bug#392380: apache2-common: Upgrad issues with libapache2-mod-php4 installed

Package: apache2-common Version: 2.0.55-4.1 I have a workaround for upgrading your system in a very easy mode # a2dismod select: php4 # apache2ctl start # apt-get -f install # apt-get -u upgrade # a2insmod select: php4 # apache2ctl stop # apache2ctl start Note: with "apache2ctl restart"