Bug#229553: debconf note spam

severity 229553 minor tags 229553 + pending merge 229553 229027 stop quit Fabio On Sat, 24 Jan 2004, Matt Zimmerman wrote: Package: apache-common Version: 1.3.29.0.1-3 Severity: normal This package displays a priority 'high' debconf note (apache-common/confignotes) on every installation,

Bug#229505: apache-ssl: post-installation script fails

Hi, are you running testing? is this a fresh installation or an upgrade? Please provide me more information asap. Fabio On Sun, 18 Jan 2004, Michael Kebe wrote: Package: apache-ssl Version: 1.3.29.0.1-3 Severity: normal After apt-get install apache-ssl I get: Setting up

Processed: Re: Bug#229553: debconf note spam

Processing commands for [EMAIL PROTECTED]: severity 229553 minor Bug#229553: debconf note spam Severity set to `minor'. tags 229553 + pending Bug#229553: debconf note spam There were no tags set. Tags added: pending merge 229553 229027 Bug#229027: apache-common: Notes changed config file

Bug#219973: apache dies only if php4 module loaded

Package: apache Version: 1.3.29.0.1-3 Severity: normal Followup-For: Bug #219973 After some testing I figured that apache dies only when php4 module is loaded (php version: 4:4.3.3-4). At first it worked fine but then it just started crashing, don't know why. Yet. -- System Information: Debian

Bug#219973: apache dies only if php4 module loaded

I don't understand why you are following up on this bug. In any case it is a well known php4 problem (see BTS) and please do not mix bugs. Thanks Fabio On Sun, 25 Jan 2004, Marko Mrdjenovic wrote: Package: apache Version: 1.3.29.0.1-3 Severity: normal Followup-For: Bug #219973 After some

Re: apache dies only if php4 module loaded

Further testing revealed that only php4 extension imap.so crashed apache. I did no further testing, since this is a php4-imap | libc-client2002debian | uw-mailutils bug. Regards, Marko Mrdjenovic Marko Mrdjenovic wrote: Package: apache Version: 1.3.29.0.1-3 Severity: normal Followup-For: Bug

Policy regarding apache modules

Hi, I am packaging OpenGroupware.org [1] which comes with an apache module that enables the webserver to handle the HTTP requests for the application server. 1) Is there a policy regarding naming, location in the filesystem etc. for apache modules? 2) The module needs some entries in

Re: Bug#225056: apache: Segmentation fault on startup with virtual hosts

Hi, I have the same problem, but it seg fault only if I have more than 2 virtual host, it's still ok with 2! : ### My apache is crashing (segmentation fault) when I try starting it, it's the first time it's doing that on me, and I tried everything that came into my mind. I have : Server

Bug#229505: apache-ssl: post-installation script fails

Fabio Massimo Di Nitto wrote: Hi, are you running testing? is this a fresh installation or an upgrade? Yes, I am running testing. I think it was a fresh install, because I purge the previous installation... Please provide me more information asap. I found the problem by myself: If you

Re: Policy regarding apache modules

On Sun, 25 Jan 2004, Sebastian Ley wrote: Hi, I am packaging OpenGroupware.org [1] which comes with an apache module that enables the webserver to handle the HTTP requests for the application server. 1) Is there a policy regarding naming, location in the filesystem etc. for apache

Re: Bug#225056: apache: Segmentation fault on startup with virtual hosts

On Sun, 25 Jan 2004, Emanuel Corthay wrote: and only when mod_php4 is loaded... And I don't need to make a request for the server to crash. php4 is buggy. please disable the php4-imap extension and everything should work just fine. Fabio -- Our mission: make IPv6 the default IP protocol We

Bug#229505: marked as done (apache-ssl: post-installation script fails)

Your message dated Sun, 25 Jan 2004 15:18:51 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line Bug#229505: apache-ssl: post-installation script fails 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

Re: Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC

tags 228421 + woody tags 228421 + fixed-upstream thanks Well, maybe a recompilation and binary NMU for apache would suffice? Should the report be reassignd to apache? Willy Tarreau writes: Package: gcc Version: 2:3.0.4-5 Kernel: Linux hp 2.4.24-pa0 #1 Sun Jan 11 18:48:21 CET 2004 parisc

