Hello Andreas,
On 11/12/2016 05:25 PM, Andreas Tille wrote:
> I'd prefer to skip this test anyway (or let the test suite pass even
> if it fails.
I looked into the source, and I guess excluding the test from the set is
the easiest and most straightforward way to achive the effect.
> Sure. If you confirm you would volunteer to exclude the test I'll
> delay the upload. I'd also fix some lintian issues before uploading.
I have written up a quick oneline patch that removes "AmberFF_test" from
the set of test programs to be built+run. It is already pushed to the
git repository and I updated d/changelog.
I put the upstream issue on watch with my github account, so I should™
get an email if something happens there.
> Thanks again for your very welcome help
>
> Andreas.
>
I don't mind helping out. I also forked ball upstream on github, maybe
I can add some automatic build/testsuite checks via Travis-CI. They
base their images on Ubuntu, but it should be a good start, and there's
always sid chroots.
I do expect that with the next release of ball, we have to rework (or
maybe, can outright drop) a lot of the debian/patches.
Hope this helps,
Danny
