Your message dated Thu, 17 Jan 2013 22:02:31 +0000
with message-id <[email protected]>
and subject line Bug#669765: fixed in backuppc 3.2.1-5
has caused the Debian Bug report #669765,
regarding backuppc: 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 [email protected]
immediately.)


-- 
669765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669765
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: backuppc
Severity: important
User: [email protected]
Usertags: apache24webapptransition

Dear maintainer,

your package backuppc is a web application which supports the Apache2
web server. We're upgrading Apache to the new upstream version 2.4 [1]
(tracked as transition bug #661958). This requires some changes in your
package about how to interface to our package. You can test your package
against our package available in experimental [2] which is soon to be
uploaded to Sid. Please note, chances are that for the time being, third
party modules (e.g. mod_php, mod_perl and such) are not yet available in
a version capable to run with the Apache 2.4 web server. You can use
their (Fast-)CGI counter parts, e.g. php5-fpm to test your packages. You
can see an up to date state of modules being in the transition to
Apache2 2.4 at [3]. We have written packaging guidelines for our reverse
dependencies [4]. Please read this document 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 shipping of Apache2
configuration files. 

In short, we want to highlight these changes you need to be aware of:

* Do NOT declare a strong relation against apache2.2-common (or
 apache2-common as its natural successor). Instead recommend "apache2 |
 httpd" in your package relationships. 

* Do NOT install any files to /etc/apache2/conf.d/. This directory is
 obsolete. Its successor is /etc/apache2/conf-available/ which can be
 interfaced through a2enconf/a2disconf

* Do NOT call a2enconf/a2disconf in your maintainer scripts. Use our
 apache2-maintscript-helper [4] instead. This is required to get a
 uniform and stateful handling of all web applications interfacing with
 Apache2.

* Please use the new authentication and authorization directives of
 Apache 2.4 [6]. While the old style directives are in principle still
 supported using mod_access_compat, mixing old and new style directives
 can cause problems. Moreover, the compatibility mode may be removed in
 a future release.


You can look at our Apache 2.4 packaging hints [7] for hands-on
tutorials.



[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://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=apache24transition;[email protected]
[4] 
http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next
[5] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html
[6] http://httpd.apache.org/docs/2.4/upgrading.html#run-time
[7] http://wiki.debian.org/Apache/PackagingFor24





--- End Message ---
--- Begin Message ---
Source: backuppc
Source-Version: 3.2.1-5

We believe that the bug you reported is fixed in the latest version of
backuppc, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ludovic Drolez <[email protected]> (supplier of updated backuppc 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.8
Date: Thu, 03 Jan 2013 17:27:35 +0100
Source: backuppc
Binary: backuppc
Architecture: source i386
Version: 3.2.1-5
Distribution: unstable
Urgency: low
Maintainer: Ludovic Drolez <[email protected]>
Changed-By: Ludovic Drolez <[email protected]>
Description: 
 backuppc   - high-performance, enterprise-grade system for backing up PCs
Closes: 525395 639102 663975 669765 672372
Changes: 
 backuppc (3.2.1-5) unstable; urgency=low
 .
   * Added libtime-modules-perl dependency. Closes: #525395
   * Remove /var/lib/backuppc/pc/localhost if it's empty
     Closes: #672372
   * Added stuff to support Apache 2.4. Closes: #669765
   * Added NICE support in /etc/default/backuppc. Closes: #639102
   * Changed the default display date format. Closes: #663975
Checksums-Sha1: 
 7921f74a270568180f745b630ac309210cfd0fea 1029 backuppc_3.2.1-5.dsc
 f079865479a632fc80eff54b5371505424d4ec72 29562 backuppc_3.2.1-5.diff.gz
 d7a6b074d15d23ee8c0ed61ef9ee0550389945b8 605032 backuppc_3.2.1-5_i386.deb
Checksums-Sha256: 
 f1b2121ee79d8d6c38af7d5648aa2467f1399ffb9536e07b2f48c8222d1b83da 1029 
backuppc_3.2.1-5.dsc
 a1ef6ce9cab725503b6ce6bde2bd1a3ea3482cfabee1d34a7a0f3e873eb44ee6 29562 
backuppc_3.2.1-5.diff.gz
 c82a704353d842f7fcaa50a94ed356fb75e076ec1ac6ff63b5b3e9040cdd1e8f 605032 
backuppc_3.2.1-5_i386.deb
Files: 
 fcb2aff1f3b4313ffbcc0b3a9c26826a 1029 utils optional backuppc_3.2.1-5.dsc
 071dc1d57dc12cc86211faa6ea18eb93 29562 utils optional backuppc_3.2.1-5.diff.gz
 2f9b0ba18d427ec139b1da524c271f07 605032 utils optional 
backuppc_3.2.1-5_i386.deb

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

iEYEARECAAYFAlD4cc0ACgkQsRlQAP1GppjdKwCeI6XfrXBTXDXDn8puz5MOpkpw
DlIAnRKVgmhcH5bJetED7TDPAM+AnCFl
=6kdA
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to