cancel
Showing results for 
Search instead for 
Did you mean: 

SVN Repo

derek
Star Contributor
Star Contributor
Hi, All

After some cleanup and shuffling of our code repository, public read-only access to a SVN mirror is now available.  A new checkout of the source code will be required.


svn co svn://www.alfresco.org/alfresco/HEAD/root alfresco
7 REPLIES 7

bkbonner
Champ in-the-making
Champ in-the-making
Derek, thanks this is good news.  Any chance that you can serve it up via http instead of svn?

Thanks

derek
Star Contributor
Star Contributor
The chances are very close to zero.  Sorry.

cmeinck
Champ in-the-making
Champ in-the-making
I installed Subversion 1.3.2, and when I try this command:


svn co svn://www.alfresco.org/alfresco/HEAD/root alfresco

I get the following message:

svn: Can't connect to host 'www.alfresco.org': A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Is this a problem on my end, or is there an issue with the server?

Thanks.

derek
Star Contributor
Star Contributor
Hi,

We had a disruption to SVN yesterday, but it is working for me, now.

Regards

unknown-user
Champ on-the-rise
Champ on-the-rise
Hi,
when i try to connect to the svn i have the foloowing error:

    Berkeley DB error
svn: Berkeley DB error while opening 'transactions' table for filesystem /home/svnadmin/svn/alfresco-open-mirror/db:
Cannot allocate memory
No error
svn: bdb: Lock table is out of available locker entries

i used the url svn://www.alfresco.org/alfresco/HEAD/root alfresco

has someone has the solution ?
thanks

jlbarrera
Champ in-the-making
Champ in-the-making
When i try:

svn co svn://www.alfresco.org/alfresco/HEAD/root alfresco

I get:

svn: Berkeley DB error while opening 'transactions' table for filesystem /home/svnadmin/svn/alfresco-open-mirror/db:
Cannot allocate memory
svn: bdb: Lock table is out of available locker entries

derek
Star Contributor
Star Contributor
We've moved the mirror to port 3696.
And the new mirror is fsfs, so should be much more stable.

Regards