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

Re: Bug#807019: tracking bin-num - broken unison due to binnmu upload

On 2016-01-03 16:54:40 +1100, Brian May wrote:
> 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.

Yes, I think that it should be removed ASAP. Thus, users of
testing/unstable could still use unison2.40.102 from stable
(hoping there won't be any conflict in the near future) so
that they would be able to sync with stable machines without
requiring a backport of unison 2.48 in stable.

This is what I currently do, but since the broken unison2.40.102
is still in testing/unstable, I had to downgrade then mark it as
frozen in aptitude, so that the stable version is not replaced by
the testing/unstable version.

Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Reply to: