On 23/04/2015 11:39 am, NIIBE Yutaka wrote: > On 04/22/2015 04:22 PM, Werner Koch wrote: >> On Sat, 18 Apr 2015 21:35, [email protected] said: >> >>> [email protected]:54: 'msgid' and 'msgstr' entries do not both end with '\n' >>> [email protected]:58: 'msgid' and 'msgstr' entries do not both end with '\n' >> >>> but no need to paste them all in); obviously the cause is somewhere >>> in those sed or make rules. I'm just not certain of the right place >> >> That script (po/quot.po) did not changed for more than a decade. I >> guess your sed is broken (did you recently update it)? > > I think that there is a minor GnuPG problem here (not MacOS). > > I haven't located the bug yet, but I could see the problem of > [email protected], when I build with git repo having old [email protected]. > > Note that in the release, we have po/[email protected] which is correctly > updated and po/[email protected] which is correctly generated.
Ah-ha! :) > In the git repo, we have an entry of po/[email protected] in the .gitignore, > so, I think that it is not maintained in the repo. When a developer > happens to have old po/[email protected], it will be merged by msgmerge and > it would result fuzzy entries with mismatches of newline. > > For me, removing po/[email protected] (so that it will be rebuild from > gnupg2.pot), it works fine. Cool. Since 2.1 is on a one month cycle, I might just wait for 2.1.4 and try again, that'll give me the changes made from 2.1.3 and not trying to make a release equivalent tarball from the current repo (although if there's a script for that I might do it later today). Regards, Ben
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
