The error on semispace.org originates from me having to perform a re-installation due to a server crash. Everything should now be up again, but unfortunately, I have got a new server side ssh key.
If the new key could be used, it would be greatly appreciated. Best regards, Erlend Nossum On 09/22/2010 01:26 AM, [email protected] wrote: > --- Some repositories were not synchronized --- [...] > groupId: org.semispace > Error: > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > Someone could be eavesdropping on you right now (man-in-the-middle attack)! > It is also possible that the RSA host key has just been changed. > The fingerprint for the RSA key sent by the remote host is > b9:58:f2:24:90:6b:a3:13:2e:98:2c:77:4f:82:5e:cd. > Please contact your system administrator. > Add correct host key in /home/maven/.ssh/known_hosts to get rid of this > message. > Offending key in /home/maven/.ssh/known_hosts:77 > RSA host key for semispace.org has changed and you have requested strict > checking. > Host key verification failed. > rsync: connection unexpectedly closed (0 bytes received so far) [receiver] > rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3] > Error synchronizing metadata. Exit code: 255 > Command line executed: /bin/sh -c 'rsync --include=*/ > --include=**/maven-metadata.xml* --exclude=* > --exclude-from=/home/maven/bin/synchronize/syncopate/exclusions.txt -Lrtivz > "--rsh=ssh " [email protected]:/home/maven/repo/org/semispace/ > /home/maven/repository-staging/to-ibiblio/maven2/org/semispace/' > > This is an automated email, do not respond.Contact the owners at > [email protected]
