From: "Ludovic Courtès" <ludo@gnu.org>
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
Cc: 26247@debbugs.gnu.org
Subject: bug#26247: Gettext introduces timestamps in .mo files
Date: Mon, 14 Dec 2020 10:09:30 +0100 [thread overview]
Message-ID: <87sg88wy7p.fsf@gnu.org> (raw)
In-Reply-To: <875z58fp8e.fsf@gmail.com> ("Miguel Ángel Arruga Vivas"'s message of "Fri, 11 Dec 2020 14:26:25 +0100")
Hi Miguel,
Miguel Ángel Arruga Vivas <rosen644835@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Julien Lepiller <julien@lepiller.eu> skribis:
>>
>>> So it's not gettext itself, but our build system that generates the
>>> en@quote and en@boldquote files. Do we really need them? If so, we
>>> should find a way to generate them reproducibly.
>>
>> They’re generated automatically by the gettext Makefilery that we use,
>> so I don’t think there’s much we can do?
>
> The issue isn't on those files but on POT generation. Currently
> xgettext doesn't honor SOURCE_DATE_EPOCH to fill POT-Creation-Date,
> which is used to fill PO-Revision-Date for auto-generated po files.
> These files are included into tarballs generated by make dist, therefore
> its date is already fixed, but they aren't present on our git tree---for
> obvious reasons.
OK.
> This bug has already been reported upstream[1] and probably I'll push it
> as soon as I have more test cases prepared and receive a brief review,
> but I can prepare a patch for previous versions if it's needed too.
[...]
> [1] https://savannah.gnu.org/bugs/?59658
Thanks for getting to the bottom of this and for preparing a patch
upstream!
In ‘core-updates’, we could either wait for the next Gettext release or
apply your patch in the meantime.
Ludo’.
next prev parent reply other threads:[~2020-12-14 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 22:54 bug#26247: Gettext introduces timestamps in .mo files Ludovic Courtès
2020-12-01 18:46 ` zimoun
2020-12-03 10:32 ` Ludovic Courtès
2020-12-03 12:07 ` Julien Lepiller
2020-12-03 14:41 ` Ludovic Courtès
2020-12-11 13:26 ` Miguel Ángel Arruga Vivas
2020-12-14 9:09 ` Ludovic Courtès [this message]
2022-10-08 14:25 ` zimoun
2023-10-16 23:48 ` Simon Tournier
2023-10-17 10:11 ` Julien Lepiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg88wy7p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26247@debbugs.gnu.org \
--cc=rosen644835@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).