unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 26247@debbugs.gnu.org
Subject: bug#26247: Gettext introduces timestamps in .mo files
Date: Tue, 01 Dec 2020 19:46:34 +0100	[thread overview]
Message-ID: <865z5luzxx.fsf@gmail.com> (raw)
In-Reply-To: <8760iyxp3t.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 24 Mar 2017 23:54:30 +0100")

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




  reply	other threads:[~2020-12-01 18:58 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 [this message]
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

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=865z5luzxx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=26247@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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).