Sounds good. I'm hoping our eventual build system will obviate all of this (perhaps using JRuby?), but I think history makes clear we should make guides based on what we have now. :) On Feb 28, 2016 13:17, "Chris Nauroth" <[email protected]> wrote:
> Thanks, Sean! > > To clarify, shortly after my last email, I started testing YETUS-226, and > I saw some glaringly obvious misformatting problems in the rendered > content. Surely other reviewers would have commented on it already, so I > assumed it was a problem on my side. That eventually led me to noticing > Ruby 1.9 was the problem, and then finding RVM as an alternative to rpm or > deb. I switched to an RVM-deployed Ruby 2.2.1, and everything worked > great. I think you've just been watching a Ruby newb ramp up on how Ruby > packaging infrastructure works. :-) > > I do think it would be nice to point out RVM in the instructions. That > would help people like me who don't have Ruby experience but want to get > enough of its infrastructure deployed to work on Yetus website content. I > filed YETUS-317. > > --Chris Nauroth > > > > > On 2/27/16, 8:35 PM, "Sean Busbey" <[email protected]> wrote: > > >Interesting that Ruby 1.9 on ubuntu works. I thought that our build > >required Ruby 2+. Ruby 2.0 is a train wreck, so I rely on Ruby 2.2.0 > >to build. > > > >I use RVM, because I have never known system packaged Ruby to be > >usable for any sustained period: > > > >https://rvm.io/ > > > >RVM also lets me save a gemset that has the results of `bundle > >install` without impacting the rest of my Ruby use. I wouldn't say RVM > >specifically is required, but some Ruby manager is for practically any > >regular use of Ruby. > > > >I think we tried to avoid all of the complications in using Ruby by > >specifying a need for a "working ruby 2.x environment setup". > > > >What do folks think about just updating the instructions to point folks > >to RVM? > > > >It's ASLv2 licensed, but its default installation instructions are > >curl piped to bash, so I'm not thrilled about that. > > > >On Sat, Feb 27, 2016 at 4:35 PM, Chris Nauroth <[email protected]> > >wrote: > >> FWIW, this problem seems specific to my CentOS VM. I switched over to > >>my > >> Ubuntu VM, repeated the whole process, and it worked fine. I assume > >>there > >> is some subtle CentOS package management issue at play here. I won't > >> troubleshoot it any further right now, because I can proceed using the > >> Ubuntu VM. > >> > >> Here is some info on my non-working CentOS environment and my working > >> Ubuntu environment, in case anyone in the future hits a similar problem, > >> or someone more savvy on Ruby infrastructure can spot a problem. > >> > >> > >> > >> uname -a > >> Linux centos 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 11:36:42 UTC 2015 > >> x86_64 x86_64 x86_64 GNU/Linux > >> > >> cat /etc/redhat-release > >> CentOS Linux release 7.1.1503 (Core) > >> > >> ruby --version > >> ruby 2.0.0p598 (2014-11-13) [x86_64-linux] > >> > >> bundle --version > >> Bundler version 1.11.2 > >> > >> bundle show middleman > >> /home/cnauroth/.gem/ruby/gems/middleman-3.4.0 > >> > >> > >> > >> uname -a > >> Linux ubuntu 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 > >>17:43:14 > >> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux > >> > >> lsb_release -r > >> Release: 14.04 > >> > >> ruby --version > >> ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] > >> > >> bundle --version > >> Bundler version 1.11.2 > >> > >> bundle show middleman > >> /var/lib/gems/1.9.1/gems/middleman-3.4.0 > >> > >> > >> > >> > >> --Chris Nauroth > >> > >> > >> > >> > >> On 2/27/16, 8:55 AM, "Chris Nauroth" <[email protected]> wrote: > >> > >>>I'm trying to build the Yetus website content according to the > >>>instructions in asf-site-src/source/contribute/website.md, but I'm > >>>running > >>>into some problems. Can anyone please help? Warning: I don't know > >>>Ruby, > >>>so there is a high probability I'm doing something stupid. > >>> > >>>One thing I discovered is that there is a dependency on ruby-devel. > >>>That > >>>part became obvious when the "bundle install" command failed due to a > >>>missing Ruby header. We probably want to document that dependency. > >>> > >>>After that, I made progress with the install, but trying to run > >>>middleman > >>>showed that it couldn't find the command: > >>> > >>> bundle exec middleman > >>>bundler: command not found: middleman > >>>Install missing gem executables with `bundle install` > >>> > >>> > >>>That's despite bundle seemingly reporting that middleman is installed > >>>just > >>>fine: > >>> > >>> bundle install > >>>... > >>>Using middleman 3.4.0 > >>>Bundle complete! 8 Gemfile dependencies, 56 gems now installed. > >>>Use `bundle show [gemname]` to see where a bundled gem is installed. > >>> > >>> bundle show middleman > >>>/home/cnauroth/.gem/ruby/gems/middleman-3.4.0 > >>> > >>> > >>>Searching the web showed a few reports that some environments needed > >>>middleman installed globally for it to work correctly, so I followed a > >>>recommendation to try repeating the installation as root. After that, > >>>middleman can be found, but I'm getting a bizarre ruby backtrace: > >>> > >>> bundle exec middleman version > >>>/home/cnauroth/.gem/ruby/bundler/gems/redcarpet-47d7c4e5ab23/lib/redcarp > >>>et > >>>. > >>>rb:1:in `require': cannot load such file -- redcarpet.so (LoadError) > >>> from > >>>/home/cnauroth/.gem/ruby/bundler/gems/redcarpet-47d7c4e5ab23/lib/redcarp > >>>et > >>>. > >>>rb:1:in `<top (required)>' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/bundler-1.11.2/lib/bundler/runtime.rb:77:i > >>>n > >>>`require' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/bundler-1.11.2/lib/bundler/runtime.rb:77:i > >>>n > >>>`block (2 levels) in require' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/bundler-1.11.2/lib/bundler/runtime.rb:72:i > >>>n > >>>`each' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/bundler-1.11.2/lib/bundler/runtime.rb:72:i > >>>n > >>>`block in require' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/bundler-1.11.2/lib/bundler/runtime.rb:61:i > >>>n > >>>`each' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/bundler-1.11.2/lib/bundler/runtime.rb:61:i > >>>n > >>>`require' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/bundler-1.11.2/lib/bundler.rb:99:in > >>>`require' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/middleman-core-3.4.0/lib/middleman-core/lo > >>>ad > >>>_ > >>>paths.rb:37:in `setup_load_paths' > >>> from > >>>/home/cnauroth/.gem/ruby/gems/middleman-core-3.4.0/bin/middleman:10:in > >>>`<top (required)>' > >>> from /usr/local/bin/middleman:23:in `load' > >>> from /usr/local/bin/middleman:23:in `<main>' > >>> > >>> > >>>There is mention of a redcarpet.so library in that message, so I tried > >>>"gem install redcarpet". That seems to install fine, but it doesn't > >>>resolve the middleman backtrace. > >>> > >>>Has anyone seen this before? > >>> > >>>--Chris Nauroth > >>> > >>> > >> > > > >
