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

Format: 1.7
Date: Sat, 05 Jan 2008 12:27:08 +0100
Source: apache2-mpm-itk
Binary: apache2-mpm-itk
Architecture: source i386
Version: 2.2.6-01-1
Distribution: unstable
Urgency: high
Maintainer: Steinar H. Gunderson <[EMAIL PROTECTED]>
Changed-By: Steinar H. Gunderson <[EMAIL PROTECTED]>
Description: 
 apache2-mpm-itk - multiuser MPM for Apache 2.2
Changes: 
 apache2-mpm-itk (2.2.6-01-1) unstable; urgency=high
 .
   * New upstream release, with patches updated for Apache 2.2.6. Should fix
     FTBFS (but that FTBFS was silently ignored, see next item).
     * Update the apache2-src build dependency to at least 2.2.6-1, as I'm
       unsure of the effects of building with this patch set against older
       versions.
   * Use "set -e" in the patch target so failing hunks are not ignored during
     building.
   * Updated the homepage URL in debian/copyright, and added
     licensing/copyright/tarball information.
Files: 
 10afaa9c60fa29787f194690cac09546 721 net extra apache2-mpm-itk_2.2.6-01-1.dsc
 f8041c58e43dae9814f903919d222c73 33269 net extra 
apache2-mpm-itk_2.2.6-01.orig.tar.gz
 bd02ca089de5cb300e60a40e81a39dbb 12572 net extra 
apache2-mpm-itk_2.2.6-01-1.diff.gz
 5764257de7d490632edc31bc20643f61 173058 net extra 
apache2-mpm-itk_2.2.6-01-1_i386.deb

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

iD8DBQFHf3QRXKRQ3lK3SH4RAqF1AJ9csQ46Fcy/R/JJwejShHNRFiLpxQCdF/BQ
bGhJeL8KjBTu5spQxw6HnLI=
=1/OP
-----END PGP SIGNATURE-----


Accepted:
apache2-mpm-itk_2.2.6-01-1.diff.gz
  to pool/main/a/apache2-mpm-itk/apache2-mpm-itk_2.2.6-01-1.diff.gz
apache2-mpm-itk_2.2.6-01-1.dsc
  to pool/main/a/apache2-mpm-itk/apache2-mpm-itk_2.2.6-01-1.dsc
apache2-mpm-itk_2.2.6-01-1_i386.deb
  to pool/main/a/apache2-mpm-itk/apache2-mpm-itk_2.2.6-01-1_i386.deb
apache2-mpm-itk_2.2.6-01.orig.tar.gz
  to pool/main/a/apache2-mpm-itk/apache2-mpm-itk_2.2.6-01.orig.tar.gz


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

Reply via email to