Bug#718893: RFS: coinutils/2.9.4-1 [ITA] -- CoinOR base library
I've been able to address all of the lintian issues except the
outdated autotools files. The coinor packages use a highly nonstandard
autotools work flow that's not compatible with autoreconf. They script
they use to run autotools appears to be:
https://projects.coin-or.org/BuildTools/browser/stable/0.7/run_autotools.
I've tried to hack this script by installing the required versions of
autoconf and automake, changing the executable names in the script,
and changing the AUTOTOOLS_DIR variable from $HOME to /usr (!), but
I'm not able to successfully run the script. The error (at the step of
running autoconf) is:
configure:323: error: possibly undefined macro: LT_LDFLAGS
This variable is defined in CoinUtils/coin.m4. I would appreciate some
tips to fix this, since I'm not very familiar with autotools.
Thanks,
Miles
On Tue, Aug 13, 2013 at 9:40 AM, Sébastien Villemot
<sebastien@debian.org> wrote:
> After a quick review of the package, I found the following issues that I
> would like you to fix before an upload:
>
> - make the package lintian clean, which means fix the 4 warnings. A few
> hints follow:
>
> + for the embedded javascript file, you should make the package depend
> on libjs-jquery, and replace the jquery.js file in your package with a
> symlink to the same file provided by libjs-jquery
>
> + for the debian/copyright file, the indentation of the paragraph
> describing the EPL is not correct; you should shift it right by one
> column, and replace empty lines by a space followed by a dot
>
> + for the outdated autotools files, you should regenerate them at
> build time using the dh-autoreconf helper
>
> - put the source of the package in a git repository on alioth under the
> debian-science tree, as explained in the Debian Science policy, and add
> the corresponding Vcs-* fields in the debian/control file. You need to
> create an alioth account and ask to join the Debian Science group there
> before being able to create the repository.
>
> - remove the obsolete README.source
Reply to: