Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 675822 - Available Ruby on Rails versions: (none found)
Summary: Available Ruby on Rails versions: (none found)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-19 05:24 UTC by far jump
Modified: 2019-01-21 17:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,4.99 KB, application/x-info)
2019-01-19 05:24 UTC, far jump
Details

Note You need to log in before you can comment on or make changes to this bug.
Description far jump 2019-01-19 05:24:47 UTC
Created attachment 562108 [details]
emerge --info

Brand new gentoo install everything emerged w/o problems.  emerged apache, passenger and rails 5.2.2.  cannot execute:
rails new ror  (per Gentoo Rails wiki page)

when I run eselect rails list, I get (none found)  however:

>whereis rails-5.2.2 
rails-5.2: /usr/bin/rails-5.2.2
Comment 1 Hans de Graaff gentoo-dev Security 2019-01-19 08:06:05 UTC
I've had a suspicion for some time that eselect-rails is non-functional in any case, so this bug will be a good opportunity to investigate that. Are you running into issues other than eselect-rails not reporting things correctly?
Comment 2 far jump 2019-01-19 16:20:59 UTC
the only other problems I had was with rails itself.

WARNING: Nokogiri was built against LibXML version 2.9.9, but has dynamically loaded 2.9.8 (I emerged nokogiri before rails)

rails-5.2.2 new ror
An error occurred while installing sqlite3 (1.3.13), and Bundler cannot continue.
Make sure that `gem install sqlite3 -v '1.3.13'` succeeds before bundling.

rails-5.2.2 new ror --database=postgresql
ran correctly

This is a brand new install and has not be deployed yet.  I am perfectly happy to re-emerge or un-emerge packages or even break it if you need to.
Comment 3 far jump 2019-01-21 00:10:26 UTC
OK un-emerged everything to do with rails-5.2.2 and all ruby gems.

remembering I had another deployed web-server running rails-5.2.0 that emerged/upgraded (from ver 4) and runs without any issues.  I emerged rails-5.2.0.  I also upgraded eselect-rails to verision 0.24 and now eselect rails works.

  I then upgraded rails to 5.2.2 (eselect automatically updated to 5.2.2) and now everything works - no errors on rails or rake

I am still getting the WARNING about nokogiri
Comment 4 Hans de Graaff gentoo-dev Security 2019-01-21 17:46:30 UTC
(In reply to far jump from comment #3)
> I also upgraded eselect-rails to verision 0.24 and now eselect
> rails works.

Aha, I forgot to update the eselect-rails dependency. Now fixed, thanks!
Comment 5 Larry the Git Cow gentoo-dev 2019-01-21 17:47:38 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba0657d906061c923ff7cd293afaf2e02a0a9050

commit ba0657d906061c923ff7cd293afaf2e02a0a9050
Author:     Hans de Graaff <graaff@gentoo.org>
AuthorDate: 2019-01-21 17:47:30 +0000
Commit:     Hans de Graaff <graaff@gentoo.org>
CommitDate: 2019-01-21 17:47:30 +0000

    dev-ruby/railties: fix eselect-rails dependency
    
    Require a new enough version that recognizes rails 5.2.
    
    Fixes: https://bugs.gentoo.org/675822
    Signed-off-by: Hans de Graaff <graaff@gentoo.org>
    Package-Manager: Portage-2.3.51, Repoman-2.3.11

 dev-ruby/railties/railties-5.2.2.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)