Manoj Srivastava <[EMAIL PROTECTED]> (30/10/2005): > On Fri, 28 Oct 2005 17:00:54 +0200, Thomas Huriaux > <[EMAIL PROTECTED]> said: > > > Package: fvwm Severity: normal Tags: l10n > > > > In the last uploaded package, debconf-updatepo has not been > > launched, which means that the debconf translations are lost. For > > example: $ msgfmt --statistics fr.po 5 translated messages. $ > > debconf-updatepo 1 translated message, 4 fuzzy translations. > > Well, debconf-updatepo is always run during build time, so > this is not as serious as ti appears -- the binary packages would > have the right bits. But yes, I was in too much of a hurry while > preparing the package, and I have added msgfmt --statistics to the > build process.
It always depends on what you mean by serious, and especially for who it is serious :-) Here, the binary package is 100% right, but all the translations teams have no way to know that the translations are out of date because the source package is wrong. > > I suggest you to add this command in the clean target of the > > debian/rules (so here in debian/common/targets.mk) > > > Err, no. The clean target should not change stuff on the disk, > this is important for those of us who keep the sources in a version > control system. The clean target returns the on disk bits to the > state they were before the build; and no more. I know that the clean target does not seem appropriate, but if something has changed in *.po files by calling this target, then the sources in your version control system are wrong. To call it at clean time ensures you that your sources are "clean", which seems to be what the clean target aims at. This is what the l10n guys recommand to every maintainer, so if you think it's wrong and you have a good solution, please tell me. There are so many packages that have a similar problem that it should be good to find the best solution and to add a lintian check for this. Cheers, -- Thomas Huriaux
signature.asc
Description: Digital signature
