From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Libtiff 4.0.7 update Date: Tue, 22 Nov 2016 12:33:18 -0500 Message-ID: <20161122173318.GA22432@jasmine> References: <20161121164827.GA29287@jasmine> <87mvgs92ac.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55921) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c9Ewe-0004ix-Mq for guix-devel@gnu.org; Tue, 22 Nov 2016 12:33:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c9Ewc-0005WB-2s for guix-devel@gnu.org; Tue, 22 Nov 2016 12:33:24 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:34567) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c9Ewb-0005VL-SN for guix-devel@gnu.org; Tue, 22 Nov 2016 12:33:22 -0500 Content-Disposition: inline In-Reply-To: <87mvgs92ac.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> 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: Marius Bakke Cc: guix-devel@gnu.org --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 21, 2016 at 06:21:47PM +0100, Marius Bakke wrote: > Leo Famulari writes: >=20 > > This updates libtiff to the latest upstream version, 4.0.7. I went > > through the tarball and confirmed that all the patches were contained in > > it but, please, double-check :) > > > > Also, libtiff has new source and home-page URLs. Read all about it: > > > > http://www.asmail.be/msg0054885794.html > > > > It will require ~1600 rebuilds. >=20 > Sweet. Perhaps it should be grafted on master first, then merge it and > ungraft on core-updates? Either approach will cause conflicts if there > are further updates to libtiff before next core-updates merge, so not > sure which is better. I updated the graft on master, and I'll handle the core-updates merge later today. --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlg0gV4ACgkQJkb6MLrK fwierBAAyFJfRjwKKklBPF54YgjCIy8jMdYrV7RHHMLDcMglCxMJTbIr3KRRja17 1qVw8Oyy0crdSKyGOefmuC0tOU7sgawS8mJBy9EtFAqqc6GuufCPhqUQfyjWnIN7 CUm65ndp3G9WJBxDSkJU0ub8uFbdYSWG8xQJYp65PyyanSQKZzc2H1tyfFtpvyox lRLxYW/boGweJ67CU+cVo2Os/JrJMm6jxbjylx6+nNm1j1GdTd3EYyQ9PDWrOxtU 8DG1xYJpsu/2irDLIkPrbzmFpd/EbjF461LgA5syATvzfBkJ0cR1CKR7/vJUi1H8 oPMUAwbEG4DayUPALUcmjgeos+agSsn6ENBtAESrcQo7biYOKuodZEbyEOlpgGAn WwlSA+vJ0zs6Al6F4n+9nPzmNHqGC69vXpvWOzquFrEFIwoGyhY66U6Wrg7JQftT VscecpNPbzUwQt8YMwms0ACilMxx7V5CJT+Ag1HQkyn30gDU4QkF3qNOIup3tPn0 caepAAHpkW9H4lvhZliYpZ5LhNpYTkvRjrXOf5jkJLZQzb7+36uddl0pp2mChkcU C5AardV22/HE0fhO7H2zGWaOMYVJvbVndpv5R7KPiDzHW1n/xLOoSWM+almit8Hx /d9juFguhdFM0IJvjF4Kqw3sHnoiZoNVtE6y+NPAJf/+SjCtY2w= =AQAk -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--