Haven't had any time to review this or ask for help on dh , glad you took the time to do it (and push through to unstable).
I attempted to put together an autoreconf on my own, but had no success (the original dist files were not restored after a build, and nothing I did seemed to correct the situation). I'll figure out where I went wrong based on your change, sorry I couldn't respond prior to the commit. Regards, -George On Tue, Jun 24, 2014 at 12:49 PM, Wookey <woo...@wookware.org> wrote: > tags 727501 + patch > tags 727501 + pending > thanks > > Dear maintainer, > > This bug has been pending for some time, and needs fixing for new > ports, including arm64 which is building now: > (http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid). > > So I've prepared an NMU for rxvt (versioned as 1:2.7.10-5.1) and > uploaded it to DELAYED/7. Please feel free to tell me if I should > delay it longer. > > Discussion on debian-devel revealed consensus that the right way to > ensure successful builds on all new architectures was to autoreconf > packages, so that method has been used to fix this bug. This works for > all arches, even those that need libtool changes, and will continue to > work into the future without an update as each new arch comes along. > (Discussion at > https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread > starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html > > For this package dh_autoreconf-ing is a bit more intrusive than normal > because autoreconf needs to be run in a subdir, but the configure > script is copied out and run from the top level. Also the package only > uses autoconf so an autoreconf does not automatically update > config.{sub,guess} - that has to be done explicitly. > > Attached is a simpler alternate patch to just update > config.{sub,guess}, which is neater but is a less-technically complete > solution (see above thread). You could use this one instead if you > prefer. > > Regards. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org