Hey Bob, On Mon, Dec 17, 2012 at 04:01:00PM -0700, Bob Proulx wrote: > Antonio Terceiro wrote: > > Wheezy (and Rails 3) porting is just starting, so I don't know yet how > > exactly that is going to be. > > Speaking of which there are currently some problems as things sit > today. It isn't happy. In a pristine system (chroot, vm, etc.) in > Wheezy as of 2012-12-17 (ruby 4.9, ruby1.9.1 1.9.3.194-5, rails3 > 3.2.6-1): > > Install ruby and rails3: > > # apt-get install ruby rails3 > > Ruby and Rails 3 are both installed. Test them by creating a new project: > > $ rails new test1 > ... > run bundle install --local > /usr/lib/ruby/1.9.1/fileutils.rb:247:in `mkdir': Permission denied - /var/lib/gems/1.9.1 (Errno::EACCES) > from /usr/lib/ruby/1.9.1/fileutils.rb:247:in `fu_mkdir' > from /usr/lib/ruby/1.9.1/fileutils.rb:221:in `block (2 levels) in mkdir_p' > from /usr/lib/ruby/1.9.1/fileutils.rb:219:in `reverse_each' > from /usr/lib/ruby/1.9.1/fileutils.rb:219:in `block in mkdir_p' > from /usr/lib/ruby/1.9.1/fileutils.rb:205:in `each' > from /usr/lib/ruby/1.9.1/fileutils.rb:205:in `mkdir_p' > from /usr/lib/ruby/1.9.1/pathname.rb:514:in `mkpath' > from /usr/lib/ruby/vendor_ruby/bundler/installer.rb:19:in `run' > from /usr/lib/ruby/vendor_ruby/bundler/installer.rb:12:in `install' > from /usr/lib/ruby/vendor_ruby/bundler/cli.rb:220:in `install' > from /usr/lib/ruby/vendor_ruby/bundler/vendor/thor/task.rb:22:in `run' > from /usr/lib/ruby/vendor_ruby/bundler/vendor/thor/invocation.rb:118:in `invoke_task' > from /usr/lib/ruby/vendor_ruby/bundler/vendor/thor.rb:263:in `dispatch' > from /usr/lib/ruby/vendor_ruby/bundler/vendor/thor/base.rb:386:in `start' > from /usr/bin/bundle:13:in `<main>' > Unfortunately, a fatal error has occurred. Please see the Bundler > troubleshooting documentation at http://bit.ly/bundler-issues. Thanks! > > Obviously the attempt to make a directory down /var/lib isn't > intended. I just tried this on a clean sid chroot, and the only way I could reproduce this problem was by manually removing /var/lib/gems/1.9.1 as root. Did you by any chance do that? > I have reviewed the wiki page tracking this: > > http://wiki.debian.org/Teams/Ruby/Rails3 > > I can see that the checklist and plan isn't complete yet. That is > understandable. But it is also severely limited in use at the > moment. The problem is that I am not sure how I can help. There is a > pretty steep learning curve to dig into gems and bundler and try to > work around it. Actually the checklist complete, but only for sid. This means that for now only sid has a complete Rails stack. There are two main parts missing from wheezy: - the asset pipeline part could not get in wheezy on time because of the nodejs thing¹ - it was not possible to rebuild all packages to get rubygems-integration support on time. I managed to upload at least the ones required for a working rails stack (without the asset pipeline) before the freeze, and those got into wheezy. ¹ http://lists.debian.org/debian-devel-announce/2012/07/msg00002.html I think I mentioned this before, but here it goes again. My personal plans are to get the missing bits into wheezy-backports once it is available, or into an unnoficial repository, so that we do have a full rails 3 stack available for wheezy. > I am sure that there is only very limited use of those packages > because there are zero bug reports against them. :-) Yep. -- Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature