2009/6/16 Jonas Smedegaard <d...@jones.dk> > >> 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. > > > >But you are *not* patching _generated_ files here. You are patching > >configure.in in this case. ?? > > Bingo! > Until recently I regenerating files, and then switched back to applying > patches only. I clearly missed that configure.in still got patched. > Thanks a lot for spotting this. The error is mine. I will fix this for > the next release (where I will also bump to the official upstream > release)!
Great! As said, there are a few more patches doing that, e.g. the zeroconf patch. > >> 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. > > > >AM_MAINTAINER_MODE might indeed fix this issue, but afaict the problem > >is caused because you touch autoconf stuff (configure.in, m4 macros) > >and rerun autotools. > > From my current knowledge, I do not even think that AM_MAINTAINER_MODE > would have helped here: I broke the chain, I need to fix it. Probably the error code would have been different like "autoconf not installed" or whatever error is thrown exactly when automake reruns the autotools chain and one of the tools is not installed on the host. > >> Please note that this Bug Tracker relates to packaged software, not > >> upstream. > > > >Yeah, and bugs that effect upstream have always been reported there > >too... I'm just actively digging into this because I'm afraid it might > >be some _upstream_ issue. > > Thanks. And sorry again for my misunderstanding and biting at you. No problem. -Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
