From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PATCH] version bump libgcrypt -> 1.7 Date: Sat, 14 May 2016 23:54:30 +0000 Message-ID: <20160514235430.GA28037@khazad-dum> References: <877ffx45n6.fsf@libertad.pw> <8737qkeknd.fsf@gmail.com> <87oa98ftn4.fsf@libertad.pw> <20160418203241.GA26832@jasmine> <87twiwqkk3.fsf@gnu.org> <20160421163242.GB10513@jasmine> <871t5vgk6d.fsf@gnu.org> <20160511125004.GB15340@khazad-dum> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43325) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1joG-0006Bl-M0 for guix-devel@gnu.org; Sat, 14 May 2016 20:21:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b1joB-0006QB-0m for guix-devel@gnu.org; Sat, 14 May 2016 20:21:27 -0400 Received: from 93-95-228-168.1984.is ([93.95.228.168]:54609 helo=beleriand.n0.is) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1joA-0006Ow-Kj for guix-devel@gnu.org; Sat, 14 May 2016 20:21:22 -0400 Received: by beleriand.n0.is (OpenSMTPD) with ESMTPSA id 1722fd4c TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO for ; Sat, 14 May 2016 23:54:39 +0000 (UTC) Content-Disposition: inline In-Reply-To: <20160511125004.GB15340@khazad-dum> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org On 2016-05-11(12:50:04PM+0000), ng0 wrote: > On 2016-04-24(04:23:22+0200), Ludovic Courtès wrote: > > Leo Famulari skribis: > > > > > On Wed, Apr 20, 2016 at 07:03:40PM +0200, Ludovic Courtès wrote: > > >> Leo Famulari 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