Re: Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC

On Sun, Jan 25, 2004 at 05:36:10PM +0100, Matthias Klose wrote: tags 228421 + woody tags 228421 + fixed-upstream thanks Well, maybe a recompilation and binary NMU for apache would suffice? recompiling apache with -O1 is enough, that's what I did here and it works. Should the report be

Extract WhoIs data!

Hello: We are able to extract WhoIs data for any selection of domain names! We can either extract: 1) only email addresses and domain expiry dates ($1/1,000 domains) or 2) complete info provided at registration which includes the following fields ($2/1,000 domains): owner/registrar,

Re: Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC

On Sun, Jan 25, 2004 at 06:05:17PM +0100, Willy Tarreau wrote: But the root of the problem lies in gcc 3.0.4 since it is OK in 3.3.2. So wouldn't it be easier to identify and backport the fix from 3.3.2 to 3.0.4 and inform all projects that they must recompile everything on parisc ? recompile

$BL$>5Bz9-9p"((B5000$B1_$G3+6H(B$B$7$^$;$s$+!*!*(B

$B!!(B $B!!(B $BL$>5Bz9-9p"((B $B$4LBOG$JJ}$O:o=|$7$F$/[EMAIL PROTECTED](B $B!!Ev9-9p$r

Re: Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC

On Sun, Jan 25, 2004 at 11:03:53AM -0700, Grant Grundler wrote: On Sun, Jan 25, 2004 at 06:05:17PM +0100, Willy Tarreau wrote: But the root of the problem lies in gcc 3.0.4 since it is OK in 3.3.2. So wouldn't it be easier to identify and backport the fix from 3.3.2 to 3.0.4 and inform all

Bug#229653: apache: /etc/init.d/apache still leaking environment

Package: apache Version: 1.3.26-0woody3 Severity: important Tags: security patch -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux hostname 2.4.18 #5 Mon May 5 13:56:33 CEST 2003 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages apache depends on: ii apache-common

Bug#229653: apache: /etc/init.d/apache still leaking environment

Sorry, this patch is useless to me. Please resend as a unified or context diff (diff -u). On Sun, Jan 25, 2004 at 03:48:57PM +0100, [EMAIL PROTECTED] wrote: Patch: 22a23 ENV=env -i LANG=${LANG} PATH=${PATH} 32c33 start-stop-daemon --start --pidfile $PIDFILE --exec $DAEMON ---

Bug#130883: 70% sav1ngs on v1agra

Generic viagra, at cheap prices. Most places charge $20, we charge $3. Quite a difference, huh? An amazing erection WITHIN SEVERAL SECONDS is guaranteed to you! Go into sexual overdrive today... vrm! Shipped worldwide. Your easy to use solution is here:

Processed: Re: Bug#229653: apache: /etc/init.d/apache still leaking environment

Processing commands for [EMAIL PROTECTED]: tags 229653 - security Bug#229653: apache: /etc/init.d/apache still leaking environment Tags were: patch security Tags removed: security thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#229677: apache2-common: segfault-o-rama with ldap auth

Package: apache2-common Version: 2.0.47-1 Severity: critical As soon as I enable LDAP authentication on a vhost apache2 will segfault on pretty much all hits. The LDAP config is trivial: Location / AuthNameAttingo Staff Portal AuthTypeBasic

.

. . ? (O95)-1O9-5325

Bug#130883: marked as done (libapache-mod-perl: mod_perl confused about method vs. direct calls when using internal_redirect)

Your message dated Sun, 25 Jan 2004 18:46:27 -0800 with message-id [EMAIL PROTECTED] and subject line No bug here (error in test case) 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

Bug#229677: apache2-common: segfault-o-rama with ldap auth

Hi Wichert, can you test using apache2 2.0.48 and see if it still happens? Thanks Fabio On Mon, 26 Jan 2004, Wichert Akkerman wrote: Package: apache2-common Version: 2.0.47-1 ^^ ii libapr0 2.0.48-4 The Apache Portable Runtime