* bug#26247: Gettext introduces timestamps in .mo files
@ 2017-03-24 22:54 Ludovic Courtès
2020-12-01 18:46 ` zimoun
0 siblings, 1 reply; 10+ messages in thread
From: Ludovic Courtès @ 2017-03-24 22:54 UTC (permalink / raw)
To: 26247
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’.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
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
0 siblings, 1 reply; 10+ messages in thread
From: zimoun @ 2020-12-01 18:46 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 26247
Hi Ludo,
This old bug #26247 about timestamp in .mo files from Gettext is still
open:
<http://issues.guix.gnu.org/issue/26247>
On Fri, 24 Mar 2017 at 23:54, ludo@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 builds (for example ‘guix’).
Is it still relevant? Since Gettext is now at 0.20.1. How can I
reproduce the issue? Because the usual:
guix build gettext --no-grafts --check
works fine.
Cheers,
simon
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
2020-12-01 18:46 ` zimoun
@ 2020-12-03 10:32 ` Ludovic Courtès
2020-12-03 12:07 ` Julien Lepiller
0 siblings, 1 reply; 10+ messages in thread
From: Ludovic Courtès @ 2020-12-03 10:32 UTC (permalink / raw)
To: zimoun; +Cc: 26247
Hi Simon,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Fri, 24 Mar 2017 at 23:54, ludo@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 builds (for example ‘guix’).
>
> Is it still relevant? Since Gettext is now at 0.20.1. How can I
> reproduce the issue?
I still see this:
--8<---------------cut here---------------start------------->8---
$ guix challenge guix --substitute-urls="https://ci.guix.gnu.org https://bayfront.guix.gnu.org"
updating substitutes from 'https://bayfront.guix.gnu.org'... 100.0%
/gnu/store/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe contents differ:
no local build for '/gnu/store/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe'
https://ci.guix.gnu.org/nar/lzip/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe: 13wvxga668grzs0p6sp0ghvdiy96nc9w71vs11djjkypsaf7wpw1
https://bayfront.guix.gnu.org/nar/lzip/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe: 1rpwil9h2whjd9dbwpikxn8prkg924nhljglwj9yjijh578nlfr8
differing files:
/share/locale/en@quot/LC_MESSAGES/guix.mo
/share/locale/en@quot/LC_MESSAGES/guix-packages.mo
/share/locale/en@boldquot/LC_MESSAGES/guix.mo
/share/locale/en@boldquot/LC_MESSAGES/guix-packages.mo
/share/info/guix-cookbook.de.info.gz
/lib/guile/3.0/site-ccache/guix/workers.go
/lib/guile/3.0/site-ccache/guix/ui.go
/lib/guile/3.0/site-ccache/guix/swh.go
/lib/guile/3.0/site-ccache/guix/svn-download.go
[…]
--8<---------------cut here---------------end--------------->8---
‘--diff=diffoscope’ is not an option here because it takes too long
looking at all the .go files…
A focused diff shows this:
--8<---------------cut here---------------start------------->8---
$ diffoscope --exclude-directory-metadata=yes /tmp/{t1,t2}/share/locale/en@quot/
--- /tmp/t1/share/locale/en@quot/
+++ /tmp/t2/share/locale/en@quot/
│ --- /tmp/t1/share/locale/en@quot/LC_MESSAGES
├── +++ /tmp/t2/share/locale/en@quot/LC_MESSAGES
│ │ --- /tmp/t1/share/locale/en@quot/LC_MESSAGES/guix-packages.mo
│ ├── +++ /tmp/t2/share/locale/en@quot/LC_MESSAGES/guix-packages.mo
│ │ ├── msgunfmt {}
│ │ │ @@ -1,12 +1,12 @@
│ │ │ msgid ""
│ │ │ msgstr ""
│ │ │ "Project-Id-Version: guix 1.2.0-3.35a32fe\n"
│ │ │ "Report-Msgid-Bugs-To: bug-guix@gnu.org\n"
│ │ │ -"PO-Revision-Date: 2020-11-29 18:33+0000\n"
│ │ │ +"PO-Revision-Date: 2020-12-02 10:10+0000\n"
│ │ │ "Last-Translator: Automatically generated\n"
│ │ │ "Language-Team: none\n"
│ │ │ "Language: en@quot\n"
│ │ │ "MIME-Version: 1.0\n"
│ │ │ "Content-Type: text/plain; charset=UTF-8\n"
│ │ │ "Content-Transfer-Encoding: 8bit\n"
│ │ │ "Plural-Forms: nplurals=2; plural=(n != 1);\n"
│ │ --- /tmp/t1/share/locale/en@quot/LC_MESSAGES/guix.mo
│ ├── +++ /tmp/t2/share/locale/en@quot/LC_MESSAGES/guix.mo
│ │ ├── msgunfmt {}
│ │ │ @@ -1,12 +1,12 @@
│ │ │ msgid ""
│ │ │ msgstr ""
│ │ │ "Project-Id-Version: guix 1.2.0-3.35a32fe\n"
│ │ │ "Report-Msgid-Bugs-To: bug-guix@gnu.org\n"
│ │ │ -"PO-Revision-Date: 2020-11-29 18:33+0000\n"
│ │ │ +"PO-Revision-Date: 2020-12-02 10:10+0000\n"
│ │ │ "Last-Translator: Automatically generated\n"
│ │ │ "Language-Team: none\n"
│ │ │ "Language: en@quot\n"
│ │ │ "MIME-Version: 1.0\n"
│ │ │ "Content-Type: text/plain; charset=UTF-8\n"
│ │ │ "Content-Transfer-Encoding: 8bit\n"
│ │ │ "Plural-Forms: nplurals=2; plural=(n != 1);\n"
--8<---------------cut here---------------end--------------->8---
Ludo’.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
2020-12-03 10:32 ` Ludovic Courtès
@ 2020-12-03 12:07 ` Julien Lepiller
2020-12-03 14:41 ` Ludovic Courtès
0 siblings, 1 reply; 10+ messages in thread
From: Julien Lepiller @ 2020-12-03 12:07 UTC (permalink / raw)
To: Ludovic Courtès, zimoun; +Cc: 26247
[-- Attachment #1: Type: text/plain, Size: 4275 bytes --]
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" <ludo@gnu.org> a écrit :
>Hi Simon,
>
>zimoun <zimon.toutoune@gmail.com> skribis:
>
>> On Fri, 24 Mar 2017 at 23:54, ludo@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 builds (for example ‘guix’).
>>
>> Is it still relevant? Since Gettext is now at 0.20.1. How can I
>> reproduce the issue?
>
>I still see this:
>
>--8<---------------cut here---------------start------------->8---
>$ guix challenge guix --substitute-urls="https://ci.guix.gnu.org
>https://bayfront.guix.gnu.org"
>updating substitutes from 'https://bayfront.guix.gnu.org'... 100.0%
>/gnu/store/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe
>contents differ:
>no local build for
>'/gnu/store/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe'
>https://ci.guix.gnu.org/nar/lzip/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe:
>13wvxga668grzs0p6sp0ghvdiy96nc9w71vs11djjkypsaf7wpw1
>https://bayfront.guix.gnu.org/nar/lzip/babcmx68gkfxwzr3rmccan88dqjiqzb4-guix-1.2.0-3.35a32fe:
>1rpwil9h2whjd9dbwpikxn8prkg924nhljglwj9yjijh578nlfr8
> differing files:
> /share/locale/en@quot/LC_MESSAGES/guix.mo
> /share/locale/en@quot/LC_MESSAGES/guix-packages.mo
> /share/locale/en@boldquot/LC_MESSAGES/guix.mo
> /share/locale/en@boldquot/LC_MESSAGES/guix-packages.mo
> /share/info/guix-cookbook.de.info.gz
> /lib/guile/3.0/site-ccache/guix/workers.go
> /lib/guile/3.0/site-ccache/guix/ui.go
> /lib/guile/3.0/site-ccache/guix/swh.go
> /lib/guile/3.0/site-ccache/guix/svn-download.go
>[…]
>--8<---------------cut here---------------end--------------->8---
>
>‘--diff=diffoscope’ is not an option here because it takes too long
>looking at all the .go files…
>
>A focused diff shows this:
>
>--8<---------------cut here---------------start------------->8---
>$ diffoscope --exclude-directory-metadata=yes
>/tmp/{t1,t2}/share/locale/en@quot/
>--- /tmp/t1/share/locale/en@quot/
>+++ /tmp/t2/share/locale/en@quot/
>│ --- /tmp/t1/share/locale/en@quot/LC_MESSAGES
>├── +++ /tmp/t2/share/locale/en@quot/LC_MESSAGES
>│ │ --- /tmp/t1/share/locale/en@quot/LC_MESSAGES/guix-packages.mo
>│ ├── +++ /tmp/t2/share/locale/en@quot/LC_MESSAGES/guix-packages.mo
>│ │ ├── msgunfmt {}
>│ │ │ @@ -1,12 +1,12 @@
>│ │ │ msgid ""
>│ │ │ msgstr ""
>│ │ │ "Project-Id-Version: guix 1.2.0-3.35a32fe\n"
>│ │ │ "Report-Msgid-Bugs-To: bug-guix@gnu.org\n"
>│ │ │ -"PO-Revision-Date: 2020-11-29 18:33+0000\n"
>│ │ │ +"PO-Revision-Date: 2020-12-02 10:10+0000\n"
>│ │ │ "Last-Translator: Automatically generated\n"
>│ │ │ "Language-Team: none\n"
>│ │ │ "Language: en@quot\n"
>│ │ │ "MIME-Version: 1.0\n"
>│ │ │ "Content-Type: text/plain; charset=UTF-8\n"
>│ │ │ "Content-Transfer-Encoding: 8bit\n"
>│ │ │ "Plural-Forms: nplurals=2; plural=(n != 1);\n"
>│ │ --- /tmp/t1/share/locale/en@quot/LC_MESSAGES/guix.mo
>│ ├── +++ /tmp/t2/share/locale/en@quot/LC_MESSAGES/guix.mo
>│ │ ├── msgunfmt {}
>│ │ │ @@ -1,12 +1,12 @@
>│ │ │ msgid ""
>│ │ │ msgstr ""
>│ │ │ "Project-Id-Version: guix 1.2.0-3.35a32fe\n"
>│ │ │ "Report-Msgid-Bugs-To: bug-guix@gnu.org\n"
>│ │ │ -"PO-Revision-Date: 2020-11-29 18:33+0000\n"
>│ │ │ +"PO-Revision-Date: 2020-12-02 10:10+0000\n"
>│ │ │ "Last-Translator: Automatically generated\n"
>│ │ │ "Language-Team: none\n"
>│ │ │ "Language: en@quot\n"
>│ │ │ "MIME-Version: 1.0\n"
>│ │ │ "Content-Type: text/plain; charset=UTF-8\n"
>│ │ │ "Content-Transfer-Encoding: 8bit\n"
>│ │ │ "Plural-Forms: nplurals=2; plural=(n != 1);\n"
>--8<---------------cut here---------------end--------------->8---
>
>Ludo’.
[-- Attachment #2: Type: text/html, Size: 5140 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
2020-12-03 12:07 ` Julien Lepiller
@ 2020-12-03 14:41 ` Ludovic Courtès
2020-12-11 13:26 ` Miguel Ángel Arruga Vivas
0 siblings, 1 reply; 10+ messages in thread
From: Ludovic Courtès @ 2020-12-03 14:41 UTC (permalink / raw)
To: Julien Lepiller; +Cc: 26247
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?
We could remove them from ‘LINGUAS’, but we’d be losing something,
wouldn’t we?
Ludo’.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
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
2022-10-08 14:25 ` zimoun
0 siblings, 2 replies; 10+ messages in thread
From: Miguel Ángel Arruga Vivas @ 2020-12-11 13:26 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 26247
Hi!
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.
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.
Best regards,
Miguel
[1] https://savannah.gnu.org/bugs/?59658
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
2020-12-11 13:26 ` Miguel Ángel Arruga Vivas
@ 2020-12-14 9:09 ` Ludovic Courtès
2022-10-08 14:25 ` zimoun
1 sibling, 0 replies; 10+ messages in thread
From: Ludovic Courtès @ 2020-12-14 9:09 UTC (permalink / raw)
To: Miguel Ángel Arruga Vivas; +Cc: 26247
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’.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
2020-12-11 13:26 ` Miguel Ángel Arruga Vivas
2020-12-14 9:09 ` Ludovic Courtès
@ 2022-10-08 14:25 ` zimoun
2023-10-16 23:48 ` Simon Tournier
1 sibling, 1 reply; 10+ messages in thread
From: zimoun @ 2022-10-08 14:25 UTC (permalink / raw)
To: Miguel Ángel Arruga Vivas
Cc: Ludovic Courtès, Julien Lepiller, 26247
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 <rosen644835@gmail.com> 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 can prepare a patch for previous versions if it's needed too.
>
> Best regards,
> Miguel
>
> [1] https://savannah.gnu.org/bugs/?59658
Are commits 4343ca8ba5b02c8fe09e5bd681abbc0440ab8b08 and following the
ones mentioned here?
Well, I am not sure to understand if it had been fixed upstream [1].
Cheers,
simon
2: <http://issues.guix.gnu.org/issue/26247>
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
2022-10-08 14:25 ` zimoun
@ 2023-10-16 23:48 ` Simon Tournier
2023-10-17 10:11 ` Julien Lepiller
0 siblings, 1 reply; 10+ messages in thread
From: Simon Tournier @ 2023-10-16 23:48 UTC (permalink / raw)
To: Miguel Ángel Arruga Vivas
Cc: Ludovic Courtès, Julien Lepiller, 26247
Hi,
It is about this old bug#26247:
https://issues.guix.gnu.org/issue/26247
On Sat, 08 Oct 2022 at 16:25, zimoun <zimon.toutoune@gmail.com> wrote:
> On Fri, 11 Dec 2020 at 14:26, Miguel Ángel Arruga Vivas <rosen644835@gmail.com> 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 can prepare a patch for previous versions if it's needed too.
>>
>> Best regards,
>> Miguel
>>
>> [1] https://savannah.gnu.org/bugs/?59658
>
> Are commits 4343ca8ba5b02c8fe09e5bd681abbc0440ab8b08 and following the
> ones mentioned here?
>
> Well, I am not sure to understand if it had been fixed upstream [1].
The issue is still not fixed in Guix.
--8<---------------cut here---------------start------------->8---
$ guix time-machine --commit=b437896e87a51cc610388d4c462893652dd773e6 -- challenge guix --substitute-urls="https://ci.guix.gnu.org https://bordeaux.guix.gnu.org"
/gnu/store/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274 contents differ:
no local build for '/gnu/store/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274'
https://ci.guix.gnu.org/nar/lzip/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274: 1inv5ri4z35xz6cv9laiaf4nv9v9km7ggvbwcdhxpv5hkabsbjia
https://bordeaux.guix.gnu.org/nar/lzip/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274: 13njz5kn402g5larsbmbi25dx4w8azpbffqlkhyagc52hnbpqxaf
differing files:
[...]
/share/locale/en@boldquot/LC_MESSAGES/guix-packages.mo
/share/locale/en@boldquot/LC_MESSAGES/guix.mo
/share/locale/en@quot/LC_MESSAGES/guix-packages.mo
/share/locale/en@quot/LC_MESSAGES/guix.mo
1 store items were analyzed:
- 0 (0.0%) were identical
- 1 (100.0%) differed
- 0 (0.0%) were inconclusive
--8<---------------cut here---------------end--------------->8---
Cheers,
simon
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#26247: Gettext introduces timestamps in .mo files
2023-10-16 23:48 ` Simon Tournier
@ 2023-10-17 10:11 ` Julien Lepiller
0 siblings, 0 replies; 10+ messages in thread
From: Julien Lepiller @ 2023-10-17 10:11 UTC (permalink / raw)
To: Simon Tournier, Miguel Ángel Arruga Vivas
Cc: Ludovic Courtès, 26247
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:48:40 GMT+02:00, Simon Tournier <zimon.toutoune@gmail.com> a écrit :
>Hi,
>
>It is about this old bug#26247:
>
> https://issues.guix.gnu.org/issue/26247
>
>On Sat, 08 Oct 2022 at 16:25, zimoun <zimon.toutoune@gmail.com> wrote:
>> On Fri, 11 Dec 2020 at 14:26, Miguel Ángel Arruga Vivas <rosen644835@gmail.com> 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 can prepare a patch for previous versions if it's needed too.
>>>
>>> Best regards,
>>> Miguel
>>>
>>> [1] https://savannah.gnu.org/bugs/?59658
>>
>> Are commits 4343ca8ba5b02c8fe09e5bd681abbc0440ab8b08 and following the
>> ones mentioned here?
>>
>> Well, I am not sure to understand if it had been fixed upstream [1].
>
>The issue is still not fixed in Guix.
>
>--8<---------------cut here---------------start------------->8---
>$ guix time-machine --commit=b437896e87a51cc610388d4c462893652dd773e6 -- challenge guix --substitute-urls="https://ci.guix.gnu.org https://bordeaux.guix.gnu.org"
>/gnu/store/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274 contents differ:
> no local build for '/gnu/store/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274'
> https://ci.guix.gnu.org/nar/lzip/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274: 1inv5ri4z35xz6cv9laiaf4nv9v9km7ggvbwcdhxpv5hkabsbjia
> https://bordeaux.guix.gnu.org/nar/lzip/0znvqzij8lvf4lv7xxs126wxzgmx0zsw-guix-1.4.0-13.e863274: 13njz5kn402g5larsbmbi25dx4w8azpbffqlkhyagc52hnbpqxaf
> differing files:
>
>[...]
>
> /share/locale/en@boldquot/LC_MESSAGES/guix-packages.mo
> /share/locale/en@boldquot/LC_MESSAGES/guix.mo
> /share/locale/en@quot/LC_MESSAGES/guix-packages.mo
> /share/locale/en@quot/LC_MESSAGES/guix.mo
>
>1 store items were analyzed:
> - 0 (0.0%) were identical
> - 1 (100.0%) differed
> - 0 (0.0%) were inconclusive
>--8<---------------cut here---------------end--------------->8---
>
>Cheers,
>simon
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-10-17 10:42 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2022-10-08 14:25 ` zimoun
2023-10-16 23:48 ` Simon Tournier
2023-10-17 10:11 ` Julien Lepiller
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.