Re: nautilus breakage due to mk.po
- From: Christian Rose <menthos gnome org>
- To: Alexander Larsson <alexl redhat com>
- Cc: GNOME I18N List <gnome-i18n gnome org>, Ivan Stojmirov <stojmir linux net mk>
- Subject: Re: nautilus breakage due to mk.po
- Date: Tue, 11 Jan 2005 00:12:14 +0100
mån 2005-01-10 klockan 19:34 +0100 skrev Alexander Larsson:
> Nautilus build is broken atm:
Ouch!
> mk.po:6611: duplicate message definition
> mk.po:3459: ...this is the location of the first definition
> mk.po:6618: duplicate message definition
> mk.po:3617: ...this is the location of the first definition
> mk.po:6626: duplicate message definition
> mk.po:3626: ...this is the location of the first definition
> /usr/bin/msgfmt: found 3 fatal errors
> make[2]: *** [mk.gmo] Error 1
> make[2]: Leaving directory `/gnome/head/cvs/nautilus/po'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/gnome/head/cvs/nautilus'
> make: *** [all-recursive-am] Error 2
> *** error during stage build of nautilus: could not build module ***
> [63/106]
>
> I'm disabling mk for now.
Translators: *Never ever* commit broken po files to CVS. That is a very,
very, very big no-no, since it breaks the build of the software and
makes almost all other contributors unable to work.
This is the reason why we request everyone to first check their po files
with msgfmt -cv before doing any commit of a po file.
Christian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]