Re: Bug#807019: tracking bin-num - broken unison due to binnmu upload
Alexander Wirt <firstname.lastname@example.org> writes:
>> This should be integrated in the backports.d.o repositories.
> Backports is not for fixing bugs in stable.
I think there is a misunderstanding here.
This is not about fixing unison in stable. "unison" 2.40.102-2 in stable
works fine. It is not broken. There is nothing to fix. It works fine
when talking to other stable servers.
The package called "unison2.40.102" version 2.40.102-3+b1 in testing and
unstable is broken. This broken package is not in stable. If it can't
get fixed, it probably should get removed.
The most recent "unison" package, version 2.48.3-1 in testing and
unstable is not broken. Unfortunately it is not compatable with the
version in stable.
This is about letting stable users use the latest bleeding each version
so that they can have compatability with unison 2.48 in unstable which
is not broken. Which I believe is inline with what backports is for.
Brian May <email@example.com>