Your message dated Mon, 5 Sep 2016 17:09:44 -0300
with message-id <[email protected]>
and subject line 
has caused the Debian Bug report #748160,
regarding ripperx: autoreconf FTBFS on new arches (as 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.)


-- 
748160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748160
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ripperx
Version: 2.7.3
Severity: normal
Tags: patch
User: [email protected]
Usertags: ppc64el
User: [email protected]
Usertags: autoreconf

Dear Maintainer,

Currently ripperx package is not able to be built on the new ports due to not
being auto reconfigured before building.  As suggested by in [1], I am creating
a patch for it, please, consider accepting it.

I understand that the package will need to have the following files NEWS README
AUTHORS ChangeLog also.

[1] - 
https://wiki.debian.org/qa.debian.org/FTBFS#A2014-01-21_using_dh-autoreconf_during_the_build
Thank you,

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

Kernel: Linux 3.13-1-powerpc64le (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Index: ripperx-2.7.3/debian/control
===================================================================
--- ripperx-2.7.3.orig/debian/control	2013-07-13 13:48:49.000000000 +0000
+++ ripperx-2.7.3/debian/control	2014-05-14 21:33:21.000000000 +0000
@@ -4,7 +4,7 @@
 Maintainer: tony mancill <[email protected]>
 Uploaders: gregor herrmann <[email protected]>
 Build-Depends: debhelper (>= 7), libgtk2.0-dev, libglib2.0-dev, libid3-dev,
- libz-dev, autoconf, gawk
+ libz-dev, autoconf, gawk, dh-autoreconf
 Standards-Version: 3.9.1
 Vcs-Svn: http://dorf.mancill.com/svn/deb/ripperx/
 Vcs-Browser: http://dorf.mancill.com/websvn/listing.php?repname=debian+SVN+repository&path=%2Fripperx%2F
Index: ripperx-2.7.3/debian/rules
===================================================================
--- ripperx-2.7.3.orig/debian/rules	2010-11-13 21:35:35.000000000 +0000
+++ ripperx-2.7.3/debian/rules	2014-05-14 21:32:54.000000000 +0000
@@ -8,6 +8,7 @@
 configure: configure-stamp
 configure-stamp:
 	dh_testdir
+	dh_autoreconf
 	# Add here commands to configure the package.
 	CFLAGS=-O1 sh ./configure --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --libexecdir=/usr/lib/ripperx
 
@@ -22,6 +23,7 @@
 clean:
 	dh_testdir
 	dh_testroot
+	dh_autoreconf_clean
 	rm -f build-stamp configure-stamp
 	dh_clean configure-stamp build-stamp install-stamp
 

--- End Message ---
--- Begin Message ---
I understand that this bug is fixed now, since ripperx builds fine on ppc64el.

I am closing this bug. Thanks for the support,
Breno

--- End Message ---

Reply via email to