Gentoo Forums :: View topic - Trouble emerging rdoc-4.2.0 [solved]

Trouble emerging rdoc-4.2.0 [solved]

View unanswered posts
View posts from last 24 hours

Gentoo Forums Forum Index

Portage & Programming

View previous topic :: View next topic

Author

Message

evoweiss
Veteran
Veteran

Joined: 07 Sep 2003
Posts: 1678
Location: Edinburgh, UK

Posted: Mon May 15, 2017 8:46 pm Post subject: Trouble emerging rdoc-4.2.0 [solved]

Hi all,

For some reason, an emerge -uDNp @world fails at rdoc-4.2.0 (see code below).

My ruby profile is set to Ruby22 and I have RUBY_TARGETS="ruby22" in /etc/make.conf, so I am not sure what I am missing.

Any help would be appreciated.

Best,

Alex

Code:

Last edited by evoweiss on Mon May 15, 2017 9:08 pm; edited 1 time in total

ntnn
n00b
n00b

Joined: 20 Mar 2017
Posts: 10

Posted: Mon May 15, 2017 8:51 pm Post subject:

Known and has been resolved: https://bugs.gentoo.org/show_bug.cgi?id=618538 Sync again and then try to update.

evoweiss
Veteran
Veteran

Joined: 07 Sep 2003
Posts: 1678
Location: Edinburgh, UK

Posted: Mon May 15, 2017 9:08 pm Post subject:

ntnn wrote:

Known and has been resolved: https://bugs.gentoo.org/show_bug.cgi?id=618538

Sync again and then try to update.

Indeed, that did the trick.

Thanks!

Alex

cwc
Veteran
Veteran

Joined: 20 Mar 2006
Posts: 1178
Location: Tri-Cities, WA USA

Posted: Sun Aug 20, 2017 1:09 pm Post subject: I had the same problem.

I had the same problem.
I do not have gems with ruby 21 but I do with ruby 22

eselect ruby list
Available Ruby profiles:
[1] ruby21
[2] ruby22 (with Rubygems) *

And I do not have anything set in /etc/portage/make.conf

Any ideas?

Calculating dependencies... done!
[nomerge ] dev-lang/ruby-2.2.6:2.2::gentoo USE="berkdb gdbm ipv6 ncurses rdoc readline ssl -debug -doc -examples -jemalloc (-libressl) -rubytests -socks5 -tk -xemacs"
[ebuild R ] dev-ruby/rdoc-4.2.0::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby21%*)" 0 KiB

Code:

>>> Emerging (1 of 1) dev-ruby/rdoc-4.2.0::gentoo
* rdoc-4.2.0.gem SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
* Running unpack phase for all ...
* Unpacking .gem file... ... [ ok ]
* Uncompressing metadata ... [ ok ]
* Unpacking data.tar.gz ... [ ok ]
>>> Source unpacked in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work
>>> Preparing source in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work ...
* Running prepare phase for all ...
* Applying rdoc-3.0.1-bin-require.patch ... [ ok ]
* Running source copy phase for ruby22 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work ...
* Running compile phase for ruby22 ...
* Running compile phase for all ...
>>> Source compiled.
>>> Test phase [not enabled]: dev-ruby/rdoc-4.2.0

>>> Install rdoc-4.2.0 into /var/tmp/portage/dev-ruby/rdoc-4.2.0/image/ category dev-ruby
* Running install phase for ruby22 ...
* Running install phase for all ...
* ERROR: dev-ruby/rdoc-4.2.0::gentoo failed (install phase):
* USE Flag 'ruby_targets_ruby21' not in IUSE for dev-ruby/rdoc-4.2.0
*
* Call stack:
* ebuild.sh, line 115: Called src_install
* environment, line 4396: Called ruby-ng_src_install
* environment, line 4096: Called _ruby_invoke_environment 'all' 'all_ruby_install'
* environment, line 535: Called all_ruby_install
* environment, line 631: Called use 'ruby_targets_ruby21'
* phase-helpers.sh, line 200: Called die
* The specific snippet of code:
* die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}"
*
* If you need support, post the output of `emerge --info '=dev-ruby/rdoc-4.2.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-ruby/rdoc-4.2.0::gentoo'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info =rdoc-4.2.0
* The complete build log is located at '/var/tmp/portage/dev-ruby/rdoc-4.2.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-ruby/rdoc-4.2.0/temp/environment'.
* Working directory: '/var/tmp/portage/dev-ruby/rdoc-4.2.0/work/all/rdoc-4.2.0'
* S: '/var/tmp/portage/dev-ruby/rdoc-4.2.0/work/all/rdoc-4.2.0'

>>> Failed to emerge dev-ruby/rdoc-4.2.0, Log file:

>>> '/var/tmp/portage/dev-ruby/rdoc-4.2.0/temp/build.log'

* Messages for package dev-ruby/rdoc-4.2.0:

* ERROR: dev-ruby/rdoc-4.2.0::gentoo failed (install phase):
* USE Flag 'ruby_targets_ruby21' not in IUSE for dev-ruby/rdoc-4.2.0
*
* Call stack:
* ebuild.sh, line 115: Called src_install
* environment, line 4396: Called ruby-ng_src_install
* environment, line 4096: Called _ruby_invoke_environment 'all' 'all_ruby_install'
* environment, line 535: Called all_ruby_install
* environment, line 631: Called use 'ruby_targets_ruby21'
* phase-helpers.sh, line 200: Called die
* The specific snippet of code:
* die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}"
*
* If you need support, post the output of `emerge --info '=dev-ruby/rdoc-4.2.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-ruby/rdoc-4.2.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-ruby/rdoc-4.2.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-ruby/rdoc-4.2.0/temp/environment'.
* Working directory: '/var/tmp/portage/dev-ruby/rdoc-4.2.0/work/all/rdoc-4.2.0'
* S: '/var/tmp/portage/dev-ruby/rdoc-4.2.0/work/all/rdoc-4.2.0'

