On Monday, 12 April 2021 12:01:28 BST Peter Humphrey wrote:

> Okay, step by step. First I chose the basic make.profile, number 1, and
> installed my base system set - everything that doesn't need a GUI. Then I
> switched to the basic desktop profile, number 5 and ran a -uav @world. So
> far so good, but then I attempted to install a basic set of GUI packages -
> everything but a DE. The command was 'emerge -uav @xorg'. I got this:
> 
> --->8
> 
> >>> Preparing source in /var/tmp/portage/dev-ruby/net-telnet-0.2.0/work ...
> 
>  * Running prepare phase for all ...
>  * Running prepare phase for all ...
>  * Running source copy phase for ruby27 ...
> 
> >>> Source prepared.
> >>> Configuring source in /var/tmp/portage/dev-ruby/net-telnet-0.2.0/work
> >>> ...
> 
>  * Running configure phase for ruby27 ...
> 
> >>> Source configured.
> >>> Compiling source in /var/tmp/portage/dev-ruby/net-telnet-0.2.0/work ...
> 
>  * Running compile phase for ruby27 ...
>  * Running compile phase for all ...
> 
> >>> Source compiled.
> 
>  * Skipping make test/check due to ebuild restriction.
> 
> >>> Test phase [disabled because of RESTRICT=test]:
> >>> dev-ruby/net-telnet-0.2.0
> >>> 
> >>> Install dev-ruby/net-telnet-0.2.0 into /var/tmp/portage/dev-ruby/net-
> 
> telnet-0.2.0/image/
>  * Running install phase for ruby27 ...
> Traceback (most recent call last):
>         3: from <internal:gem_prelude>:1:in `<internal:gem_prelude>'
>         2: from <internal:gem_prelude>:1:in `require'
>         1: from /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `<top (required)>'
> /usr/lib64/ruby/2.7.0/rubygems.rb:16:in `require': cannot load such file --
> rubygems/compatibility (LoadError)
>  * Unable to find the gems dir
>  * ERROR: dev-ruby/net-telnet-0.2.0::gentoo failed (install phase):
>  *   Unable to find the gems dir
> --->8
> 
> There seems to be an inconsistency in the ruby packaging. Is there anything
> I can do to evade it? I've attached the package-set files I use when
> building a new system, for info.

This doesn't happen in a stable system, only in ~amd64. It's consistent there, 
though, so I'm tempted to raise a bug report.

-- 
Regards,
Peter.




Reply via email to