On 2016-04-24(04:23:22+0200), Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > On Wed, Apr 20, 2016 at 07:03:40PM +0200, Ludovic Courtès wrote:
> >> Leo Famulari <leo@famulari.name> skribis:
> >> 
> >> > On Sun, Apr 17, 2016 at 11:53:51AM +0200, ng0 wrote:
> >> >> Updated libgcrypt patch.
> >> >
> >> > Is there a consensus on upgrading from 1.6.5 and making the change on
> >> > core-updates?
> >> 
> >> OK for doing it in ‘core-updates’!
> >
> > Done in 81068f178.
> >
> >> In an ideal world, we’d do it in a separate branch to check for
> >> breakage, but currently we lack the computational resources to do so.
> >
> > I'm going to build a new system with some changes to core packages. I
> > could test this change as well. Are there any libgcrypt-dependent
> > packages I should pay particular attention to?
> 
> Not particularly.  This new version is API- and ABI-compatible, so I’m
> rather confident.
> 
> Ludo’.

So I am not sure if this is libgcrypt-1.7 related, I am still debugging
this and will ask on gnunet-dev and proxy-maint-gentoo about this later,
but there's a slight chance that gnunet-gtk breaks with libgcrypt-1.7[1].
It might of course be the ebuild rewrite causing this, that's what I'm
trying to find out.
Just a heads up and notice on why nothing happened with the guix
packages of gnunet, I'm stuck with debugging the last 1% before gnunet
suite gets into portage.

I hope this is not libgcrypt-1.7 related, but if it is, I'll adjust all
packages accordingly until gnunet is patched to this.

[1]: http://www.n0.is/static/pub/p/gnunet/debug/ and
    http://far37qbrwiredyo5.onion/static/pub/p/gnunet/debug/
-- 
♥Ⓐ ng0