Trying to contacting a x86_64 unison from a i686 unison I get a Fatal error Lost connection with the server just after entering the password Reproducible: Always
could you please report this upstream too ?
ho wait, did 2.27.57 work like that ?
(In reply to comment #2) > ho wait, did 2.27.57 work like that ? > The bug is from 2.27.57-r1. I had to go back to 2.27.57 since I had the same error message when trying to synchronize between two 2.27.57-r1 amd64! (I have absolutely no problem with 2.27.57 amd64)
(In reply to comment #3) > (In reply to comment #2) > > ho wait, did 2.27.57 work like that ? > > > > The bug is from 2.27.57-r1. > > I had to go back to 2.27.57 since I had the same error message when trying to > synchronize between two 2.27.57-r1 amd64! > (I have absolutely no problem with 2.27.57 amd64) there is an elog at the end of the merge: * Unison now uses SLOTs, so you can specify servercmd=/usr/bin/unison-2.27 * in your profile files to access exactly this version over ssh. * Or you can use 'eselect unison' to set the version. did you try one of those ? eselect unison will restore the old name
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > ho wait, did 2.27.57 work like that ? > > > > > > > The bug is from 2.27.57-r1. > > > > I had to go back to 2.27.57 since I had the same error message when trying to > > synchronize between two 2.27.57-r1 amd64! > > (I have absolutely no problem with 2.27.57 amd64) > > there is an elog at the end of the merge: > > * Unison now uses SLOTs, so you can specify servercmd=/usr/bin/unison-2.27 > * in your profile files to access exactly this version over ssh. > * Or you can use 'eselect unison' to set the version. > > did you try one of those ? > eselect unison will restore the old name > no answer, setting as worksforme