_________________
Without diversity there can be no evolution:)

Dzierzymiecz
n00b
n00b

Joined: 14 Mar 2010
Posts: 9

Posted: Sun Aug 20, 2017 1:30 pm Post subject:

Same issue as cwc

sevendogs
n00b
n00b

Joined: 25 Mar 2017
Posts: 5
Location: Texas

Posted: Sun Aug 20, 2017 5:33 pm Post subject: rdoc emerge fails

Dzierzymiecz wrote:

Same issue as cwc

Same issue here, did an

Code:

emerge --sync

but same behavior.
_________________
When asked "Are you a god or a man?" the Buddha replied "I am awake."

Bloot
Tux's lil' helper

Joined: 10 Mar 2006
Posts: 99
Location: Barcelona

Posted: Sun Aug 20, 2017 5:39 pm Post subject:

After an emerge --sync same problem here

Code:

# emerge --ask --verbose --update --deep --newuse @world

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] dev-ruby/rubygems-2.5.2::gentoo USE="-server {-test}" RUBY_TARGETS="ruby22 (-ruby23) (-ruby21%*)" 465 KiB
[ebuild R ] virtual/rubygems-11::gentoo RUBY_TARGETS="ruby22 (-rbx) (-ruby23) (-ruby21%*)" 0 KiB
[ebuild R ] dev-ruby/rake-10.5.0::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby23) (-ruby21%*)" 128 KiB
[ebuild R ] dev-ruby/power_assert-0.3.1::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby23) (-ruby21%*)" 14 KiB
[ebuild R ] dev-ruby/minitest-5.8.4:5::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby23) (-ruby21%*)" 71 KiB
[ebuild R ] dev-ruby/json-1.8.3::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby23) (-ruby21%*)" 149 KiB
[ebuild R ] dev-ruby/test-unit-3.1.9:2::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby23) (-ruby21%*)" 122 KiB
[ebuild R ] dev-ruby/racc-1.4.11::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby21%*)" 111 KiB
[ebuild R ] dev-ruby/rdoc-4.2.0::gentoo USE="-doc {-test}" RUBY_TARGETS="ruby22 (-ruby21%*)" 718 KiB

Code:

>>> Emerging (9 of 9) dev-ruby/rdoc-4.2.0::gentoo
* rdoc-4.2.0.gem SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
* Running unpack phase for all ...
* Unpacking .gem file... ... [ ok ]
* Uncompressing metadata ... [ ok ]
* Unpacking data.tar.gz ... [ ok ]
>>> Source unpacked in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work
>>> Preparing source in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work ...
* Running prepare phase for all ...
* Applying rdoc-3.0.1-bin-require.patch ... [ ok ]
* Running source copy phase for ruby22 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-ruby/rdoc-4.2.0/work ...
* Running compile phase for ruby22 ...
* Running compile phase for all ...
>>> Source compiled.
>>> Test phase [not enabled]: dev-ruby/rdoc-4.2.0

>>> Install rdoc-4.2.0 into /var/tmp/portage/dev-ruby/rdoc-4.2.0/image/ category dev-ruby
* Running install phase for ruby22 ...
* Running install phase for all ...
* ERROR: dev-ruby/rdoc-4.2.0::gentoo failed (install phase):
* USE Flag 'ruby_targets_ruby21' not in IUSE for dev-ruby/rdoc-4.2.0
*
* Call stack:
* ebuild.sh, line 115: Called src_install
* environment, line 4426: Called ruby-ng_src_install
* environment, line 4126: Called _ruby_invoke_environment 'all' 'all_ruby_install'
* environment, line 565: Called all_ruby_install
* environment, line 661: Called use 'ruby_targets_ruby21'
* phase-helpers.sh, line 200: Called die
* The specific snippet of code:
* die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}"

