-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On Tue, Jun 16, 2009 at 11:59:23AM +0200, Frank Lahm wrote: >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.
Yes, that might certainly be an issue. And if that is an issue, the solution is *not* to compile unpatched code by hand, but to fix that issue. You've asked those patches before, and I told you not (as upstream) to worry about those pathces to autogenerated files): I agree that they are not of concern for upstream. Let me elaborate (since you seem to stay interested): first the upstream files are patched, then the autogenerated files are patched. This is separated to ensure timestamps are skewed only in the right direction, to not trigger regeneration of those files. I believe that the problem here is *not* with those files, however. As I wrote already, I beleive it is tied to libtool: Debian use a much newer libtool that used upstream, and it seems (also experienced in other packages that I maintain) that if libtool acts up (which can be suppressed my AM_MAINTAINER_MODE that you sadly do not use currently), then too big differences in versions of libtool and automake won't work. I suspect that the concrete issue was triggered by libltdl3-dev missing initially, and after that the autogenerated files was broken beyond repair. That's why I explicitly requestes to test from scratch, not continue to try build same unpacked source, that has now gone sour. >@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> What would be the point of such test? Please note that this Bug Tracker relates to packaged software, not upstream. Kind regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAko3dQQACgkQn7DbMsAkQLh1OwCfe1CsFa2Lhq/CBFDec2o3zuUb OVoAn1sgQgHnU7vmG6y8rGA0/ljcc9gh =Ucll -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
