Return-Path: X-Original-To: apmail-maven-repo-maintainers-archive@minotaur.apache.org Delivered-To: apmail-maven-repo-maintainers-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2757C9817 for ; Wed, 11 Jan 2012 03:35:21 +0000 (UTC) Received: (qmail 82082 invoked by uid 500); 11 Jan 2012 03:35:20 -0000 Delivered-To: apmail-maven-repo-maintainers-archive@maven.apache.org Received: (qmail 82024 invoked by uid 500); 11 Jan 2012 03:35:14 -0000 Mailing-List: contact repo-maintainers-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: repo-maintainers@maven.apache.org Delivered-To: mailing list repo-maintainers@maven.apache.org Delivered-To: moderator for repo-maintainers@maven.apache.org Received: (qmail 22730 invoked by uid 99); 11 Jan 2012 02:12:39 -0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jorlina@sonatype.com designates 64.18.2.173 as permitted sender) MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 10 Jan 2012 21:12:10 -0500 Message-ID: Subject: Re: Unblocking Gmock Maven Rsync From: Joel Orlina To: repo-maintainers@maven.apache.org Content-Type: multipart/alternative; boundary=14dae93407c7cccc9704b637284f --14dae93407c7cccc9704b637284f Content-Type: text/plain; charset=ISO-8859-1 Julien, I've attempted to re-activate the sync, but it currently fails with: protocol version mismatch -- is your shell clean? (see the rsync man page for an explanation) rsync error: protocol incompatibility (code 2) at compat.c(171) [receiver=3.0.6] Are you doing any validation on your end to ensure that only certain rsync/ssh parameters are being allowed from our rsync client? If it helps, I ran a handful of dryrun attempts shortly before sending this e-mail. This should help you track down any potential issues in the logs on your end. Thanks, Joel On Tue, Jan 10, 2012 at 3:07 PM, Julien Gagnet wrote: > Hi, > > I believe that the rsync process with the maven repo has been blocked > due to an old version of rsync running on our server. > > A new server has been now deploy and this should fix the issue. > > The physical host has also changed and you should remove the gmock > entry on your known_hosts file. > > The previous ip of gmock repo was: 91.121.92.74 > The current ip of gmock should be now: 91.121.96.190 > > Thanks in advance for your help. > > Regards, > > Julien > > On 20 December 2011 16:39, Julien Gagnet wrote: > > Hi, > > > > I believe that the rsync process with the maven repo has been blocked > > due to an old version of rsync running on our server. > > > > A new server has been now deploy and this should fix the issue. > > > > The physical host has also changed and you should remove the gmock > > entry on your known_hosts file. > > > > The previous ip of gmock repo was: 91.121.92.74 > > The current ip of gmock should be now: 91.121.96.190 > > > > Thanks in advance for your help. > > > > Regards, > > > > Julien Gagnet > --14dae93407c7cccc9704b637284f--