elprawn
n00b
n00b

Joined: 22 May 2017
Posts: 5

Posted: Sun Aug 20, 2017 5:41 pm Post subject:

Bloot wrote:

After an emerge --sync same problem here

Code:

I am having the same problem.

Fitzcarraldo
Advocate

Joined: 30 Aug 2008
Posts: 2002
Location: United Kingdom

Posted: Sun Aug 20, 2017 6:04 pm Post subject:

To the August 20, 2017 posters: https://bugs.gentoo.org/show_bug.cgi?id=628368 _________________ Clevo W230SS: amd64 nvidia-drivers & xf86-video-intel. Compal NBLB2: ~amd64 xf86-video-ati. Dual boot Win 7 Pro 64-bit. OpenRC udev elogind & KDE on both. Fitzcarraldo's blog

gen2saurus
n00b
n00b

Joined: 20 Aug 2017
Posts: 11

Posted: Sun Aug 20, 2017 6:43 pm Post subject: Re: I had the same problem.

cwc wrote:

Code:

It's a bug in ebuild.

Please do

Code:

cd /usr/portage/dev-ruby/rdoc
sed -i 's/[[:alpha:]]*21 //' /usr/portage/dev-ruby/rdoc/rdoc-4.2.0.ebuild
ebuild rdoc-4.2.0.ebuild digest

and recompile it.

sevendogs
n00b
n00b

Joined: 25 Mar 2017
Posts: 5
Location: Texas

Posted: Sun Aug 20, 2017 7:13 pm Post subject: Re: I had the same problem.

Quote:

It's a bug in ebuild.

Please do

Code:

cd /usr/portage/dev-ruby/rdoc
sed -i 's/[[:alpha:]]*21 //' /usr/portage/dev-ruby/rdoc/rdoc-4.2.0.ebuild
ebuild rdoc-4.2.0.ebuild digest

and recompile it.

That did it for me, thanks gen2saurus!
_________________
When asked "Are you a god or a man?" the Buddha replied "I am awake."

cwc
Veteran
Veteran

Joined: 20 Mar 2006
Posts: 1178
Location: Tri-Cities, WA USA

Posted: Sun Aug 20, 2017 11:59 pm Post subject: Re: I had the same problem.

sevendogs wrote:

Quote:

It's a bug in ebuild.

Please do

Code:

cd /usr/portage/dev-ruby/rdoc
sed -i 's/[[:alpha:]]*21 //' /usr/portage/dev-ruby/rdoc/rdoc-4.2.0.ebuild
ebuild rdoc-4.2.0.ebuild digest

and recompile it.

That did it for me, thanks gen2saurus!

The above also solved the problem for me! Thanks!

This is amazing! Nice !
sed -i 's/[[:alpha:]]*21 //' /usr/portage/dev-ruby/rdoc/rdoc-4.2.0.ebuild
_________________
Without diversity there can be no evolution:)

TuxPower
n00b
n00b

Joined: 27 Apr 2018
Posts: 1
Location: Denmark

Posted: Fri Apr 27, 2018 2:09 pm Post subject:

On 2018-04-27 this still works with rdoc-4.3.0/ruby23 with the following change:

Code:

cd /usr/portage/dev-ruby/rdoc
sed -i 's/[[:alpha:]]*22 //' /usr/portage/dev-ruby/rdoc/rdoc-4.3.0.ebuild
ebuild rdoc-4.3.0.ebuild digest

And then re-emerge.

Update
The emerge later in the day on my primary desktop and laptop did not have this problem.
So for people in the future who read this:

Adapt the above fix to your rdoc/ruby version
- or -
Wait for it to be fixed in a later emerge --sync

richardash1981
Tux's lil' helper

Joined: 08 Apr 2005
Posts: 94
Location: England

Posted: Sat Apr 28, 2018 6:37 pm Post subject:

This is still failing for me after a sync. The problem is that all though I don't now have ruby 2.2.x installed at all, I still have it in RUBY_TARGETS according to emerge --info:

Code:

RUBY_TARGETS="ruby22 ruby23"

This isn't set anywhere in /etc/portage/, and I have my profile set to the desktop stable (17.0).

Code:

default/linux/x86/17.0/desktop (stable) *

I think this is because the tree still has the line

Code:

/usr/portage/profiles/base/make.defaults:RUBY_TARGETS="ruby22 ruby23"

which is setting ruby 2.2 when it shouldn't be.

guitou
Guru
Guru

Joined: 02 Oct 2003
Posts: 534
Location: France

Posted: Sun Apr 29, 2018 12:08 pm Post subject:

Hi. A simple workaround is to set RUBY_TARGET="ruby23" in /etc/portage/make.conf ++ Gi)

Display posts from previous:

	Gentoo Forums Forum Index Portage & Programming	All times are GMT
Page 1 of 1

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2022 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy