View previous topic :: View next topic |
Author |
Message |
oz_tiram n00b
Joined: 31 May 2015 Posts: 45
|
Posted: Sat Jan 14, 2017 6:54 am Post subject: No ebuilds to satisfy building vagrant |
|
|
Hi,
I am having trouble installing vagrant with Ruby22. Can someone take a look at this?
Code: |
# USE=ruby22 emerge -a =app-emulation/vagrant-1.9.1
These are the packages that would be merged, in order:
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy ">=dev-ruby/erubis-2.7.0[ruby_targets_ruby22]".
(dependency required by "app-emulation/vagrant-1.9.1::gentoo[-test,ruby_targets_ruby22]" [ebuild])
(dependency required by "=app-emulation/vagrant-1.9.1" [argument])
|
But I just compiled log4r:
Code: |
# USE=ruby22 emerge -a log4r
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-ruby/log4r-1.1.10-r2
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) dev-ruby/log4r-1.1.10-r2::gentoo
* log4r-1.1.10.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/log4r-1.1.10-r2/work
>>> Preparing source in /var/tmp/portage/dev-ruby/log4r-1.1.10-r2/work ...
* Running prepare phase for all ...
* Running source copy phase for ruby21 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-ruby/log4r-1.1.10-r2/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-ruby/log4r-1.1.10-r2/work ...
* Running compile phase for all ...
>>> Source compiled.
>>> Test phase [not enabled]: dev-ruby/log4r-1.1.10-r2
>>> Install log4r-1.1.10-r2 into /var/tmp/portage/dev-ruby/log4r-1.1.10-r2/image/ category dev-ruby
* Running install phase for ruby21 ...
* Running install phase for all ...
* Running check install phase for ruby21 ...
>>> Completed installing log4r-1.1.10-r2 into /var/tmp/portage/dev-ruby/log4r-1.1.10-r2/image/
* Final size of build directory: 776 KiB
* Final size of installed tree: 412 KiB
ecompressdir: bzip2 -9 /usr/share/doc
>>> Done.
>>> Installing (1 of 1) dev-ruby/log4r-1.1.10-r2::gentoo
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
|
So what am I supposed to do? |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30916 Location: here
|
Posted: Sat Jan 14, 2017 9:54 am Post subject: |
|
|
First the corect use flag is called ruby_targets_ruby22, but the problem is that this use flag is maked for package dev-ruby/erubis you need to umask (see here or here) _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
oz_tiram n00b
Joined: 31 May 2015 Posts: 45
|
Posted: Sun Jan 15, 2017 4:30 pm Post subject: |
|
|
fedeliallalinea wrote: | First the corect use flag is called ruby_targets_ruby22, but the problem is that this use flag is maked for package dev-ruby/erubis you need to umask (see here or here) |
Excuse me for the ignorance, but I have no clue how to proceed with the information you provided me.
I tried the following:
Code: |
# cat /etc/portage/package.use.mask
dev-ruby/erubis -ruby_targets_ruby22 |
But this won't do:
Code: |
USE=ruby_targets_ruby22 emerge -a log4r vagrant
These are the packages that would be merged, in order:
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy ">=dev-ruby/erubis-2.7.0[ruby_targets_ruby22]".
(dependency required by "app-emulation/vagrant-1.9.1::gentoo[ruby_targets_ruby22,-test]" [ebuild])
(dependency required by "vagrant" [argument]) |
|
|
Back to top |
|
|
oz_tiram n00b
Joined: 31 May 2015 Posts: 45
|
Posted: Sun Jan 15, 2017 4:43 pm Post subject: |
|
|
I solved the problem, I edited the file /etc/portage/profile/use.stable.mask
and unmask the ruby target as described here: https://wiki.gentoo.org/wiki/Project:Ruby |
|
Back to top |
|
|
|