On Tue, Feb 1, 2011 at 11:37 PM, Craig Small <[email protected]> wrote: > 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.
Neat ! Thanks for the link, I now understand what was going on. -- Mathieu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/AANLkTinmyL5WaHxf-DGGHü05K16H=ä[email protected]
