Your message dated Fri, 28 Jun 2013 11:48:23 +0000
with message-id <e1usxa7-0008ir...@franck.debian.org>
and subject line Bug#666796: fixed in libapache2-mod-python 3.3.1-11
has caused the Debian Bug report #666796,
regarding libapache2-mod-python: sourceful transition towards Apache 2.4
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
666796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-python
Severity: important
User: debian-apa...@lists.debian.org
Usertags: apache24transition

Dear maintainer,

your package libapache2-mod-python is provding an Apache2 web server module.
We're upgrading Apache to the new upstream version 2.4 [1] (tracked
as transition bug #661958). This requires all modules to be rebuilt
due to ABI changes.  Thus, you need to rebuild and reupload your
Apache2 module package in a version compatible to our new package
available in experimental [2].  Please note it is not enough to
simply rebuild the module - it needs some adaptions in the module
package metadata. We have written packaging guidelines for our
reverse dependencies [3]. Please read it carefully, it should be able
to answer most of your questions. Do also look at dh_apache2
(available through the dh-apache2 package) which can simplify
packaging Apache2 modules.  In short, we want to highlight these
changes you need to be aware of.

* APIs changed for some cases [3]. Chances are your module needs some
  adaptions, please get in touch with upstream or us if you need help
  to port your module to Apache 2.4.

* MPM packages are gone. You cannot depend or conflict with a
  particular MPM anymore. If your module does not work with a
  particular module, make sure to make it abort with an error if
  loaded together with an incompatible MPM. You can use our
  apache2-maintscript-helper [4] to switch to the MPM of your choice
  in your maintainer scripts. 

* Do not build-depend on apache2-threaded-dev or apache2-prefork-dev
  anymore. Just like MPMs are gone, are our MPM -dev packages as
  well. All modules need to simply build-depend on apache2-dev. 

* Do NOT depend on apache2, apache2-common or any other real apache2
  package in your binary module package. Depend on our virtual
  apache2-api-20120211 package only!

* Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our
  apache2-maintscript-helper [3] instead. This is required to get a
  uniform and stateful handling of all Apache2 modules.


You can look at our Apache 2.4 packaging hints [5] for hands-on
tutorials.  Please note: This bug is filed as "important" for now. As
the time goes by we plan make it a release critical severity. In the
consequences your module either needs an update or is going to be
removed from Wheezy. For the time being please tag the bug as pending
as soon as you have a package ready. We strongly recommend that at
least maintainers of complex module packages make an upload to
experimental as well. Of course, uploading simple modules to
experimental is welcome, too.

[1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html
[2] 
http://packages.debian.org/search?keywords=apache2&searchon=sourcenames&exact=1&suite=all&section=all
[3] 
http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next
[4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html
[5] http://wiki.debian.org/Apache/PackagingFor24





--- End Message ---
--- Begin Message ---
Source: libapache2-mod-python
Source-Version: 3.3.1-11

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

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 666...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arthur de Jong <adej...@debian.org> (supplier of updated libapache2-mod-python 
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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 28 Jun 2013 13:13:39 +0200
Source: libapache2-mod-python
Binary: libapache2-mod-python libapache2-mod-python-doc
Architecture: source i386 all
Version: 3.3.1-11
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 
<python-modules-t...@lists.alioth.debian.org>
Changed-By: Arthur de Jong <adej...@debian.org>
Description: 
 libapache2-mod-python - Python-embedding module for Apache 2
 libapache2-mod-python-doc - Python-embedding module for Apache 2 - 
documentation
Closes: 616858 666796 710640
Changes: 
 libapache2-mod-python (3.3.1-11) unstable; urgency=low
 .
   * Team upload.
   * Upload to unstable.
 .
 libapache2-mod-python (3.3.1-10) experimental; urgency=low
 .
   * Team upload.
 .
   [ Arthur de Jong ]
   * Switch to dh_python2 based on the patch in Ubuntu. (Closes: #616858,
     LP: #788514)
   * FTBFS: switch configure.in to pkg-config to configure Python. This fixes
     discovery with multiarch Python. Taken from the Ubuntu packaging
     (LP: #1098597) (closes: #710640).
   * Remove version from apache2-threaded-dev build dependency because every
     version since etch is new enough.
   * Dropped provides/replaces/conflicts for ancient versions of mod_python.
   * Switch from dpatch to source format 3.0 (quilt).
   * Dropped obsolete patch 03_includes.patch: long since been fixed in
     mod_python.
   * Switch to dh-style debian/rules.
   * Switch to debhelper compatibility level 9.
   * Update 02_makefile.patch to add --install-layout=deb to the setup.py
     call.
   * Remove generated file to support building twice in a row.
   * Simple spelling fix in Python docstring (thanks lintian).
   * Remove code for renaming mod_python.load to python.load because we are
     not supporting upgrades from etch.
   * Update watch file provided by Bart Martens.
   * Update to Standards-Version 3.9.4.
   * Build with Apache 2.4 (closes: #666796):
     - use dh_apache2 (remove postinst and prerm)
     - 20_apache24.patch: fixes for Apache 2.4.
 .
   [ Jakub Wilk ]
   * Use canonical URIs for Vcs-* fields.
Checksums-Sha1: 
 c87ec293bff85ed65e9c3f3564e40cc40e0b6707 1606 
libapache2-mod-python_3.3.1-11.dsc
 ef82981e616347bdfffd7288314150f8c29b2e1d 12404 
libapache2-mod-python_3.3.1-11.debian.tar.gz
 a4d3ef056ee585a88a390d9da5637b24b7d694d7 131958 
libapache2-mod-python_3.3.1-11_i386.deb
 d7dcfa159c93f267d9a3bd3a7600b29b98859a8d 162008 
libapache2-mod-python-doc_3.3.1-11_all.deb
Checksums-Sha256: 
 c3c0437eb571c8630e6cd52f970284fe74d498cdf2d506cbcacde9dc05633fba 1606 
libapache2-mod-python_3.3.1-11.dsc
 9d638b970803313a56c2295514739e646e0c7dca4485d1b668ce3f1de0b7a348 12404 
libapache2-mod-python_3.3.1-11.debian.tar.gz
 2d13eb674081f4c56206b9eaf2f09689957ca596b2106c827ffdb2f8f9d0e08e 131958 
libapache2-mod-python_3.3.1-11_i386.deb
 c53874c9fafd008ad6c5395e6637fff1bc6f3cde294dadad2ba1acf53619411d 162008 
libapache2-mod-python-doc_3.3.1-11_all.deb
Files: 
 48c824a9f86232a59f2702e02742c694 1606 httpd optional 
libapache2-mod-python_3.3.1-11.dsc
 9bac06be0c15fa97d6700b08c4d3039b 12404 httpd optional 
libapache2-mod-python_3.3.1-11.debian.tar.gz
 ac1c6bb1b80d7a1ae2f525e2330e5f03 131958 httpd optional 
libapache2-mod-python_3.3.1-11_i386.deb
 89056c955efaab795a251637fed9d782 162008 doc optional 
libapache2-mod-python-doc_3.3.1-11_all.deb

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

iEYEARECAAYFAlHNc/YACgkQVYan35+NCKfnYQCfWUkw6SKtETDIwUxFJRbm8ToU
UV0AoLAzQg8q3ajs7h+h5wj42Q6GuGkG
=u0Pe
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to