Hello, On 19 May 2014 05:03, Vincent Cheng <vch...@debian.org> wrote: > - Why does debian/control now have "Build-Conflicts: autoconf2.13, > automake1.4"?
Probably because configure.in is for a newer autoconf, but doesn't have AC_PREREQ(), so the autoconf wrapper incorrectly detects it as autoconf2.13-compatible because of the name (.in). In my packages I just replace an autoconf call by a call to autoconf2.50. P.S. I haven't actually checked the package, this is just a guess based on the symptoms :) -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cacujmdnu5frpyp7w9b2gajgtyfxh9bbbcrprrmem7je_e+n...@mail.gmail.com
