2009/6/16 Jonas Smedegaard <d...@jones.dk> > On Tue, Jun 16, 2009 at 10:33:23AM +0200, Frank Lahm wrote: > >2009/6/16 Itai Seggev <is+deb...@cs.hmc.edu> > >> Any other suggestions? > > > >Although you're only reporting this problem with a rc and the final is > >alread available, whatever causes your error may still be present. > >Therefore I'm digging into this and will be talkin to the libtool > >folks. Stay tuned. > > I believe that this issue can be solved upstream by adding > AM_MAINTAINER_MODE to configure.in and using a more recent libtool when > preparing release tarballs.
I've just took another look at Debian list of patches to netatalk. As it seems you're touching configure.in amongst others. I'm not familiar with the workings of the Debian package building tools, but I guess in order for these patches to be applied they must re-run the Autotools toolchain, do they? If they do, it might be an issue in how they do that. @Itai: please try to configure and make the unpatched tarball as available from the Debian archive <http://ftp.de.debian.org/debian/pool/main/n/netatalk/netatalk_2.0.4~rc2.orig.tar.gz> -Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
