Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 48550
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Ruby Team <ruby@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: alex f <acid.punk@gmx.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
ruby-getttext-0.5.0.emerge-log ruby-getttext-0.5.0.emerge-log text/plain alex f 2004-04-21 04:27 0000 10.19 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 48550 depends on: Show dependency tree
Bug 48550 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-04-21 04:26 0000 
It seems portage wants to emerge the package twice. First normally and then it
tries to "build the package for ruby18" again. Running the while procedure
again: unpacking, building, etc. to finally fail while doing dodoc. See
attached log for all the error messages. I only have ruby 1.8, so why does it
want to build twice?

$ equery list ruby
Searching for package 'ruby' in all categories among:
 * installed packages
[I--] [  ] dev-lang/ruby-1.8.1-r3 (1.8)

------- Comment #1 From alex f 2004-04-21 04:27:18 0000 ------- 
Created an attachment (id=29744) [details]
ruby-getttext-0.5.0.emerge-log

emerge log

------- Comment #2 From Mamoru KOMACHI (RETIRED) 2004-04-22 08:32:21 0000 ------- 
Probablly you set LANG or LC_ALL to de_DE and it causes the build
process to fail. (ruby-gettext compiles sucessfully with LC_ALL=C)
ruby modules get compiled twice as it is needed for ruby SLOT support,
but I'll rewrite the routine to not run the process twice if you
have only one version of ruby. I'll fix them this weekend (sorry
I don't have much time on weekdays).

------- Comment #3 From Xavier Neys 2004-04-22 09:41:01 0000 ------- 
My LC_ALL is 'en_US.utf8' but setting it to C or unsetting it did not solve the
problem.

Removing the following line from the ebuild did solve the problem
USE_RUBY="ruby16 ruby18 ruby19"

I only have 1.8.x installed btw.

Besides, ruby18 and ruby19 do not appear to be valid USE flags.
Only ruby16 is listed in use.local.desc and ruby18/ruby19 are nowhere to be
found.

------- Comment #4 From alex f 2004-04-22 10:12:44 0000 ------- 
Well for me setting LC_ALL=C did install ruby-gettext. But nevertheless this is
a bug. And building twice although only one ruby version is installed should
also be fixed. And yeah, ruby18 and ruby19 aren't defined useflags. But I of
course understand you are busy on weekdays, Mamuro. No problem, just take your
time.

------- Comment #5 From Mamoru KOMACHI (RETIRED) 2004-04-24 06:48:31 0000 ------- 
Thanks for reporting. Both problems have been fixed. USE_RUBY is not
meant for IUSE flag, it only specifies versions of ruby which work
with the package.

Previously I named it RUBY_SLOT but I thought the name is misleading
as SLOT accepts only single number while RUBY_SLOT may contain more
than two members (such as "ruby16 ruby18 ruby19").

ruby16 local IUSE flag left behind should have been removed because
actually that IUSE flag was removed from dev-lang/ruby several month
ago. I've just removed it so I hope it becomes less confusing.

Cheers,
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug