On 20.09.2016 03:47, Russell Coker wrote: > On Tuesday, 20 September 2016 1:55:14 AM AEST Markus Koschany wrote: >> Confirmed. The same happens here on my machine. Unfortunately that's a >> show-stopper. I think I will upload a new revision that Build-Conflicts >> with automake and thus resolves #824011 and then I push my changes to >> the SVN repo. Perhaps someone else is able to spot the mistake. > > I still think that a build-conflicts is the wrong option when you can make it > build with both packages installed. My patch allows it to build regardles of > any other packages installed. > > Why do you think that build-conflicts is the right solution?
Currently the game can only be built with automake1.11. That is even enforced with the revert-372eff6693e633e8d0d1d0b8a9ceb996a5c3f49f.patch. Maybe you forgot to include your patch in the debian directory that you attached to the bug report. When I build without automake1.11 the package FTBFS. So this patch needs an update but building with the default automake is of course the preferred solution. By the way the package builds fine in a clean environment even without the Build-Conflicts option, that's why I downgraded the severity.
signature.asc
Description: OpenPGP digital signature
