unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Leo Famulari <leo@famulari.name>
Cc: 33243@debbugs.gnu.org
Subject: [bug#33243] [PATCH 0/1] Update libgcrypt
Date: Tue, 6 Nov 2018 07:45:48 +0100	[thread overview]
Message-ID: <20181106074548.4973c9fe@alma-ubu> (raw)
In-Reply-To: <20181102203155.GC16537@jasmine.lan>

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

On Fri, 2 Nov 2018 16:31:55 -0400
Leo Famulari <leo@famulari.name> wrote:

> On Fri, Nov 02, 2018 at 06:12:07PM +0100, Björn Höfling wrote:
> > This patch updates libgcrypt to 1.8.4.
> > 
> > The reproducibility problem was fixed upstream and thus the patch
> > was removed from package definition.
> > 
> > I applied this on core-updates-next, was that the right branch?  
> 
> Yes, that's the right branch, thank you!

Just to be sure: I applied locally, someone with commit rights need to
commit it.

I also built gnupg successfully as a test.

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-11-06  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 17:12 [bug#33243] [PATCH 0/1] Update libgcrypt Björn Höfling
2018-11-02 17:31 ` [bug#33243] [PATCH 1/1] gnu: libgcrypt: Update to 1.8.4 Björn Höfling
2018-11-02 20:31 ` [bug#33243] [PATCH 0/1] Update libgcrypt Leo Famulari
2018-11-06  6:45   ` Björn Höfling [this message]
2018-11-14 11:13     ` Ludovic Courtès
2018-11-14 17:40       ` Leo Famulari
     [not found]         ` <20181116101358.65629d8c@alma-ubu>
     [not found]           ` <87y39t1ib5.fsf@gnu.org>
2018-11-18 12:03             ` bug#33243: " Björn Höfling
2018-11-18 22:34               ` [bug#33243] " Leo Famulari

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=20181106074548.4973c9fe@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=33243@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).