Hi Jones,

svn write-access should work again...

Cheers,
Norman

2009/2/17 Norman Maurer <[email protected]>:
> Hi Jonas,
>
> svn.apache.org is up again (read-only).
>
> Bye,
> Norman
>
> 2009/2/17 Jonas Arnsmann <[email protected]>:
>> Hi Norman,
>>
>> Ok. I only need read access..
>> 3 Hours is a reasonable timeframe.. :)
>>
>> Cheers,
>> Jonas
>>
>> Norman Maurer schrieb:
>>>
>>> Hi Jonas,
>>>
>>> svn.apache.org should be up (read-only) in about 3 hours. Enabling
>>> write access will prolly take some more time thought...
>>>
>>> Cheers,
>>> Norman
>>>
>>> 2009/2/17 Jonas Arnsmann <[email protected]>:
>>>>
>>>> Hi Norman,
>>>>
>>>> Thanks for the update..
>>>> Are there any time estimates?
>>>>
>>>> svn.eu.apache.org does not seem to contain the resources needed by the
>>>> James Maven Build, so this is not an option. This option would also
>>>> require
>>>> to manually edit all pom.xml's in trunk, right?
>>>>
>>>> Bye,
>>>> Joans
>>>>
>>>> Norman Maurer schrieb:
>>>>>
>>>>> Hi Jones,
>>>>>
>>>>> svn.apache.org lost a disk. It's currently resync the zfs array. It
>>>>> will be up again after the resync completes. You could use
>>>>> svn.eu.apache.org in the meantime ( read-only ).
>>>>>
>>>>> Bye,
>>>>> Norman
>>>>>
>>>>>
>>>>> 2009/2/17 Jonas Arnsmann <[email protected]>:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Seems like http://svn.apache.org/repos/asf/james/server/ is down since
>>>>>> yesterday night.
>>>>>> Are there any estimates, when the SVN will be up and running again?
>>>>>> Maven2 Builds of the current trunk are failing, because external
>>>>>> resources
>>>>>> hosted on svn.apache.org and people.apache.org are not available.
>>>>>>
>>>>>> Greetings from Germany,
>>>>>> Jonas Arnsmann
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to