Sync libapr-memcache 0.7.0-3 (universe) from Debian unstable (main)

Bug #1282283 reported by Bas van den Dikkenberg
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libapr-memcache (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Please sync libapr-memcache 0.7.0-2 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Use dh_autotools-dev to update config.{sub,guess} for new ports.
  * Use dh_autotools-dev to update config.{sub,guess} for new ports.

Dh tools is used in the new versions

Changelog entries since current saucy version 0.7.0-1ubuntu1:

libapr-memcache (0.7.0-2) unstable; urgency=low

  * Watch file was not working, checking wrong source file
  * Updated copyright file
    - Changed FSF address to URL
    - Updated copyright dates
  * debian/control:
    - Changed Standards-Version to 3.9.5
    - Added debian VCS URLs in control file
    - Changed dependency of deb-helper to <= 9
  * debian/compat: Changed Deb-helper compatibility level to 9
  * debian/rules:
    - Minimized rules file
    - Removed unneeded cp actions
    - Added hardening by adding CPP/LD/C FLAGS to dh_auto_configure
  * debian/*.install
    - Removed libapr-memcache.install because it was not needed
    - Changed /usr/lib/ to usr/lib/*/
    - Removed libapr_memcache.la from libapr-memcache-dev.install
      (Closes: #735083)
  * Removed libapr_memcache.la from libapr-memcache-dev package
  * Fix "Lintian reports hardening-no-relro" harding is done by new
    version of deb-helper. So is fix on next rebuild automatically
    (Closes: #735127)
  * debian/*.install, rules and control
    - Adjusted control and install file for multi-arch support

 -- Bastiaan Franciscus van den Dikkenberg <email address hidden> Sat, 11 Jan 2014 17:29:41 +0100

Revision history for this message
Daniel Holbach (dholbach) wrote :

Can you explain where dh_autotools-dev is run so we can make sure this builds on arm64 and ppc64el?

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Bastiaan: you need to replace "dh $@" with "dh $@ --with autotools-dev", adding the build-dependency is not sufficient enough.

Changed in libapr-memcache (Ubuntu):
status: New → Incomplete
Revision history for this message
Bas van den Dikkenberg (bas-dikkenberg) wrote :

Uploaded it to debian mentors,

Filed the RFS at debian now just waiting for sponsor to upload the packages.

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Thanks. I am unsubscribing ubuntu-sponsors for now, please subscribe back once the new upload is accepted.

Revision history for this message
Bas van den Dikkenberg (bas-dikkenberg) wrote :
Download full text (3.3 KiB)

libapr-memcache now debian is version 0.7.0-3 i use autoreconf in the build proces instead of autotool-dev this does the same you need right :-)

so please sync in to ubuntu

Accepted libapr-memcache 0.7.0-3 (source amd64)

To: <email address hidden>
Subject: Accepted libapr-memcache 0.7.0-3 (source amd64)
From: Bastiaan Franciscus van den Dikkenberg <email address hidden>
Date: Sat, 01 Mar 2014 22:49:10 +0000
Mail-followup-to: <email address hidden>
Message-id: <email address hidden>
Reply-to: <email address hidden>
Sender: Archive Administrator <email address hidden>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 23 Feb 2014 10:51:11 +0100
Source: libapr-memcache
Binary: libapr-memcache0 libapr-memcache-dev
Architecture: source amd64
Version: 0.7.0-3
Distribution: unstable
Urgency: low
Maintainer: Bastiaan Franciscus van den Dikkenberg <email address hidden>
Changed-By: Bastiaan Franciscus van den Dikkenberg <email address hidden>
Description:
 libapr-memcache-dev - memcache client - development libraries
 libapr-memcache0 - memcache client - shared library
Closes: 722789
Changes:
 libapr-memcache (0.7.0-3) unstable; urgency=low
 .
   * debian/rules removed unneeded export command from rules file
   * debian/rules now using autoreconf (Closes: #722789)
   * debian/control added build dependency for dh-autoreconf
   * debian/control removed build dependency for autotools-dev
   * debian/patches/configurepatch added patch to make autoreconf work
     - Added AC_CONFIG_MACRO_DIR to include m4 files of libapr-memcache
     - Added missing LT_INIT
     - Remove obsolete extra options form AM_INIT_AUTOMAKE
Checksums-Sha1:
 896da51bd8405eca8c84401a931a652da06fb0f0 1732 libapr-memcache_0.7.0-3.dsc
 d6e45417ab3a90c752189c5c71bde17418d0eff1 3716 libapr-memcache_0.7.0-3.debian.tar.xz
 4f4ed8b60e8bb7cf6567a50dade1c04b5778538a 10892 libapr-memcache0_0.7.0-3_amd64.deb
 6a6cdf3ff36cc12b9bca088206e85343f19e7aa8 11798 libapr-memcache-dev_0.7.0-3_amd64.deb
Checksums-Sha256:
 924af19e7aeb867bb2485b23d1f61b021cffd183c7291e9a0cddb33f6ef76e6d 1732 libapr-memcache_0.7.0-3.dsc
 671a80e3195f4a1e6a325f81edc30e9b3e21285b1878ab9f772fd30e5815a9d1 3716 libapr-memcache_0.7.0-3.debian.tar.xz
 9988c30a5e0243c1d19b18f8d82e69e30ac3e2b239bde02e33c2d04374a18a90 10892 libapr-memcache0_0.7.0-3_amd64.deb
 70c88afb824d194e4365dbfb13ffe19db30dbcd177d98fec84e8baf5c845fa91 11798 libapr-memcache-dev_0.7.0-3_amd64.deb
Files:
 bcf9c7053cb3b07a2c6ae40cd951efee 1732 libs extra libapr-memcache_0.7.0-3.dsc
 a764c67bb14f839298e355e3005c250b 3716 libs extra libapr-memcache_0.7.0-3.debian.tar.xz
 cebc79ea9dcf7ed96a07fef203eaf897 10892 libs extra libapr-memcache0_0.7.0-3_amd64.deb
 84db4663c4ee5f312c91581caf027ff6 11798 libdevel extra libapr-memcache-dev_0.7.0-3_amd64.deb

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

iQEcBAEBAgAGBQJTEl/kAAoJEFb2GnlAHawEh4EH/1MgMqzDlaOjzo3C88GbaBEo
tusQbynBfwl2/b1X9/+ajpCCw/jZQn+t1aD8Ts++aMN2yHBL4vSUTgvyxtteYvgz
X9G2+Orf/utmwGOmYq+uzi+pmICUTZfEuHnaoCukMNsKmeLDsevk6iiMwT9n5YbQ
V52h03BkyitjGE32XUH6C/sU6ucsyzm0pD6kuoF2F8n+6O6zKsDYxN4s9aXgm2xO
b5mZrRYJa8Xmwf2mcKpED8RIB64xJcG/Jt...

Read more...

summary: - Sync libapr-memcache 0.7.0-2 (universe) from Debian unstable (main)
+ Sync libapr-memcache 0.7.0-3 (universe) from Debian unstable (main)
Changed in libapr-memcache (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Dmitry Shachnev (mitya57) wrote :

This bug was fixed in the package libapr-memcache - 0.7.0-3
Sponsored for Bas van den Dikkenberg (bas-dikkenberg)

---------------
libapr-memcache (0.7.0-3) unstable; urgency=low

  * debian/rules removed unneeded export command from rules file
  * debian/rules now using autoreconf (Closes: #722789)
  * debian/control added build dependency for dh-autoreconf
  * debian/control removed build dependency for autotools-dev
  * debian/patches/configurepatch added patch to make autoreconf work
    - Added AC_CONFIG_MACRO_DIR to include m4 files of libapr-memcache
    - Added missing LT_INIT
    - Remove obsolete extra options form AM_INIT_AUTOMAKE

 -- Bastiaan Franciscus van den Dikkenberg <email address hidden> Sun, 23 Feb 2014 10:51:11 +0100

libapr-memcache (0.7.0-2) unstable; urgency=low

  * Watch file was not working, checking wrong source file
  * Updated copyright file
    - Changed FSF address to URL
    - Updated copyright dates
  * debian/control:
    - Changed Standards-Version to 3.9.5
    - Added debian VCS URLs in control file
    - Changed dependency of deb-helper to <= 9
  * debian/compat: Changed Deb-helper compatibility level to 9
  * debian/rules:
    - Minimized rules file
    - Removed unneeded cp actions
    - Added hardening by adding CPP/LD/C FLAGS to dh_auto_configure
  * debian/*.install
    - Removed libapr-memcache.install because it was not needed
    - Changed /usr/lib/ to usr/lib/*/
    - Removed libapr_memcache.la from libapr-memcache-dev.install
      (Closes: #735083)
  * Removed libapr_memcache.la from libapr-memcache-dev package
  * Fix "Lintian reports hardening-no-relro" harding is done by new
    version of deb-helper. So is fix on next rebuild automatically
    (Closes: #735127)
  * debian/*.install, rules and control
    - Adjusted control and install file for multi-arch support

 -- Bastiaan Franciscus van den Dikkenberg <email address hidden> Sun, 16 Feb 2014 21:09:38 +0100

Changed in libapr-memcache (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.