On Wed, May 28, 2008 at 1:45 AM, Liam Morley <[EMAIL PROTECTED]> wrote:
> I do have a cygwin copy of svn and cygwin is in my path, so after executing > 'svn co' on the cmd line, I can successfully add the key permanently, but I > don't think that setting makes it outside of cygwin. There is a native Windows port of SVN. Native Windows ports generally do better than Cygwin ports. > After I accept permanently from the cmd line, I'm still presented with only > 'reject or accept temporarily' from Capistrano. Question: What are you deploying to? The "reject or accept temporarily" from Capistrano is very likely happening on the server side. I'll bet money you're deploying from Windows, to some Unix. If that's the case, ssh in and run a manual checkout there, ten accept that permanently. > > The interesting thing is, I tried checking out from TortoiseSVN in a new > directory, and it didn't even prompt me to accept at all, it just checked > everything out. Just for full disclosure, my ordinary everyday svn client is > Subclipse (plugin for Eclipse, I'm a RadRails user), which had prompted me > earlier, and did offer the "accept permanently" option. > > Liam > > > > On Wed, May 28, 2008 at 2:22 AM, Ezra Zygmuntowicz <[EMAIL PROTECTED]> > wrote: > >> >> Hey~ >> >> On May 27, 2008, at 11:16 PM, Liam Morley wrote: >> > >> > I'm guessing that our sys admin is just using a bum certificate or >> > something, but in any case, when I try to use our svn repo which is on >> > a secure server, i get the following: >> > >> > [err] Error validating server certificate for 'https://blah:443': >> > - The certificate is not issued by a trusted authority. Use the >> > fingerprint to validate the certificate manually! >> > ... >> > (R)eject or accept (t)emporarily? >> > >> > >> > In all of my googling, I always see something like "(R)eject, accept >> > (t)emporarily or accept (p)ermanently?" I'd really like to accept >> > permanently, but cap won't let me. :( And to make matters worse, both >> > Firefox and my SVN client will accept the cert permanently, so I have >> > a hard time going to my sys admin and telling him to fix the cert. Is >> > there anything I can do with capistrano (or maybe Net::SSH?) to >> > somehow permanently accept the cert? Thanks all. >> >> >> >> Liam- >> >> The way to get around this is to do a fresh svn checkout of the >> repo >> in question and permanently accept it on the command line. once you do >> this the next time you run cap tasks it will not prompt you anymore. >> >> $ cd ~ >> $ svn co <your repo url here> >> # permanently accept cert >> $ cd ~/railsapp >> $ cap deploy >> >> >> Cheers- >> >> - Ezra Zygmuntowicz >> -- Founder & Software Architect >> -- [EMAIL PROTECTED] >> -- EngineYard.com >> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
