Daniel Burrows <[EMAIL PROTECTED]> writes:
> On Sat, Nov 17, 2007 at 02:12:43PM +0100, Sven Joachim <[EMAIL PROTECTED]>
> was heard to say:
>> Apparently bug #441696 has reappeared. When I rebuilt aptitude twice
>> on my system, the .mo files were in the first package but not in the
>> second. Reopening #441696,
>
> It looks like the problem is that that fix was committed as a
> divergence from upstream in the Debian repository. When I was
> putting together the last Debian release, I discovered that it was
> failing to build because of changes to the .gmo files, found this
> deviation from upstream, and reverted it.
I do not quite understand. Why did it fail to build? And couldn't
this be remedied by running "make maintainer-clean all" in the po
directory to force the rebuild of the .gmo files?
> Is there a way to fix this without making the package unbuildable?
An alternative would be not to ship the *.gmo files at all in the
package, but to create them at build time. But in this case you would
need to run make maintainer-clean instead of distclean in the po
directory (or remove the files in the debian/rules clean target).
Note that if you don't ship po/*.gmo, you also should not ship the
po/stamp-po file.
Cheers,
Sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
