bug#26247: Gettext introduces timestamps in .mo files

2023-10-17 Thread Julien Lepiller
It's interesting to see that only the generate po files are compiled to non-reproducible mo files. All other translations seem fine, right? Could it be related to the way these po files are created? It might introduce a timestamp at that point, but I can't check right now. Le 17 octobre 2023 01

bug#26247: Gettext introduces timestamps in .mo files

2023-10-17 Thread Simon Tournier
Hi, It is about this old bug#26247: https://issues.guix.gnu.org/issue/26247 On Sat, 08 Oct 2022 at 16:25, zimoun wrote: > On Fri, 11 Dec 2020 at 14:26, Miguel Ángel Arruga Vivas > wrote: > >> This bug has already been reported upstream[1] and probably I'll push it >> as soon as I have mor

bug#26247: Gettext introduces timestamps in .mo files

2022-10-08 Thread zimoun
Hi Miguel, It is about an old patch [2] and on old message from Dec. 2020. On Fri, 11 Dec 2020 at 14:26, Miguel Ángel Arruga Vivas wrote: > 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

bug#26247: Gettext introduces timestamps in .mo files

2020-12-14 Thread Ludovic Courtès
Hi Miguel, Miguel Ángel Arruga Vivas skribis: > Ludovic Courtès writes: > >> Julien Lepiller 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 reprodu

bug#26247: Gettext introduces timestamps in .mo files

2020-12-11 Thread Miguel Ángel Arruga Vivas
Hi! Ludovic Courtès writes: > Julien Lepiller 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 ge

bug#26247: Gettext introduces timestamps in .mo files

2020-12-03 Thread Ludovic Courtès
Julien Lepiller 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

bug#26247: Gettext introduces timestamps in .mo files

2020-12-03 Thread Julien Lepiller
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. Le 3 décembre 2020 05:32:54 GMT-05:00, "Ludovic Courtès" a écrit : >Hi Simon, > >zimoun skribis: > >> On Fri,

bug#26247: Gettext introduces timestamps in .mo files

2020-12-03 Thread Ludovic Courtès
Hi Simon, zimoun skribis: > On Fri, 24 Mar 2017 at 23:54, l...@gnu.org (Ludovic Courtès) wrote: > >> Gettext 0.19.8.1 (current core-updates, >> 77ab6983a19ef307558ab2607920158d6bb94ba8) introduces timestamps in .mo >> file, without honoring SOURCE_DATE_EPOCH, which leads to >> non-reproducible b

bug#26247: Gettext introduces timestamps in .mo files

2020-12-01 Thread zimoun
Hi Ludo, This old bug #26247 about timestamp in .mo files from Gettext is still open: On Fri, 24 Mar 2017 at 23:54, l...@gnu.org (Ludovic Courtès) wrote: > Gettext 0.19.8.1 (current core-updates, > 77ab6983a19ef307558ab2607920158d6bb94ba8) introduces

bug#26247: Gettext introduces timestamps in .mo files

2017-03-24 Thread Ludovic Courtès
Gettext 0.19.8.1 (current core-updates, 77ab6983a19ef307558ab2607920158d6bb94ba8) introduces timestamps in .mo file, without honoring SOURCE_DATE_EPOCH, which leads to non-reproducible builds (for example ‘guix’). Ludo’.