Bug#422026: marked as done (libapache2-mod-perl2: PerlSetEnv vars not available in PerlPostConfigRequire startup script)

Wed Dec 26 04:51:03 UTC 2007

Your message dated Wed, 26 Dec 2007 01:47:54 -0300
with message-id <b9800b70712252047o6790dde9n47f627c3ae4b3965 at mail.gmail.com>
and subject line Bug#422026: (mod-perl2) PerlSetEnv vars not available in PerlPostConfigRequire startup script
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 reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

-------------- next part --------------
An embedded message was scrubbed...
From: srdjan <srdjan at catalyst.net.nz>
Subject: libapache2-mod-perl2: PerlSetEnv vars not available in PerlPostConfigRequire
 startup script
Date: Thu, 03 May 2007 12:50:55 +1200
Size: 3064
Url: http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20071226/df8460c2/attachment.eml 
-------------- next part --------------
An embedded message was scrubbed...
From: "=?ISO-8859-1?Q?Mart=EDn_Ferrari?=" <martin.ferrari at gmail.com>
Subject: Re: Bug#422026: (mod-perl2) PerlSetEnv vars not available in PerlPostConfigRequire startup script
Date: Wed, 26 Dec 2007 01:47:54 -0300
Size: 2886
Url: http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20071226/df8460c2/attachment-0001.eml 