If you install gems via sudo, you're probably starting to have a huge mess in your installation.
facets is not provided by a gem, but by a debian package (ruby-facets). As to why it did not get installed, that's a different question. Sylvain On Tue, Aug 11, 2015 at 1:30 PM, Raul Dominguez <[email protected]> wrote: > I installed the missing gem (with "sudo gem2.0 install facets"), but > this should have been done automagically by autoproj, right? > > Also I think that the trace is confusing, because it says to use the > ruby1.9.1. libraries... Which I think it doesn't because "sudo gem > install facets" didn't solve the problem but "sudo gem2.0 install > facets" did. > > > Kind regards, > Raúl > > On 11.08.2015 16:34, Raul Dominguez wrote: >> Hello, >> >> I am trying to install rock on the flavor master and somehow autoproj is >> not using ruby2.0 but ruby1.9.1. Can someone point me what might be >> causing this error? >> >> 1. wget http://www.rock-robotics.org/autoproj_bootstrap >> 2. ruby2.0 autoproj_bootstrap git [email protected]:rock-core/buildconf.git >> branch=master >> >> Here is the traceback. Thanks a lot: >> >> >> The current directory is not empty, continue bootstrapping anyway ? >> [yes] yes >> autodetecting the operating system >> operating system: ubuntu,debian - 14.04,14.04.3,lts,trusty,tahr >> Which prepackaged software (a.k.a. 'osdeps') should autoproj install >> automatically (all, none or a comma-separated list of: os gem pip) ? >> The software packages that autoproj will have to build may require >> other >> prepackaged softwares (a.k.a. OS dependencies) to be installed >> (RubyGems >> packages, packages from your operating system/distribution, ...). >> Autoproj >> is able to install those automatically for you. >> >> Advanced users may want to control this behaviour. Additionally, the >> installation of some packages require administration rights, which >> you may >> not have. This option is meant to allow you to control autoproj's >> behaviour >> while handling OS dependencies. >> >> * if you say "all", it will install all packages automatically. >> This requires root access thru 'sudo' >> * if you say "pip", only the Ruby packages will be installed. >> Installing these packages does not require root access. >> * if you say "gem", only the Ruby packages will be installed. >> Installing these packages does not require root access. >> * if you say "os", only the OS-provided packages will be installed. >> Installing these packages requires root access. >> * if you say "none", autoproj will not do anything related to the >> OS dependencies. >> >> Finally, you can provide a comma-separated list of pip gem and os. >> >> As any configuration value, the mode can be changed anytime by calling >> autoproj reconfigure >> >> Finally, the "autoproj osdeps" command will give you the necessary >> information >> about the OS packages that you will need to install manually. >> >> So, what do you want ? (all, none or a comma-separated list of: os >> gem pip) [all] all >> autoproj: installing a proper Ruby environment (this can take a long time) >> autoproj: installing autoproj and its dependencies (this can take a long >> time) >> looking for RubyGems updates >> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot >> load such file -- facets/module/spacename (LoadError) >> from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' >> from /usr/lib/ruby/vendor_ruby/utilrb/logger/hierarchy.rb:1:in >> `<top (required)>' >> from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' >> from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' >> from /usr/lib/ruby/vendor_ruby/utilrb/kernel/require.rb:8:in `block >> in require_dir' >> from /usr/lib/ruby/vendor_ruby/utilrb/kernel/require.rb:5:in `each' >> from /usr/lib/ruby/vendor_ruby/utilrb/kernel/require.rb:5:in >> `require_dir' >> from /usr/lib/ruby/vendor_ruby/utilrb/logger.rb:3:in `<top (required)>' >> from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' >> from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' >> from >> /home/dfki.uni-bremen.de/rdominguez/Artemis/.gems/gems/autoproj-1.13.2/lib/autoproj.rb:30:in >> `<top (required)>' >> from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' >> from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' >> from >> /home/dfki.uni-bremen.de/rdominguez/Artemis/.gems/gems/autoproj-1.13.2/bin/autoproj:12:in >> `<top (required)>' >> from >> /home/dfki.uni-bremen.de/rdominguez/Artemis/.gems/bin/autoproj:23:in `load' >> from >> /home/dfki.uni-bremen.de/rdominguez/Artemis/.gems/bin/autoproj:23:in >> `<main>' >> ERROR: failed to run autoproj bootstrap git, >> [email protected]:rock-core/buildconf.git, branch=master >> >> >> Kind regards, >> Raúl >> >> > > -- > Raúl Domínguez (M.Sc.) > Space Robotics > > Besuchsadresse der Nebengeschäftsstelle: > DFKI GmbH > Robotics Innovation Center > Robert-Hooke-Straße 5 > 28359 Bremen, Germany > > Postadresse der Hauptgeschäftsstelle Standort Bremen: > DFKI GmbH > Robotics Innovation Center > Robert-Hooke-Straße 1 > 28359 Bremen, Germany > > Tel.: +49 421 178 45-6617 > Zentrale: +49 421 178 45-0 > Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen) > E-Mail: [email protected] > > Weitere Informationen: http://www.dfki.de/robotik > ----------------------------------------------------------------------- > Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH > Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern > Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster > (Vorsitzender) Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes > Amtsgericht Kaiserslautern, HRB 2313 > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973 > Steuernummer: 19/673/0060/3 > > _______________________________________________ > Rock-dev mailing list > [email protected] > http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
