It seems like the root of this problem is usually that people are
setting their :repository to something that is accessible just fine on
the remote hosts, but which cannot be queried directly from the local host.
In other words, something like set(:repository, "/local/path.git").
That local path might exist on the remote host and be accessible just
fine. But Capistrano needs to query that repository to determine what
the current revision is, and of course /local/path.git doesn't exist
locally.
The easiest way to work around this (assuming this is the same problem
you're having) is to declare two repository addresses: one for the
remote host(s), and one for the local host.
set :repository, "/local/path.git"
set :local_repository, "."
Done this way, Capistrano will use your working copy (".") to query the
revision, and "/local/path.git" when it needs to access the repo on the
remote host.
Does that make sense? Does it help you at all?
- Jamis
On 1/21/09 2:43 AM, Andres Rodriguez wrote:
> Hi, I haven't had any luck solving this.
>
> Used this guide (http://capistrano.lighthouseapp.com/projects/8716/
> tickets/56-query_revision-unable-to-resolve-revision-for-head-on-
> repository) to set :branch, "master" and no luck.
>
> Updated to cap 2.5.3, which presumably would fix the bug but nothing.
>
> Any ideas?
>
> FWIW, I'm setting up webistrano to manage different deployments. My
> local webistrano setup goes well and doesn' find any errors. My
> production webistrano setup (Solaris OS) is the one giving me this
> output.
>
> * git version 1.5.6.4
>
> Thanks for any help
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
