Your message dated Tue, 21 May 2019 16:33:39 +0000
with message-id <[email protected]>
and subject line Bug#754092: fixed in libapache2-mod-defensible 1.4-3.2
has caused the Debian Bug report #754092,
regarding libapache2-mod-defensible: use dh-autoreconf to fix FTBFS on ppc64el
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.)


-- 
754092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754092
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libapache2-mod-defensible
Version: 1.4-3.1
Severity: normal
Tags: patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

* Use dh-autoreconf to fix FTBFS on ppc64el by getting new libtool macros.
 * Use automake's "foreign" option to fix FTBFS while autoreconfing.

Thanks for considering the patch.

Erwan Prioul.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

diff -Naur a/debian/control b/debian/control
--- a/debian/control	2014-07-07 15:24:59.727689299 +0200
+++ b/debian/control	2014-07-07 15:25:46.255686827 +0200
@@ -3,7 +3,7 @@
 Section: web
 Priority: extra
 Standards-Version: 3.8.0
-Build-Depends: debhelper (>= 5.0.0), dh-apache2, apache2-dev (>= 2.2.3-2)
+Build-Depends: debhelper (>= 5.0.0), dh-apache2, apache2-dev (>= 2.2.3-2), dh-autoreconf
 
 Package: libapache2-mod-defensible
 Architecture: any
diff -Naur a/debian/patches/automake-foreign.patch b/debian/patches/automake-foreign.patch
--- a/debian/patches/automake-foreign.patch	1970-01-01 01:00:00.000000000 +0100
+++ b/debian/patches/automake-foreign.patch	2014-07-07 15:39:50.515641955 +0200
@@ -0,0 +1,13 @@
+--- a/configure.in
++++ b/configure.in
+@@ -1,8 +1,8 @@
+ # configure.in for mod_defensible
+ # © 2007 Julien Danjou <[email protected]>
+ 
+-AC_INIT(mod_defensible)
+-AM_INIT_AUTOMAKE(mod_defensible, 1.2)
++AC_INIT([mod_defensible], [1.2])
++AM_INIT_AUTOMAKE([foreign])
+ 
+ AC_CONFIG_SRCDIR(mod_defensible.c) 
+ 
diff -Naur a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series	2014-07-07 15:24:59.739689299 +0200
+++ b/debian/patches/series	2014-07-07 15:39:50.515641955 +0200
@@ -2,3 +2,4 @@
 aplog-use-module.patch
 server-banner.patch
 conn-rec-remote-ip.patch
+automake-foreign.patch
diff -Naur a/debian/rules b/debian/rules
--- a/debian/rules	2014-07-07 15:24:59.735689299 +0200
+++ b/debian/rules	2014-07-07 15:26:34.291684273 +0200
@@ -5,6 +5,7 @@
 
 config.status:
 	dh_testdir
+	dh_autoreconf
 	./configure
 
 build: build-stamp
@@ -20,6 +21,7 @@
 	dh_testroot
 	rm -f build-stamp config.log
 	[ ! -f Makefile ] || $(MAKE) distclean
+	dh_autoreconf_clean
 	dh_clean 
 
 install: build


--- End Message ---
--- Begin Message ---
Source: libapache2-mod-defensible
Source-Version: 1.4-3.2

We believe that the bug you reported is fixed in the latest version of
libapache2-mod-defensible, 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.
Frédéric Bonnard <[email protected]> (supplier of updated 
libapache2-mod-defensible 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: SHA512

Format: 1.8
Date: Tue, 21 May 2019 17:44:15 +0200
Source: libapache2-mod-defensible
Architecture: source
Version: 1.4-3.2
Distribution: unstable
Urgency: medium
Maintainer: Julien Danjou <[email protected]>
Changed-By: Frédéric Bonnard <[email protected]>
Closes: 754092
Changes:
 libapache2-mod-defensible (1.4-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Applied Ubuntu patches from 1.4-3.1ubuntu2 to fix ppc64el :
     - Use dh-autoreconf instead of autotools-dev to also fix
       FTBFS on ppc64el by getting new libtool macros (still updates
       config.{sub,guess}).
     - Use automake's "foreign" option to fix FTBFS while autoreconfing.
     - Use dh_autotools-dev to update config.{sub,guess} for new ports.
     Thanks Logan Rose and Adam Conrad (Closes: #754092)
Checksums-Sha1:
 62935c51c422c154dbbf523da2846d02482c7a30 1884 
libapache2-mod-defensible_1.4-3.2.dsc
 796a591cdbc9e29a38515b3f445e2072e586c204 3720 
libapache2-mod-defensible_1.4-3.2.debian.tar.xz
 76096e3d4bdab1a8035ef2112e0126bdff966980 6287 
libapache2-mod-defensible_1.4-3.2_ppc64el.buildinfo
Checksums-Sha256:
 3bbfd034afa0d1b872abe16aecea76a1756a8e814e41e4a57ea0006fc13e7e40 1884 
libapache2-mod-defensible_1.4-3.2.dsc
 da9348c0066a18c3a496d80c038ebbda4e07c48ef199030702f3a141a57377b9 3720 
libapache2-mod-defensible_1.4-3.2.debian.tar.xz
 4fa6713ba8563b70218c09c5ef57258a7efc0896eb9c26e3d97de7f93be420f8 6287 
libapache2-mod-defensible_1.4-3.2_ppc64el.buildinfo
Files:
 a4e08a6343a3d21235322bc3ae543052 1884 web extra 
libapache2-mod-defensible_1.4-3.2.dsc
 5ff284128b2d7c706e9886da82dd6373 3720 web extra 
libapache2-mod-defensible_1.4-3.2.debian.tar.xz
 f17777bd7f3769b7f637df3e5ef956c0 6287 web extra 
libapache2-mod-defensible_1.4-3.2_ppc64el.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEh9vVdWFVIC7DiF6Ta3SY/LmzWKwFAlzkIYgSHGZyZWRpekBk
ZWJpYW4ub3JnAAoJEGt0mPy5s1is2vsQAKfNvm7EL9uG9OyxMmNDPWDDlJl+TfOB
t/PpTUpwJwldoHgOE/KZwGqaVK2bPaHch0OcOtUwJVNe6mcH4Ou6aOxIeQXtKpVv
SsTK/YdPCV0W7ii0A1Er2vBhFIMoCwUx3ktQHRr55RhTljkqNFDgqhxz70zjWcEG
CXWOxHMJ28ymjnp2cgIvwZZ3+Kg/Brr/8Z6HaK2aCh5kSGgQUz//jhC7QRc//dld
7QUUEad5+2Lfw8qp788m59pRpZYy1m3UzJHhPewHQtV9qBOCGgnVzRN6a0ihD0kk
QAq3ZQorO5T7k7tH1cbSDbK8x8wcigLwybig9fCIZiIlmd+LYF79m00k5LQWRsct
Mc/HBIfU2NM7FFWod1YqyKGIc6LJk8m/ya+i6nN1Kva6XoaX7XBFFulQiiS4zacV
hGReeY4QpOLG4ER797GPC0BEndlj5jVHHtCWTTnS/JCDCq057fYxQK0/GI1e9+/u
a0ThEPkYSOOiWgci0hlftNj8PcV0HUM+3bL4K7lOX2mL2PYV6DxAstnQt1NZ/iS+
vz2NFVWDVBdqEFOxkcujvW1IJ9sAuGNxNVyUY1g+DqCEqt8L7sF2M/oRYfT01kuH
VHWfoI8GeYj8C6ohuABsqaUyrM2V8j/YnA7Kr/U/C3TwnH7+zCg2UEqRNlCJKcQe
VsmJSMFf2jih
=2ES5
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to