unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Eric Bavier <bavier@member.fsf.org>, 30448@debbugs.gnu.org
Subject: [bug#30448] Breaking rdiff-backup and btar (was Re: [bug#30448] Update librsync to 2.0.1)
Date: Tue, 24 Apr 2018 13:57:15 -0400	[thread overview]
Message-ID: <20180424175715.GA14535@jasmine.lan> (raw)
In-Reply-To: <87k1sy2i6u.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

On Mon, Apr 23, 2018 at 02:58:17PM +0200, Ludovic Courtès wrote:
> ludo@gnu.org (Ludovic Courtès) skribis:
> 
> > Leo Famulari <leo@famulari.name> skribis:
> >
> >> Is anyone using one of the dependent packages interested in looking more
> >> closely at this?
> >
> > I’m not using it, but at first sight the patch LGTM.
> 
> 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 — 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...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-04-24 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 19:01 [bug#30448] Update librsync to 2.0.1 Leo Famulari
2018-02-15 14:27 ` Ludovic Courtès
2018-04-23 12:58   ` Ludovic Courtès
2018-04-24 17:57     ` Leo Famulari [this message]
2018-04-24 20:30       ` [bug#30448] Breaking rdiff-backup and btar (was Re: [bug#30448] Update librsync to 2.0.1) Ludovic Courtès
2018-04-25 17:23         ` Leo Famulari
2018-04-28 16:48           ` Oleg Pykhalov
2019-02-13  0:00           ` bug#30448: " Leo Famulari
2019-02-13 21:30           ` [bug#30448] Update librsync to 2.0.1 Leo Famulari
2019-02-25 23:24             ` bug#30448: " Leo Famulari
2019-02-13 21:26 ` [bug#30448] [PATCH] gnu: librsync: Update to 2.0.2 Leo Famulari

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=20180424175715.GA14535@jasmine.lan \
    --to=leo@famulari.name \
    --cc=30448@debbugs.gnu.org \
    --cc=bavier@member.fsf.org \
    --cc=ludo@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).