I think that sounds right... here's the full error I was seeing:
===============
* getting (via export) revision 142 to /tmp/20080601013153
executing locally: svn export -q -r142
file:///home/tom/svn/trunk/gforge_sites /tmp/20080601013153
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///home/tom/svn/trunk/gforge_sites'
===============
So yup, like you said, the copy strategy was using the :repository
rather than the :local_repository.
I guess what I was thinking was that using repository and
local_repository together was meant for situations where you were
deploying to the same machine that the svn repo was on. So doing a
"deploy_via :copy" might not make much sense in that case since the
whole "tar, sftp, untar" step that a deploy_via :copy entails wouldn't
be necessary. Just check out in the revisions/ directory and have done
with it.
Yours,
tom
On Sat, 2008-05-24 at 22:34 -0600, Jamis Buck wrote:
> I'm probably just overtired, but I'm not understanding why the copy
> strategy fails when local_repository is set? Is it because the
> strategy isn't doing source.local.xyz? If so, maybe we should consider
> patching the strategies to use source.local, since source.local just
> falls back to the normal repository if a local repo hasn't been
> specified.
>
> - Jamis
>
> On May 21, 2008, at 6:02 PM, Tom Copeland wrote:
>
> >
> > Hi all -
> >
> > I posted on my new bee struggles with local_repository and deploy_via
> > copy today:
> >
> > http://tomcopeland.blogs.com/juniordeveloper/2008/05/capistrano-loca.html
> >
> > Here's an ugly patch, but you get the idea:
> >
> > ==================================
> > $ diff -Naur base.rb base.new.rb
> > --- base.rb 2008-05-21 19:50:07.000000000 -0400
> > +++ base.new.rb 2008-05-21 19:49:59.000000000 -0400
> > @@ -43,6 +43,7 @@
> > # Creates a new SCM instance with the given configuration
> > options.
> > def initialize(configuration={})
> > @configuration = configuration
> > + logger.info "WARNING: You probably don't want to use
> > 'set :deploy_via, :copy' and a :local_repository together; remove
> > 'set :deploy_via, :copy and things will probably work as expected" if
> > @configuration.variables[:deploy_via] == :copy &&
> > @configuration.variables[:local_repository]
> > end
> >
> > # Returns a proxy that wraps the SCM instance and forces it to
> > operate
> > ==================================
> >
> > Maybe there's a scenario when you'd want to have both those variables
> > set? I noodled for a bit but couldn't think of one...
> >
> > Yours,
> >
> > Tom
> >
> >
> >
> > > >
>
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
