unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: guix-devel@gnu.org
Subject: Re: [PATCH] version bump libgcrypt -> 1.7
Date: Sat, 14 May 2016 23:54:30 +0000	[thread overview]
Message-ID: <20160514235430.GA28037@khazad-dum> (raw)
In-Reply-To: <20160511125004.GB15340@khazad-dum>

On 2016-05-11(12:50:04PM+0000), ng0 wrote:
> 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/

I guess It is safe to say that libgcrypt-1.7 does not break gnunet-gtk
functionality, it has to be everything else I am looking at but not
libgcrypt, error introduced itself on a new build system with
libgcrypt-1.6.5

-- 
♥Ⓐ ng0
4096R/13212A27975AF07677A29F7002A296150C201823

  reply	other threads:[~2016-05-15  0:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16 21:15 [PATCH] version bump libgcrypt -> 1.7 ng0
2016-04-17  7:53 ` Alex Kost
2016-04-17  9:36   ` ng0
2016-04-17  9:53   ` ng0
2016-04-18 20:32     ` Leo Famulari
2016-04-19  8:27       ` Alex Kost
2016-04-19  9:27         ` ng0
2016-04-20 17:03       ` Ludovic Courtès
2016-04-21 16:32         ` Leo Famulari
2016-04-24 14:23           ` Ludovic Courtès
2016-05-11 12:50             ` ng0
2016-05-14 23:54               ` ng0 [this message]
2016-05-15 17:49                 ` Leo Famulari
2016-04-17 20:21 ` Leo Famulari
2016-04-17 22:02   ` ng0

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=20160514235430.GA28037@khazad-dum \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    /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).