[bug#33243,0/1] Update libgcrypt

Message ID 20181102181207.2aa0cc01@alma-ubu
Headers show
Series Update libgcrypt | expand

Message

Björn Höfling Nov. 2, 2018, 5:12 p.m. UTC
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

Comments

Leo Famulari Nov. 2, 2018, 8:31 p.m. UTC | #1
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!
Björn Höfling Nov. 6, 2018, 6:45 a.m. UTC | #2
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
Ludovic Courtès Nov. 14, 2018, 11:13 a.m. UTC | #3
Hello Björn,

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:

> 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 think you could be that person.  :-)

Could you create an account on Savannah, upload the OpenPGP key you’ll
use to sign commits there (via the web UI), and reply to this message
signed with the same key and giving me your account name?

Thanks in advance!

Ludo’.
Leo Famulari Nov. 14, 2018, 5:40 p.m. UTC | #4
On Wed, Nov 14, 2018 at 12:13:29PM +0100, Ludovic Courtès wrote:
> I think you could be that person.  :-)
> 
> Could you create an account on Savannah, upload the OpenPGP key you’ll
> use to sign commits there (via the web UI), and reply to this message
> signed with the same key and giving me your account name?
> 
> Thanks in advance!

Great! Please also make sure to read the HACKING file in our Git repo.
Björn Höfling Nov. 18, 2018, 12:03 p.m. UTC | #5
On Fri, 16 Nov 2018 10:29:50 +0100
ludo@gnu.org (Ludovic Courtès) wrote:

> Hello!
> 
> Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
> 
> > On Wed, 14 Nov 2018 12:40:29 -0500
> > Leo Famulari <leo@famulari.name> 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
Leo Famulari Nov. 18, 2018, 10:34 p.m. UTC | #6
On Sun, Nov 18, 2018 at 01:03:25PM +0100, Björn Höfling wrote:
> Pushed under core-updates-next:
> 
> 02d83c247931045cf899433223e1b1a51f605a9f
> 
> First push to Guix. Is everything fine?

It looks good to me, thank you!