Package: gtkmm3.0
Severity: normal
Version: 3.8.1-1
Tags: patch
User: [email protected]
Usertags: origin-ubuntu ubuntu-patch trusty

Hi,

The ppc64el port requires a patch to libtool.m4.  I don't think that's
in Debian yet, but when it is it will require autoreconfing a bunch of
packages to pick it up.  cwidget could handle this quite easily by using
dh-autoreconf rather than just cdbs autotools-dev; when libtool is in
use (as of course it is here), dh-autoreconf is a superset of
autotools-dev, and it seems to still build just fine if I do the
following.

diff -Nru gtkmm3.0-3.10.1/debian/control.in gtkmm3.0-3.10.1/debian/control.in
--- gtkmm3.0-3.10.1/debian/control.in   2013-12-16 23:33:17.000000000 +0000
+++ gtkmm3.0-3.10.1/debian/control.in   2013-12-20 02:02:17.000000000 +0000
@@ -1,13 +1,15 @@
 Source: gtkmm3.0
 Section: libs
 Priority: optional
-Maintainer: Debian GNOME Maintainers 
<[email protected]>
+Maintainer: Ubuntu Developers <[email protected]>
+XSBC-Original-Maintainer: Debian GNOME Maintainers 
<[email protected]>
 Uploaders: @GNOME_TEAM@
 Homepage: http://www.gtkmm.org/
 Vcs-Browser: 
http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gtkmm3.0
 Vcs-Svn: svn://anonscm.debian.org/svn/pkg-gnome/desktop/unstable/gtkmm3.0
 Build-Depends: cdbs (>= 0.4.93),
                debhelper (>= 8.1.3),
+              dh-autoreconf,
                gnome-pkg-tools (>= 0.11),
                libgtk-3-dev (>= 3.10.0),
                libglibmm-2.4-dev (>= 2.38.0),
diff -Nru gtkmm3.0-3.10.1/debian/rules gtkmm3.0-3.10.1/debian/rules
--- gtkmm3.0-3.10.1/debian/rules        2013-12-16 23:33:17.000000000 +0000
+++ gtkmm3.0-3.10.1/debian/rules        2013-12-20 02:08:29.000000000 +0000
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+include /usr/share/cdbs/1/rules/autoreconf.mk
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/rules/utils.mk
 include /usr/share/cdbs/1/class/autotools.mk


--
Regards,

Dimitri.


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

Reply via email to