On Tue, Feb 01, 2011 at 12:29:22PM +0100, Mathieu Malaterre wrote: > However the build failure is still there. What I do not understand > is that the debian-changes-3.6.0-1 patch is generated on the fly by > dpkg, therefore I cannot remove it (quilt pop): A rough rule of thumb is if you get a debian-changes file and you weren't expecting it, you're doing something wrong. The hard bit is working out what the "something wrong" is.
/usr/share/doc/autotools-dev/README.Debian.gz is a good file to read for starters. It sounds like you have old config.* files and are updating them. That's a good start! The clean target can delete or rebuild the config.* files and perhaps even run autogen.sh For the patching problem, you can ignore the changes because your script is going to nuke the files anyhow. It's explained pretty well at Raphael's blog entry at: http://raphaelhertzog.com/2011/01/28/3-ways-to-not-clutter-your-debian-source-package-with-autogenerated-files/ Just under "A new way to avoid the problem" I use this feature in pidgin-musictracker because upstream always forgets to regenerate his po files so my diff would be filled with useless updates. - Craig -- Craig Small VK2XLZ http://www.enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110201223717.ga18...@enc.com.au
