Resurrecting an old thread here, but here's a patch to RubyGems that fixes this issue by following the symlinks:
http://rubyforge.org/tracker/index.php?func=detail&aid=24874&group_id=126&atid=577 On Jan 28, 12:34 pm, Yehuda Katz <[email protected]> wrote: > If you do figure out how to fix it, I'll make sure it gets into the next > release. > -- Yehuda > > > > > > On Tue, Jan 27, 2009 at 10:44 PM, Tony Mann <[email protected]> wrote: > > Ah, the problem is that the directory that exists is a symbolic link, since > > the cap recipe creates a shared/gems/gems link, and mkdir mistakenly thinks > > a file is in the way. I will see what I can do to fix this... > > ..tony.. > > > On Tue, Jan 27, 2009 at 4:38 PM, Tony Mann <[email protected]> wrote: > > >> Hi all. > >> I have finally got bundling working on my local system, but when I try and > >> deploy to a FreeBSD server, I get an error like this: > > >> /usr/local/lib/ruby/1.8/fileutils.rb:243:in `mkdir': File exists - > >> /usr/local/apps/ts2_integration/releases/20090128002647/gems/gems > >> (Errno::EEXIST) > >> from /usr/local/lib/ruby/1.8/fileutils.rb:243:in `fu_mkdir' > >> from /usr/local/lib/ruby/1.8/fileutils.rb:217:in `mkdir_p' > >> from /usr/local/lib/ruby/1.8/fileutils.rb:215:in `reverse_each' > >> from /usr/local/lib/ruby/1.8/fileutils.rb:215:in `mkdir_p' > >> from /usr/local/lib/ruby/1.8/fileutils.rb:201:in `each' > >> from /usr/local/lib/ruby/1.8/fileutils.rb:201:in `mkdir_p' > >> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/installer.rb:210:in > >> `install' > >> from > >> /usr/local/apps/ts2_integration/releases/20090128002647/tasks/merb.thor/mai > >> n.thor:63:in > >> `redeploy' > >> ... 9 levels... > >> from /usr/local/lib/ruby/gems/1.8/gems/thor-0.9.9/lib/thor.rb:78:in > >> `start' > >> from /usr/local/lib/ruby/gems/1.8/gems/thor-0.9.9/bin/thor:7 > >> from bin/thor:31:in `load' > >> from bin/thor:31 > > >> Basically, under this OS the call to mkdir is failing if the directory > >> exists. This happens under sudo as well, so this is not a permissions > >> issue. > >> I tried patching the gems installer, but it was not working out well and I > >> do not want to break normal gem installation. On that point, since normal > >> gem installation is working fine, I have to wonder why it is breaking in > >> this case. > > >> Anyone else run into this? Or have a clever way around the issue? > > >> ..tony.. > > -- > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
