From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36159) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fB2Cd-0006sc-NZ for guix-patches@gnu.org; Tue, 24 Apr 2018 13:58:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fB2CY-0006LH-Sg for guix-patches@gnu.org; Tue, 24 Apr 2018 13:58:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58736) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fB2CY-0006L5-OL for guix-patches@gnu.org; Tue, 24 Apr 2018 13:58:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fB2CY-0006Kp-DC for guix-patches@gnu.org; Tue, 24 Apr 2018 13:58:02 -0400 Subject: [bug#30448] Breaking rdiff-backup and btar (was Re: [bug#30448] Update librsync to 2.0.1) Resent-Message-ID: Date: Tue, 24 Apr 2018 13:57:15 -0400 From: Leo Famulari Message-ID: <20180424175715.GA14535@jasmine.lan> References: <20180213190113.GA22610@jasmine.lan> <87zi4a8h0v.fsf@gnu.org> <87k1sy2i6u.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <87k1sy2i6u.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: Eric Bavier , 30448@debbugs.gnu.org --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 23, 2018 at 02:58:17PM +0200, Ludovic Court=C3=A8s wrote: > ludo@gnu.org (Ludovic Court=C3=A8s) skribis: >=20 > > Leo Famulari skribis: > > > >> Is anyone using one of the dependent packages interested in looking mo= re > >> closely at this? > > > > I=E2=80=99m not using it, but at first sight the patch LGTM. >=20 > Ping! :-) My understanding is this update will break btar and rdiff-backup. I suspect this will annoy some Guix users. Plus, I don't know if these projects make an effort to detect MD4 collisions or not; perhaps they are safe to use despite the broken librsync dependency. We could add an old librsync package variant for those packages, but we should add a note about the reliance on MD4. I'll wait a few days for more feedback. PS =E2=80=94 this issue highlighted for me that the duplicity backup program also depends on librsync with MD4. For recent versions of librsync, duplicity forces librsync to fallback to MD4... --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlrfb/cACgkQJkb6MLrK fwgv4w/+Ok35Ie+bPnHbawLuYiWrCiuAYfitw683OeJj38A8HNJ/I8r2sX06JE3K 1tYUFqv0F2rBLaYUwMvOWn5Zs40d7sBE9GenibFu6j9fyBE4FjHlbmWDw9PPLBVX q+ZgDW+tuTJqFskpvtD6C6thfY89NMMfnE24eXeKi3bAy/fkn2/jIZ3gDuaCK+Dp MmjD/vXuVBPoBcvGeK0OiEAcq6QQ5ti1Iqv3LF48xUgtN4/ybtW6MGG2M2fX/2et jbY+BJnCzYlAjxSRL1PQbJEzjZhd0E0piK48OC3x4b4PLWK509Y9y4HlAusnV7ze oWKqfocsINGqZSfMrLfTuIVJuV1ojodfopFMlCrRUg4fb2tZhjhqRjyTcHo/SuTF 9poEhzqN7qjBIJqFmrp8kFXYyB3hhwkwN14TUvIU9mX0Exap8sR4AE9/t7iRk68b JMQswNJL0F7v4zovKnw5/cFVKlRUjPiJ3gSKFzKzphu/N2dHD134Av7tDnS3acXc yHGhKBWgY0yI5HWUslchSrG5xtFQ2RD/SEEUE+T5nWmJBazCHwq15cP6ZgitYXkf paVsGXouXLEOhtj+vhQHOFxibJbIuCtMtH3T4LIKKvgD9x9Qab6/obI9bOckEQGJ ZTTlMa44XPdVOuPed8T4dzJQGSKp2CeNMGYO8t1lyD4laKMx68c= =Wc0b -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/--