From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PATCH] gnu: libgcrypt update to 1.7.1 Date: Fri, 17 Jun 2016 22:44:46 +0000 Message-ID: <20160617224446.GA9320@khazad-dum> References: <20160615195328.GA13352@khazad-dum> <20160616154047.GC2245@jasmine> <20160616162825.GB29687@debian-netbook> <87d1nfvox7.fsf@gnu.org> <20160617174302.GA8255@jasmine> <20160617185923.GA24906@khazad-dum> <20160617192836.GA17273@jasmine> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56219) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bE2VY-0001XT-Fb for guix-devel@gnu.org; Fri, 17 Jun 2016 18:45:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bE2VU-0001yv-Fp for guix-devel@gnu.org; Fri, 17 Jun 2016 18:44:59 -0400 Received: from 93-95-228-168.1984.is ([93.95.228.168]:46130 helo=beleriand.n0.is) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bE2VU-0001xc-2Q for guix-devel@gnu.org; Fri, 17 Jun 2016 18:44:56 -0400 Received: by beleriand.n0.is (OpenSMTPD) with ESMTPSA id 825927fb TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO for ; Fri, 17 Jun 2016 22:44:50 +0000 (UTC) Content-Disposition: inline In-Reply-To: <20160617192836.GA17273@jasmine> 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 --s/l3CgOIzMHHjg/5 Content-Type: multipart/mixed; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-06-17(03:28:36-0400), Leo Famulari wrote: > On Fri, Jun 17, 2016 at 06:59:23PM +0000, ng0 wrote: > > On 2016-06-17(01:43:02-0400), Leo Famulari wrote: > > > On Fri, Jun 17, 2016 at 05:02:44PM +0200, Ludovic Court=C3=A8s wrote: > > > > Efraim Flashner skribis: > > > > > > > > > On Thu, Jun 16, 2016 at 11:40:47AM -0400, Leo Famulari wrote: > > > > >> On Wed, Jun 15, 2016 at 07:53:28PM +0000, ng0 wrote: > > > > >> > * gnu/packages/gnupg.scm (libgcrypt): Update to 1.7.1 > > > > >> > > > > >> This looks good to me. What branch should it go on? > > > > >> > > > > > > > > > > either core-updates or core-updates-next > > > > > > > > The latter please. :-) > > > > > > Okay, in that case, can you rebase it on core-updates, ng0? Otherwise= is > > > won't apply cleanly due to trying to upgrade from 1.6.5 instad of 1.7= =2E0. > > > > > > > This should be relatively easy when I have the gnupg branch still aroun= d, > > otherwise I'll recreate it. > > > > With the wording familiar to me yet sometimes not good to comprehend ev= en > > when I hear and parse it correctly when talking: > > I should rebase the commit on the branch > > `core-updates` which currently is at version 1.6.5? > > I think your copy of core-updates needs to be updated. I pushed your > patch "gnu: libgcrypt: Update to 1.7.0" as 81068f178 to it in April ;) > > All you need to do is get the latest core-updates, and then re-do this > patch on that branch, so that it updates from 1.7.0 instead of 1.6.5. > You don't need to do anything with gnupg. That was the name of the branch where I worked on gnupg.scm, that's why. inlined and appened the rebase on core-updates (I left out the header as this was already added with the gnupg update): =46rom 372943f91376905ebefe47372cdf55e1c14bc165 Mon Sep 17 00:00:00 2001 =46rom: ng0 Date: Fri, 17 Jun 2016 22:35:18 +0000 Subject: [PATCH] gnu: libgcrypt: Update to 1.7.1. * gnu/packages/gnupg.scm (libgcrypt): Update to 1.7.1. --- gnu/packages/gnupg.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm index 2ef2410..f2b53c2 100644 --- a/gnu/packages/gnupg.scm +++ b/gnu/packages/gnupg.scm @@ -74,14 +74,14 @@ Daemon and possibly more in the future.") (define-public libgcrypt (package (name "libgcrypt") - (version "1.7.0") + (version "1.7.1") (source (origin (method url-fetch) (uri (string-append "mirror://gnupg/libgcrypt/libgcrypt-" version ".tar.bz2")) (sha256 (base32 - "14pspxwrqcgfklw3dgmywbxqwdzcym7fznfrqh9rk4vl8jkpxrmh")))) + "15bsdpihb8xvr2a6sh0ikzw9wdw3gdi4pl1vpr6wc48npzy9q3a5")))) (build-system gnu-build-system) (propagated-inputs `(("libgpg-error-host" ,libgpg-error))) -- 2.8.4 It's the very same, so I did not check it, build functionality shold be exactly the same as in master, given that the last commit is a merge of master. -- =E2=99=A5=E2=92=B6 ng0 For non-prism friendly talk find me on psyced.org / loupsycedyglgamf.onion --2fHTh5uZTiUOsy+g Content-Type: text/x-diff; charset=utf-8 Content-Disposition: attachment; filename="0001-gnu-libgcrypt-Update-to-1.7.1.patch" Content-Transfer-Encoding: quoted-printable =46rom 372943f91376905ebefe47372cdf55e1c14bc165 Mon Sep 17 00:00:00 2001 =46rom: ng0 Date: Fri, 17 Jun 2016 22:35:18 +0000 Subject: [PATCH] gnu: libgcrypt: Update to 1.7.1. * gnu/packages/gnupg.scm (libgcrypt): Update to 1.7.1. --- gnu/packages/gnupg.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm index 2ef2410..f2b53c2 100644 --- a/gnu/packages/gnupg.scm +++ b/gnu/packages/gnupg.scm @@ -74,14 +74,14 @@ Daemon and possibly more in the future.") (define-public libgcrypt (package (name "libgcrypt") - (version "1.7.0") + (version "1.7.1") (source (origin (method url-fetch) (uri (string-append "mirror://gnupg/libgcrypt/libgcrypt-" version ".tar.bz2")) (sha256 (base32 - "14pspxwrqcgfklw3dgmywbxqwdzcym7fznfrqh9rk4vl8jkpxrmh")))) + "15bsdpihb8xvr2a6sh0ikzw9wdw3gdi4pl1vpr6wc48npzy9q3a5")))) (build-system gnu-build-system) (propagated-inputs `(("libgpg-error-host" ,libgpg-error))) --=20 2.8.4 --2fHTh5uZTiUOsy+g-- --s/l3CgOIzMHHjg/5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iF4EARYKAAYFAldkfV4ACgkQhhoAchyzrCDaXQEAjeJc5u1E/nE4lyASxingaFGZ OzfLIV0VLJd3zpiURwgBAOoUdjHCuskl33mTiRBmkvA7vJxfkzLpySxQHOpDAEoM =QOXR -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5--