[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#659903: cannot sync with squeeze (expected "Unison 2.40\n" but received "Unison 2.32\n…")

On Tue, Feb 14, 2012 at 06:41:29PM +0100, Mehdi Dogguy wrote:

> Unison 2.40 is indeed not compatible with former packaged versions in
> Debian. But you can still use binaries built from unison2.32.52 source
> package (which is compatible with Squeeze's unison... they are the same
> in fact) and present in Wheezy.

Oh, dear, so it's in a different package, ok.

Would it make sense for unison to recommend unison2.32.52, so that one
can easily find the version to talk to squeeze?

Otherwise, just file it as PEBKAC on my side, or, well, this can
probably be merged with #659151.

It is quite frustrating to have unison-based procedures breaking at
every unison upgrade. Note that even if I hardcode the version of the
unison executables in my procedures, they would still break:

 1. when things are upgraded on the other side
 2. when I upgrade unison locally, since the upgrade will get rid of the
    version of unison I'm using and won't automatically install the
    compatibility package.

Alternatively, this can be handled with a unison-all package that
depends on all unison versions and I could install in all my machines.
But such a strategy would guarantee that all my procedures will end up,
over time, using the OLDEST available protocol version, even if a newer
one could be found.

I know it's not your fault, of course. Here's a little jar filled with
my tears:


can you please pass it on to upstream?



GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>

Attachment: signature.asc
Description: Digital signature

Reply to: