* Santiago Vila [Fri, 29 Jun 2007 16:58:13 +0200]: > Consider the case where the .diff.gz for a package updates a .po file but > not the corresponding .mo file (which are usually included in the original > tarball as well).
> You need to run ./configure at least to be able to run the clean target, > and you need to do "make" so that the .mo file is overwritten by the one > from the updated .po file (via msgfmt). > Then you try to build a second time and dpkg-source realizes that > it can't represent the change from the old .mo file to the new .mo file, > as it is a binary file. > I don't know how much typical this example is, but the two "can't build > twice in a row" bugs I got were like that. The you should/could remove the .mo files in your debian/rules clean target. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org And don't get me wrong - I don't mind getting proven wrong. I change my opinions the way some people change underwear. And I think that's ok. -- Linus Torvalds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]