--- Some repositories were not synchronized ---
groupId: com.pyx4j
Error:
rsync: failed to connect to pyx4me.com: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(122) 
[receiver=3.0.3]
Error synchronizing metadata. Exit code: 10

groupId: com.pyx4me
Error:
rsync: failed to connect to pyx4me.com: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(122) 
[receiver=3.0.3]
Error synchronizing metadata. Exit code: 10

groupId: net.fckeditor
Error:
rsync: failed to connect to java.fckeditor.net: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(122) 
[receiver=3.0.3]
Error synchronizing metadata. Exit code: 10

groupId: net.sf.bluecove
Error:
rsync: failed to connect to pyx4me.com: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(122) 
[receiver=3.0.3]
Error synchronizing metadata. Exit code: 10

groupId: net.sf.jour
Error:
rsync: failed to connect to pyx4me.com: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(122) 
[receiver=3.0.3]
Error synchronizing metadata. Exit code: 10

groupId: org.amplecode
Error:
bash: rsync: command not found
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: remote command not found (code 127) at io.c(635) [receiver=3.0.3]
Error synchronizing metadata. Exit code: 127

groupId: org.microemu
Error:
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(794) 
[receiver=3.0.3]
Error synchronizing metadata. Exit code: 12

groupId: org.puremvc
Error:
Command line executed: /bin/sh -c "svn update 
/home/maven/repository-staging/to-ibiblio/maven-svn/org/puremvc/"org.codehaus.plexus.util.cli.CommandLineException:
 Error while executing external command, process killed.Error while executing 
external command, process killed.Process timeout out after 900 seconds

This is an automated email, do not respond.Contact the owners at 
[email protected]

Reply via email to