On 28.08.2016 05:33, Russell Coker wrote: > On Wednesday, 24 August 2016 4:57:30 PM AEST Markus Koschany wrote: >> yes, we are in dire need of active maintainers. >> >> The last thing that I remember about warzone2100 is that upstream's >> source tarball doesn't ship "the preferred form for modification" for >> all of its source files. I haven't investigated this issue but that's >> probably the reason why Paul Wise hasn't updated the package yet. >> >> If you can help us packaging a new upstream release and confirm that the >> new release is compliant with the DFSG, that would be very much appreciated. > > I just had a quick hack on the source, I've attached a modified version of > the > 3.1.1-3 patches that applies to the 3.2.1 release. > > When I try to build I get the following error. What's the preferred solution > to this? Trying to get it to work with Automake 1.15 is probably > unreasonably > difficult (everything with Automake is horrible). Is there a good way of > building with automake1.11 when automake-1.15 is installed? > > dh_autoreconf ./autogen.sh > + checking for automake >= 1.12 ... found 1.15, ok. > Sorry, automake 1.12+ is not supported yet, please use 1.11. > dh_autoreconf: ./autogen.sh returned exit code 1
Thanks for taking a look. We already build-depend on automake-1.11 and you could prevent the installation of newer automake version by declaring a Build-Conflicts relationship which would solve #824011 too btw. Of course it would be preferable if we could simply use default automake since 1.11 will be removed from Debian sometime. Regards, Markus
signature.asc
Description: OpenPGP digital signature
