Yeah, was a false positive. Thanks, tho...
On May 7, 6:50 pm, Jamis Buck [EMAIL PROTECTED] wrote:
Hmm. You shouldn't need capistrano on any server but the one you are
deploying from. I'm not sure installing it on the remote server(s)
would have any effect at all...
- Jamis
On May 7,
Hi, Folks.
Actually, chalk this up to my own stupidity. I hadn't upgraded
capistrano on the production server. I did that and everything is
working for me.
Ben
On May 6, 7:29 am, zmalltalker [EMAIL PROTECTED] wrote:
The small patch
execute #{git} fetch #{remote} #{git} fetch
OK, take it back. That wasn't it.
On May 7, 6:32 pm, BenHill [EMAIL PROTECTED] wrote:
Hi, Folks.
Actually, chalk this up to my own stupidity. I hadn't upgraded
capistrano on the production server. I did that and everything is
working for me.
Ben
On May 6, 7:29 am, zmalltalker [EMAIL
Hmm. You shouldn't need capistrano on any server but the one you are
deploying from. I'm not sure installing it on the remote server(s)
would have any effect at all...
- Jamis
On May 7, 2008, at 7:32 PM, BenHill wrote:
Hi, Folks.
Actually, chalk this up to my own stupidity. I hadn't
Actually I think this is related to git fetch --tags being used now
which apparently *only* fetches tags as opposed to fetching all commit
objects in addition to tags when a successive deploy is made.
Here's what's happening on my server:
if [ -d /APPROOT/shared/cached-copy ]; then
cd
Hi Jamis,
basically you'd just need to reverse the patch in ticket #6, should I
just reopen that one and attach a note?
Best,
Patrick
On May 6, 2008, at 3:09 PM, Jamis Buck wrote:
Fair enough. I'm still new to git (and haven't needed to use git with
capistrano yet), so I'll rely on the
I added a note to ticket, waiting for reply from Alex
On Tue, May 6, 2008 at 3:22 PM, Patrick Lenz [EMAIL PROTECTED]
wrote:
Hi Jamis,
basically you'd just need to reverse the patch in ticket #6, should I
just reopen that one and attach a note?
Best,
Patrick
On May 6, 2008, at 3:09 PM,
The small patch
execute #{git} fetch #{remote} #{git} fetch --tags
#{remote} #{git} reset --hard #{revision}
worked like a charm for me, +1.
Marius
On May 6, 3:36 pm, Mislav Marohnić [EMAIL PROTECTED]
wrote:
I added a note to ticket, waiting for reply from Alex
On Tue, May 6,
Can you observe the output and find the git command that triggered this
error?
There is probably a problem with query_revision, but the error itself didn't
come from Capistrano.
On Mon, May 5, 2008 at 1:33 AM, BenHill [EMAIL PROTECTED] wrote:
After deploying 2.3, I suddenly get this error
