Good to know, Mathias. Thanks for the follow-up. - Jamis
On Aug 27, 2008, at 10:12 AM, Mathias Meyer wrote:
On Aug 27, 5:22 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote:I'm not sure how anything that's been done in Capistrano could haveresulted in this error suddenly cropping up, since the shadowed- methoderror has existed in cap since 2.0. If anyone wants to track it down and see why this is suddenly an issue, I'd appreciate it.The problem simply seems to be that the ruby-debug-base gem defines a method start in the Kernel module. This will cause the all_methods method in namespaces.rb to find an already defined method called start and therefore cause the aforementioned error. That change in ruby-debug was introduced in release 0.10.1. I have 0.10.0 installed and I haven't seen that error. Cheers, Mathias -- http://paperplanes.de http://twitter.com/roidrage --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
smime.p7s
Description: S/MIME cryptographic signature
