Greetings Wendy: Thanks for seeing this. I do use a startup script for continuum. It uses the environment from /etc/profile which contains this relevant info:
... JAVA_HOME=/usr/lib/jvm/java-6-sun MAVEN_HOME=/opt/maven PATH=$PATH:$MAVEN_HOME/bin JAVA_OPTS="-Xms256m -Xmx1792m -XX:PermSize=128m -XX:MaxPermSize=512m -Djava.awt.headless=true" export JAVA_HOME JAVA_OPTS MAVEN_HOME ... But I can also use the environment from /etc/profile from the command line before invoking the svn checkout: [EMAIL PROTECTED]:/home/bill# su continuum $ bash [EMAIL PROTECTED]:/home/bill$ . /etc/profile [EMAIL PROTECTED]:/home/bill$ svn list https://localhost/repo/emap branches/ tags/ trunk/ [EMAIL PROTECTED]:/home/bill$ So thats where I get stuck. Does this give you any info more info to look at? Is there any other debug info I could send along? Thanks. Bill. Wendy Smoak-3 wrote: > > On 10/14/07, Bill Brown <[EMAIL PROTECTED]> wrote: > >> This issue still exists for me. I run continuum with the user I created >> "continuum" . I am able to check out code with the continuum user from >> the >> command line. I have already manually accepted the certificate >> verification >> permenantly from the command line as the continuum user. After all of >> this, the build fails with the same error message as the original post. >> Does anyone else have another suggestion? Am I the only user >> experiencing >> this issue? > > It's a legitimate issue, but accepting the certificate should have > fixed it. Most likely, Continuum is not running in exactly the same > environment that you get when you log in. > > How are you starting Continuum? > > -- > Wendy > > -- View this message in context: http://www.nabble.com/The-svn-command-failed-...-Server-certificate-verification-failed%3A-issuer-is-not-trusted-tf4611163.html#a13298429 Sent from the Continuum - Users mailing list archive at Nabble.com.
