Actually the bugs aren't really duplicates. The issue in the
description of this bug has been fixed. It has not for #229603.
Unmarked the duplication and re-closed this bug.
** Changed in: unison (Ubuntu)
Status: New => Invalid
--
7.10 and 8.04 incompatible
https://bugs.launchpad.net/b
Hello Piotr
Piotr Sniady <[EMAIL PROTECTED]> wrote:
> Current solution (disabling backorts, etc) is just a workaround; the
> true solution upstream should be to make unison backward compatible,
> also in the future.
Yes that must be the solution if a newer protocol is inserted in
unison. We need
As a submitter of the bug #229603 (which is the duplicate of this bug) I
do not think that these two bugs can be classified now as invalid.
Current solution (disabling backorts, etc) is just a workaround; the
true solution upstream should be to make unison backward compatible,
also in the future.
** Changed in: unison (Ubuntu)
Status: New => Invalid
--
7.10 and 8.04 incompatible
https://bugs.launchpad.net/bugs/229232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Hello Dave
thanks that was the problem. I set unison to "hold" now and have
deacticated the backports. This report can be closed.
Bye
Eric
--
7.10 and 8.04 incompatible
https://bugs.launchpad.net/bugs/229232
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hi,
Unison is at version 2.13.16 in all Ubuntu releases back to dapper (see
http://packages.ubuntu.com/unison). Except intrepid and hardy-
backports.
I'm guessing you have hardy-backports enabled on your 8.04 amd64
machine. If so then:
- disable that repository
- run 'apt-get update'
- run 'ap
