On Thu, Oct 27, 2016 at 02:07:17PM +0200, Hilmar Preuße wrote: > Sorry to bother you again. The generated configure script seems to be broken > or incomplete:
arggg :( > Should we open a new bug for all this? IMHO yes. > > > I suggest you bring that upstream, not being able to run > > autoreconf -f -i > > on a autotools project is IMHO a bug that ought to be fixed. > > > Well, yes. Something to do in the future, not sure when. IMHO, this should be handled upstream. I've now looked for the first time at the upstream git repo, and I see the "configure" file being there: it shouldn't. All the artifacts of autotool are not supposed to be stored within a VCS, only generated at release time. Though that one seems to be kept up to date with configure.in; clearly they are not doing the same with the rest of autotools-generated artifacts. Considering that there are so many issues and maybe you want to upload soon rather than later, for me feel free to skip this point about autoreconf, but please try to get this fixed. btw, I peaked at the debian's git repository, and I saw that you used the git:// protocol in Vcs-Git; given that it's possible please avoid doing so, also see https://lintian.debian.org/tags/vcs-field-uses-insecure-uri.html -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
