SVN problem

Discussion on computers, ROMS installation and compiling

Moderators: arango, robertson

Post Reply
Message
Author
surja
Posts: 12
Joined: Thu Jan 12, 2012 5:19 pm
Location: Jadavpur university,INCOIS

SVN problem

#1 Post by surja » Thu May 31, 2012 8:31 am

Dear all,
I use the svn command line in my laptop which is linux environment.My username is surja.I login roms home page ( https://www.myroms.org)using this username and password.But when I am trying to download the roms giving following commend

svn checkout --username surja https://www.myroms.org/svn/src/trunk MyDir

svn: OPTIONS of 'https://www.myroms.org/svn/src/trunk': Could not resolve hostname `www.myroms.org': Host not found (https://www.myroms.org

please help me.

User avatar
robertson
Site Admin
Posts: 124
Joined: Wed Feb 26, 2003 3:12 pm
Location: IMCS, Rutgers University

Re: SVN problem

#2 Post by robertson » Fri Jun 01, 2012 2:30 am

Are you sure that the computer you are running svn on has access to the internet? Some clusters and computer centers don't allow their high performance computers access to the internet for security and performance reasons.

surja
Posts: 12
Joined: Thu Jan 12, 2012 5:19 pm
Location: Jadavpur university,INCOIS

Re: SVN problem

#3 Post by surja » Fri Jun 01, 2012 2:12 pm

Thank you sir.The problem occurred from internet server.

pmaccc
Posts: 39
Joined: Wed Oct 22, 2003 6:59 pm
Location: U. Wash., USA

Re: SVN problem

#4 Post by pmaccc » Thu Jun 07, 2012 8:59 pm

I am trying to get the latest ROMS using svn onto a linux machine. This has worked many times in the past but today it chokes halfway through with the error message:

svn: Can't read file 'ROMS_620/Lib/ARPACK/LAPACK/.svn/log': Permission denied

A possible clue is that today for the first time I got the following query at the start of the svn download:
-----------------------------------------------------------------------
ATTENTION! Your password for authentication realm:

<https://www.myroms.org:443> Subversion Repository

can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.

You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/home/parker/.subversion/servers'.
-----------------------------------------------------------------------
Store password unencrypted (yes/no)?

and it only seemed interested in getting "no" for an answer.

User avatar
robertson
Site Admin
Posts: 124
Joined: Wed Feb 26, 2003 3:12 pm
Location: IMCS, Rutgers University

Re: SVN problem

#5 Post by robertson » Thu Jun 14, 2012 2:01 pm

The two issues should not have anything to do with each other.
svn: Can't read file 'ROMS_620/Lib/ARPACK/LAPACK/.svn/log': Permission denied
Appears to be a file permission error. Check the permissions on that file and make sure your user and/or group have write permissions on that file. Perhaps some files in your ARPACK directory were edited or compiled by another username. Another less likely possibility is that your file handle limit was reached. Typically you would get a "Too many open files" error but it can manifest in other ways.
-----------------------------------------------------------------------
ATTENTION! Your password for authentication realm:

<https://www.myroms.org:443> Subversion Repository

can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.

You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/home/parker/.subversion/servers'.
-----------------------------------------------------------------------
Store password unencrypted (yes/no)?
is likely due to new security measures in the 1.6.x versions of the Subversion client. Have you ever successfully checkout/updated the ROMS code from this Linux machine before? If so did you recently update or reconfigure Subversion? To check what version of subversion you are running type:

Code: Select all

svn --version

Post Reply