Your message dated Fri, 08 Apr 2005 03:17:07 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#267353: fixed in libapache-mod-security 1.8.4-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 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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Aug 2004 02:53:27 +0000
>From [EMAIL PROTECTED] Sat Aug 21 19:53:27 2004
Return-path: <[EMAIL PROTECTED]>
Received: from s010600e029962405.cg.shawcable.net (lucifer.0c3.net) 
[68.147.116.8] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1ByiU2-0005T2-00; Sat, 21 Aug 2004 19:53:27 -0700
Received: from adconrad by lucifer.0c3.net with local (Exim 3.36 #1 (Debian))
        id 1ByiU1-0007vF-00
        for <[EMAIL PROTECTED]>; Sat, 21 Aug 2004 20:53:25 -0600
To: [EMAIL PROTECTED]
Subject: libapache-mod-security needs to be rebuilt to revert the apache2 ABI 
transition
Message-Id: <[EMAIL PROTECTED]>
From: Adam Conrad <[EMAIL PROTECTED]>
Date: Sat, 21 Aug 2004 20:53:25 -0600
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: libapache-mod-security
Severity: serious

Well, here we are, back where we started a week ago.  The apache2 LFS
transition has (sadly) been reverted, due to us spotting a few more bugs
than we were willing to deal with in the 8 day time limit we were given.

So, what this means is that your package needs to be updated.  Again.  We
need it built against apache2/libapr-dev (>= 2.0.50-10), which means
bumping your build-deps appropriately.  Urgency should be "high", or this
is never going to work right.  An example changelog entry follows:

libapache2-mod-spiffy (1.5.0-4) unstable; urgency=high

  * Back out the ill-fated apache2 LFS transition.
  * Remove the LFS CFLAGS that I added for the transition.  Man, I
    wish my apache module just used CFLAGS from apxs2 like all the
    OTHER ones do, so I could skip this step.
  * Bump the apache2-{threaded,prefork}-dev build-dep to (>= 2.0.50-10)

 -- Adam Conrad <[EMAIL PROTECTED]>  Thu, 19 Aug 2004 03:46:11 -0600

I apologize yet again for this.  We tried, we failed, we learned.  We'll
be doing this against post-Sarge, but in a much more organised fashion, I
assure you, and only after we've staged things in experimental for a while
and ironed out some of the more obscure bugs (like subversion's WC-munging)

... Adam Conrad

PS: If you want me to NMU your package to back out this transition, please
    let me know.  I'm only sending bugs to the maintainers who actively
    updated last time, with the others I just reverted my previous NMUs.
    
    In the interest of getting this all synched and fixed before Sarge, I
    will be NMUing without permission after today's dinstall.  So, you have
    around 24 hours to upload your own version first. :)

---------------------------------------
Received: (at 267353-close) by bugs.debian.org; 8 Apr 2005 07:32:19 +0000
>From [EMAIL PROTECTED] Fri Apr 08 00:32:19 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DJnyU-0002ee-00; Fri, 08 Apr 2005 00:32:19 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DJnjn-0001Wu-00; Fri, 08 Apr 2005 03:17:07 -0400
From: Alberto Gonzalez Iniesta <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#267353: fixed in libapache-mod-security 1.8.4-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 08 Apr 2005 03:17:07 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 2

Source: libapache-mod-security
Source-Version: 1.8.4-2

We believe that the bug you reported is fixed in the latest version of
libapache-mod-security, which is due to be installed in the Debian FTP archive:

libapache-mod-security_1.8.4-2.diff.gz
  to 
pool/main/liba/libapache-mod-security/libapache-mod-security_1.8.4-2.diff.gz
libapache-mod-security_1.8.4-2.dsc
  to pool/main/liba/libapache-mod-security/libapache-mod-security_1.8.4-2.dsc
libapache-mod-security_1.8.4-2_i386.deb
  to 
pool/main/liba/libapache-mod-security/libapache-mod-security_1.8.4-2_i386.deb
libapache2-mod-security_1.8.4-2_i386.deb
  to 
pool/main/liba/libapache-mod-security/libapache2-mod-security_1.8.4-2_i386.deb
mod-security-common_1.8.4-2_all.deb
  to pool/main/liba/libapache-mod-security/mod-security-common_1.8.4-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alberto Gonzalez Iniesta <[EMAIL PROTECTED]> (supplier of updated 
libapache-mod-security package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri,  8 Apr 2005 08:48:11 +0200
Source: libapache-mod-security
Binary: libapache-mod-security libapache2-mod-security mod-security-common
Architecture: source i386 all
Version: 1.8.4-2
Distribution: unstable
Urgency: medium
Maintainer: Alberto Gonzalez Iniesta <[EMAIL PROTECTED]>
Changed-By: Alberto Gonzalez Iniesta <[EMAIL PROTECTED]>
Description: 
 libapache-mod-security - Tighten the Web application security for Apache 1.x
 libapache2-mod-security - Tighten the Web application security for Apache 2.x
 mod-security-common - Tighten the Web application security - common files
Closes: 267353 297983 303613
Changes: 
 libapache-mod-security (1.8.4-2) unstable; urgency=medium
 .
   * New maintainer (Closes: #303613)
   * Thanks Adam Conrad for helping with the apache2
     LFS transition. (Closes: #267353)
   * Patched apache2/mod_security.c to include regex.h and build
     correctly. (Closes: #297983). Thanks Andreas Jochens.
     This was RC, thus the urgency.
Files: 
 dd64bbdea8b5ec344f5ed324432b2440 737 web optional 
libapache-mod-security_1.8.4-2.dsc
 0cd6c87e96bc4984ad585d6c75918b08 7100 web optional 
libapache-mod-security_1.8.4-2.diff.gz
 6d4586b2f7c459fa2fb8cc1869317474 278316 web optional 
mod-security-common_1.8.4-2_all.deb
 e4e6872c111fe4e1f6a135c44f00766e 26902 web optional 
libapache-mod-security_1.8.4-2_i386.deb
 24141387c68a242215a846dce3c74e87 32880 web optional 
libapache2-mod-security_1.8.4-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCVi29xRSvjkukAcMRApmRAKCXFSUromTBz7mnd+aqBDZAuap3jwCgifAL
BPGxrzE73mRXDcdmIZlu8Nc=
=s/P1
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to