Removed that cruft and re-submitted package.

On Thu, Mar 10, 2016 at 7:10 PM, Stephen Dennis <brazilof...@gmail.com>
wrote:

> Oh, all that cruft got through. Tried the templates. Didn't work. Need
> them now.
>
> At the airport. Will touch tonight.
> On Mar 10, 2016 7:07 PM, "Martin Michlmayr" <t...@hpe.com> wrote:
>
>> * Stephen Dennis <brazilof...@gmail.com> [2016-03-10 18:07]:
>> > * I did not add dh-autoreconf because as you say, the root problem is a
>> > config.{sub,guess} was stale. Unfortunately, there is code in
>> autoconf.h.in
>> > from a previous autoconf.h file which running autoreconf would step on.
>>
>> Ah, I see.  But if you're not running the tool, why do you close the
>> bug?  Oh, because you say that the autoconf scripts have been updated
>> in the tar ball.
>>
>> > * Yeah, 2.10 is out there and it works well. The problems like
>> autoconf.h.in
>>
>> Ok, makes sense.
>>
>> Anyway, in the new version, we now have:
>>
>> tinymux-2.6.5.34/debian/autoreconf.after
>> tinymux-2.6.5.34/debian/autoreconf.before
>> tinymux-2.6.5.34/debian/patches/deleteme
>>
>> which looks like cruft to me.
>>
>> Also, is tinymux-2.6.5.34/debian/patches/autoreconf-templates.diff
>> necessary and if so do you need to build-depend on something?
>> --
>> Martin Michlmayr
>> Linux for HPE Helion, Hewlett Packard Enterprise
>>
>

Reply via email to