all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 32410-done@debbugs.gnu.org
Subject: bug#32410: [PATCH] libgcrypt: Make it reproducible
Date: Thu, 16 Aug 2018 17:11:06 -0400	[thread overview]
Message-ID: <20180816211106.GC29448@jasmine.lan> (raw)
In-Reply-To: <20180809170429.52a33b8f@alma-ubu>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

On Thu, Aug 09, 2018 at 05:04:29PM +0200, Björn Höfling wrote:
> This is a fix for core-updates.
> 
> The libgcrypt package contains a yat2m command that adds a timestamp
> into the generated man-page. The (more or less) same C-file exits
> also in the packages gnupg and libgpg-error. There it already considers
> SOURCE_DATE_EPOCH. I diffed from gnupg and removed unrelated things.
> 
> I will also report upstream.

Thanks, please reply with a link to the upstream discussion.

> From 908c760f89ae5b47edbb0124339eab5801196f62 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Bj=C3=B6rn=20H=C3=B6fling?=
>  <bjoern.hoefling@bjoernhoefling.de>
> Date: Thu, 9 Aug 2018 16:45:45 +0200
> Subject: [PATCH] gnu: libgcrypt: Make build reproducible.
> 
> * gnu/packages/patches/libgcrypt-make-yat2m-reproducible.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add it.
> * gnu/packages/gnupg.scm (libgcrypt)[source]: Use it.

Pushed as 4866cba66ae40d722bb6c50b7dca27725ffa4532

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-08-16 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09 15:04 [bug#32410] [PATCH] libgcrypt: Make it reproducible Björn Höfling
2018-08-14  5:06 ` Björn Höfling
2018-08-16 21:11 ` Leo Famulari [this message]
2018-08-17  7:40   ` Björn Höfling

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180816211106.GC29448@jasmine.lan \
    --to=leo@famulari.name \
    --cc=32410-done@debbugs.gnu.org \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    /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 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.