Mailing List Archive

bundler-2.1.4 failing to emerge
I'm updating my system, but it is stopping on dev-ruby/bundler-2.1.4

According rebuild, below it shouldn't be related to new "python"

[ebuild R ] dev-ruby/bundler-2.1.4 USE="doc -test" RUBY_TARGETS="ruby27 -ruby26*"

------message--------
ERROR: compile
ERROR: dev-ruby/bundler-2.1.4::gentoo failed (compile phase):
failed to (re)build documentation

Call stack:
ebuild.sh, line 127: Called src_compile
environment, line 2182: Called ruby-ng_src_compile
environment, line 1782: Called _ruby_invoke_environment 'all' 'all_ruby_compile'
environment, line 618: Called all_ruby_compile
environment, line 727: Called all_fakegem_compile
environment, line 688: Called die
The specific snippet of code:
rdoc ${RUBY_FAKEGEM_DOC_SOURCES} || die "failed to (re)build documentation";

If you need support, post the output of `emerge --info '=dev-ruby/bundler-2.1.4::gentoo'`,
the complete build log and the output of `emerge -pqv '=dev-ruby/bundler-2.1.4::gentoo'`.
The complete build log is located at '/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment'.
Working directory: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'
S: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'

--
Thelma
Re: bundler-2.1.4 failing to emerge [ In reply to ]
Thelma
On 7/6/22 11:50, thelma@sys-concept.com wrote:
> I'm updating my system, but it is stopping on dev-ruby/bundler-2.1.4
>
> According rebuild, below it shouldn't be related to new "python"
>
> [ebuild   R   ] dev-ruby/bundler-2.1.4  USE="doc -test" RUBY_TARGETS="ruby27 -ruby26*"
>
> ------message--------
> ERROR: compile
> ERROR: dev-ruby/bundler-2.1.4::gentoo failed (compile phase):
>   failed to (re)build documentation
>
> Call stack:
>     ebuild.sh, line  127:  Called src_compile
>   environment, line 2182:  Called ruby-ng_src_compile
>   environment, line 1782:  Called _ruby_invoke_environment 'all' 'all_ruby_compile'
>   environment, line  618:  Called all_ruby_compile
>   environment, line  727:  Called all_fakegem_compile
>   environment, line  688:  Called die
> The specific snippet of code:
>                   rdoc ${RUBY_FAKEGEM_DOC_SOURCES} || die "failed to (re)build documentation";
>
> If you need support, post the output of `emerge --info '=dev-ruby/bundler-2.1.4::gentoo'`,
> the complete build log and the output of `emerge -pqv '=dev-ruby/bundler-2.1.4::gentoo'`.
> The complete build log is located at '/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/build.log'.
> The ebuild environment file is located at '/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment'.
> Working directory: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'
> S: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'

I think it is a bug in recent version of rubby, "documentation doesn't exist or has a wrong link"
Removing "doc" flag solve the problem:

=dev-ruby/bundler-2.1.4 -doc
Re: bundler-2.1.4 failing to emerge [ In reply to ]
On Wed, 2022-07-06 at 11:50 -0600, thelma@sys-concept.com wrote:
> I'm updating my system, but it is stopping on dev-ruby/bundler-2.1.4
>
> According rebuild, below it shouldn't be related to new "python"
>
> [ebuild R ] dev-ruby/bundler-2.1.4 USE="doc -test" RUBY_TARGETS="ruby27 -ruby26*"

I had this as well. I had to manually use "eselect ruby" to choose
ruby27 in order to proceed.