Is there a /usr/local/bin/ruby? Is /usr/local/bin ahead of /usr/bin in  
your path? What happens if you remove the /usr/bin/ruby symlink?

- Jamis

On Jun 23, 2008, at 12:38 PM, sean wrote:

>
> Hi Jamis,
>
> Well, I really wouldn't know where to begin in terms of digging
> through the code. One thing I noticed, though (not sure if this is
> relevant) is that on my system, there is a symbolic link at /usr/lib/
> ruby which points to /System/Library/Frameworks/Ruby.framework/
> Versions/Current/usr/lib/ruby
> in which I find a gems directory which has some gems, but not the
> capistrano gem. Additionally there is a gems directory in the path /
> usr/local/lib/ruby/gems/1.8/gems which has the capistrano and other up
> to date gems. I wonder if some part of capistrano is using the wrong
> gem path?
>
> Take care,
> Sean
>
>
> On Jun 23, 2:18 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>> I'm sorry all, but I'm at a loss here. I can't duplicate it (using OS
>> X 10.5, Ruby 1.6, Cap 2.4, gems 1.2, etc.). If you are having this
>> problem, I'm afraid I'm going to have to call on you to dig into the
>> code and see what's going on. That, or help me to duplicate the
>> problem so I can investigate. :(
>>
>> - Jamis
>>
>> On Jun 23, 2008, at 12:14 PM, sean wrote:
>>
>>
>>
>>> Hi Jamis et al,
>>
>>> I am running capistrano 2.4 on os x 10.5, and I have having the same
>>> problem:
>>
>>> cap deploy:check
>>>  * executing `deploy:check'
>>> could not find any strategy named `checkout'
>>
>>> That is after commenting out the line:  
>>> set :deploy_via, :remote_cache
>>
>>> When that line is left in I get:
>>>  * executing `deploy:check'
>>> could not find any strategy named `remote_cache'
>>
>>> I haven't had any problems with other gems, so I don't think the
>>> problem is with my load path. cap -V returns Capistrano v2.4.0
>>
>>> I am having this problem both with a new rais app that uses a git
>>> repository and my old rails apps that use subversion.
>>
>>> thanks in advance for any ideas,
>>> Sean
>>
>>> On Jun 23, 12:33 pm, "[EMAIL PROTECTED]"
>>> <[EMAIL PROTECTED]> wrote:
>>>> not sure this is going to help much but see below
>>
>>>> thanks
>>>> Nick
>>
>>>> On Jun 23, 5:21 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:> Do you
>>>> have a .caprc file in your home directory?
>>
>>>> No
>>
>>>>> What does your
>>>>> Capfile look like?
>>
>>>> http://pastie.org/220451
>>
>>>>> Do you have any plugins in vendor/plugins that have
>>>>> cap recipes?
>>
>>>> The only plugins installed are:
>>>> [EMAIL PROTECTED]:~/git/nyvej-accreditation (master)$ ls -l vendor/
>>>> plugins/
>>>> total 24
>>>> drwxr-xr-x  4 nick nick 4096 2008-06-21 17:07 acts_as_state_machine
>>>> drwxr-xr-x  8 nick nick 4096 2008-06-21 17:07 exception_logger
>>>> drwxr-xr-x  4 nick nick 4096 2008-06-21 17:07 manage_fixtures
>>>> drwxr-xr-x  4 nick nick 4096 2008-06-21 17:07 restful- 
>>>> authentication
>>>> drwxr-xr-x 13 nick nick 4096 2008-06-21 17:07 rspec
>>>> drwxr-xr-x  8 nick nick 4096 2008-06-21 17:07 rspec_on_rails
>>
>>>>> I'm just wondering if there is something, somewhere, that is  
>>>>> mucking
>>>>> with your load path. Try adding this to the bottom of both your
>>>>> deploy.rb and deploy/staging.rb files:
>>
>>>>>    puts(__FILE__, load_paths.join(":"))
>>
>>>>> The load paths that are printed should be (by default) "." and the
>>>>> path to the "recipes" subdirectory in your capistrano installation
>>>>> (/
>>>>> path/to/gems/capistrano-2.4.0/lib/capistrano/recipes).
>>
>>>> I get:http://pastie.org/220453
>>>> all the paths look correct to me
>>
>>>>> - Jamis
>>
>>>>> On Jun 23, 2008, at 10:10 AM, [EMAIL PROTECTED] wrote:
>>
>>>>>> [EMAIL PROTECTED]:~$ ls -l /usr/lib/ruby/gems/1.8/gems/
>>>>>> capistrano-2.4.0/
>>>>>> lib/capistrano/recipes/deploy/strategy
>>>>>> total 32
>>>>>> -rw-r--r-- 1 root root 2562 2008-06-23 14:36 base.rb
>>>>>> -rw-r--r-- 1 root root  533 2008-06-23 14:36 checkout.rb
>>>>>> -rw-r--r-- 1 root root 8417 2008-06-23 14:36 copy.rb
>>>>>> -rw-r--r-- 1 root root  469 2008-06-23 14:36 export.rb
>>>>>> -rw-r--r-- 1 root root 1488 2008-06-23 14:36 remote_cache.rb
>>>>>> -rw-r--r-- 1 root root 1735 2008-06-23 14:36 remote.rb
>>
>>>>>> I've tried uninstalling all the gems relating to capistrano but
>>>>>> this
>>>>>> did not help either.  I also tried running capistrano 2.3.0
>>>>>> (which it
>>>>>> was working for previously) but that did not help
>>
>>>>>> Thanks
>>>>>> Nick
>>
>>>>>> On Jun 23, 4:54 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>>>>>>> I don't think it is related to rubygems, since I just tried
>>>>>>> uninstalling capistrano and reinstalling (using rubygems 1.2.0)
>>>>>>> and I
>>>>>>> can find the remote_cache strategy just fine. What does the lib/
>>>>>>> capistrano/recipes/deploy/strategy directory look like in your
>>>>>>> capistrano installation? Is there a remote_cache.rb file?
>>
>>>>>>> - Jamis
>>
>>>>>>> On Jun 23, 2008, at 9:38 AM, [EMAIL PROTECTED] wrote:
>>
>>>>>>>> I did a fresh install of Ubuntu 8.04 at the weekend
>>
>>>>>>>> ruby 1.8.6 (2007-09-24 patchlevel 111) [i486-linux]
>>
>>>>>>>> I wonder if it has anything to do with the new version of
>>>>>>>> rubygems?
>>
>>>>>>>> thanks
>>>>>>>> Nick
>>
>>>>>>>> On Jun 23, 4:06 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>>>>>>>>> Very odd. :( I can't duplicate this at all. What version of  
>>>>>>>>> Ruby
>>>>>>>>> are
>>>>>>>>> you using? And what OS?
>>
>>>>>>>>> - Jamis
>>
>>>>>>>>> On Jun 23, 2008, at 8:53 AM, [EMAIL PROTECTED]  
>>>>>>>>> wrote:
>>
>>>>>>>>>> Hi,
>>
>>>>>>>>>> I'm getting a similar problem with my deploy:
>>>>>>>>>> could not find any strategy named `remote_cache'
>>
>>>>>>>>>> capistrano (2.4.0)
>>>>>>>>>> capistrano-ext (1.2.1)
>>>>>>>>>> gem 1.2.0
>>
>>>>>>>>>> deploy.rb:http://pastie.org/220387
>>>>>>>>>> deploy/staging.rb:http://pastie.org/220389
>>
>>>>>>>>>> I've tried uninstalling and reinstalling capistrano but no  
>>>>>>>>>> luck
>>
>>>>>>>>>> Any ideas?
>>>>>>>>>> Thanks
>>>>>>>>>> Nick
>>
>>>>>>>>>> On Jun 23, 2:29 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>>>>>>>>>>> Sounds like maybe you've got a botched install of  
>>>>>>>>>>> capistrano.
>>>>>>>>>>> Does
>>>>>>>>>>> the
>>>>>>>>>>> file lib/capistrano/recipes/deploy/strategy/checkout.rb
>>>>>>>>>>> exist in
>>>>>>>>>>> your
>>>>>>>>>>> capistrano installation? What version of rubygems do you  
>>>>>>>>>>> have
>>>>>>>>>>> installed?
>>
>>>>>>>>>>> If nothing else, you might want to "gem uninstall" all
>>>>>>>>>>> versions
>>>>>>>>>>> of
>>>>>>>>>>> capistrano that you've got installed, and then "gem install
>>>>>>>>>>> capistrano" and see if that works any better.
>>
>>>>>>>>>>> - Jamis
>>
>>>>>>>>>>> On Jun 22, 2008, at 11:43 PM, Parker McGee wrote:
>>
>>>>>>>>>>>> Whenever I try to deploy using Capistrano 2.4.0, I get the
>>>>>>>>>>>> following
>>>>>>>>>>>> output:
>>
>>>>>>>>>>>> $ cap deploy
>>>>>>>>>>>>  * executing `deploy'
>>>>>>>>>>>>  * executing `deploy:update'
>>>>>>>>>>>> ** transaction: start
>>>>>>>>>>>>  * executing `deploy:update_code'
>>>>>>>>>>>> *** [deploy:update_code] rolling back
>>>>>>>>>>>>  * executing "rm -rf /home/pmcgee/homeless-shelter/ 
>>>>>>>>>>>> releases/
>>>>>>>>>>>> 20080623053142; true"
>>>>>>>>>>>>    servers: ["twistingmaze.com"]
>>>>>>>>>>>> Password:
>>>>>>>>>>>>    [twistingmaze.com] executing command
>>>>>>>>>>>>    command finished
>>>>>>>>>>>> could not find any strategy named `checkout'
>>
>>>>>>>>>>>> On deploy:check, I get the same error:
>>
>>>>>>>>>>>> $ cap -q deploy:check
>>>>>>>>>>>> could not find any strategy named `checkout'
>>
>>>>>>>>>>>> My deploy.rb file is available here:http://pastie.org/ 
>>>>>>>>>>>> 220188
>>
>>>>>>>>>>>> I've never had this problem before, though I did just
>>>>>>>>>>>> upgrade to
>>>>>>>>>>>> 2.4.0.  I can't see anywhere where I'm trying to call a
>>>>>>>>>>>> 'checkout'
>>>>>>>>>>>> strategy.  Could someone please help?  Thanks!
>>
>>>>>>>>>>>> Parker McGee
> >


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to