rubygems ebuilds want to clobber the ruby19 interpreter. Forcing RUBY=/usr/bin/ruby18 seems to fix the issue (note the attached patch). Reproducible: Always Steps to Reproduce: 1. Set FEATURES="collision-protect" (so the ebuild bails out and gives you a message saying what will be overwritten) 2. Install ruby-1.9 (in the overlay) 3. emerge rubygems (1.3.0 to at least as low as 1.1.1) Actual Results: * checking 95 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * package dev-ruby/rubygems-1.2.0 NOT merged * * Detected file collision(s): * * /usr/bin/ruby19 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-lang/ruby-1.9.0.2 * /usr/bin/ruby19 * Messages for package dev-ruby/rubygems-1.2.0: * Skipping make test/check due to ebuild restriction. * RUBYOPT= * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * package dev-ruby/rubygems-1.2.0 NOT merged * * Detected file collision(s): * * /usr/bin/ruby19 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-lang/ruby-1.9.0.2 * /usr/bin/ruby19 Expected Results: Install without clobbering the ruby19 interpreter.
Created attachment 166669 [details, diff] Suggested fix for rubygems ebuilds
Um... as someone pointed out on the #gentoo-ruby IRC channel, someone managed the fixes in before me and apparently I didn't notice them in two of the ebuilds. The problem exists for versions <= 1.2.0, but the newer ones (at least in the ruby overlay) should be fine.
