Subject: bug#33243: closed (Re: [bug#33243] [PATCH 0/1] Update libgcrypt)

From: [email-masked] (GNU bug Tracking System)
Date: Sun, 18 Nov 2018 12:04:03 +0000

Your bug report

#33243: [PATCH 0/1] Update libgcrypt

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
33243: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33243
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: [bug#33243] [PATCH 0/1] Update libgcrypt
From: Björn Höfling <[email-masked]>
To: [email-masked] (Ludovic Courtès), [email-masked]
Cc: Ricardo Wurmus <[email-masked]>, Leo Famulari <[email-masked]>
Date: Sun, 18 Nov 2018 13:03:25 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

On Fri, 16 Nov 2018 10:29:50 +0100
[email-masked] (Ludovic Courtès) wrote:

> Hello!
> 
> Björn Höfling <[email-masked]> skribis:
> 
> > On Wed, 14 Nov 2018 12:40:29 -0500
> > Leo Famulari <[email-masked]> wrote:
> >  
> >> On Wed, Nov 14, 2018 at 12:13:29PM +0100, Ludovic Courtès wrote:  
> >> > I think you could be that person.  :-)

Pushed under core-updates-next:

02d83c247931045cf899433223e1b1a51f605a9f

First push to Guix. Is everything fine?

Björn

Subject: [PATCH 0/1] Update libgcrypt
From: Björn Höfling <[email-masked]>
To: <[email-masked]>
Date: Fri, 2 Nov 2018 18:12:07 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

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?

Björn