maven-repo-maintainers mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Sanchez" <car...@apache.org>
Subject Permanent errors in Maven repo sync [Was: [Maven Central Repository Synchronization] FAILURE]
Date Mon, 08 Sep 2008 12:13:59 GMT
mysql and com.exadel.flamingo syncs have been removed due to permanent failure.

Christian:
You can filter the messages that don't have you as part of the To:
field, if your repo fails you'll get direct email, given that it is
listed in https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv

The sync happens every 4 hours, not hourly

groupId:null is a special case for the codehaus repo, could probably
be more explanatory, but wold require some fixes to the scripts that I
don't have the time right now to do.

Thanks


On Mon, Sep 8, 2008 at 1:58 PM, Christian Schulte <cs@schulte.it> wrote:
> maven@repo1.maven.org wrote:
>>
>> --- Some repositories were not synchronized ---
>> groupId: null
>> Error:
>> 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 -i $HOME/.ssh/new-id_dsa"
>> mavensync@repository.codehaus.org:/repository/
>> /home/maven/repository-staging/to-ibiblio/maven2/'org.codehaus.plexus.util.cli.CommandLineException:
>> Error while executing external command, process killed.Error while executing
>> external command, process killed.Process timeout out after 600 seconds
>>
>> groupId: com.exadel.flamingo
>> Error:
>> ssh: connect to host build.exadel.com port 22: Connection timed out
>> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
>> rsync error: error in rsync protocol data stream (code 12) at io.c(635)
>> [receiver=3.0.3]
>> Error synchronizing metadata. Exit code: 12
>>
>> groupId: mysql
>> Error:
>>
>> insecure -e option not allowed.
>> This account is restricted by rssh.
>> Allowed commands: rsync
>>
>> If you believe this is in error, please contact your system administrator.
>>
>> rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
>> rsync error: error in rsync protocol data stream (code 12) at io.c(635)
>> [receiver=3.0.3]
>> Error synchronizing metadata. Exit code: 12
>>
>> This is an automated email, do not respond.Contact the owners at
>> repo-maintainers@maven.apache.org
>
> Since nobody seems to react upon these emails, wouldn't it be possible to
> automatically stop synchronizing a group which failed for e.g. 3 days (or
> whatever number fits) ? Synchronizing on a daily basis (or every 4, 8, 12,
> whatever hours) could also reduce all these mails dramatically. What's the
> reason for needing to synchronize on an hourly basis ? Its just that I
> receive an email every hour which makes the MUA beep which in turn makes me
> switch to the MUA to look for the arrived mail. Filtering such mails to be
> put into a different folder does not stop the MUA from beeping :-) That
> holds true also for success mails. Unsubscribing from the list would indeed
> stop that from happening. Maybe that's what these guys already did ?
>
> Btw,
>
> groupId: null
>
> could be a bug. That would mean even the maintainer responsible for the
> synchronization does not pay attention to all these mails.
>
> Not to be misunderstood: If things can't be changed the way they are, I
> simply create a new email account solely for the repo-maintainers list.
> Wanted to ask here first, to not need to create that new account and make
> someone change the email address in the synchronization script.
>
> --
> Christian
>
>

Mime
View raw message