| Summary: | dev-ruby/facter-3.0.1-r4 : error: cannot access com.puppetlabs.Facter | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ruby, sysadmin |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge log
package history |
||
|
Description
Toralf Förster
2015-07-22 12:16:17 UTC
Created attachment 407410 [details]
package history
looks like we might need java, can you install a jdk and retry? (In reply to Matthew Thode ( prometheanfire ) from comment #2) > looks like we might need java, can you install a jdk and retry? Hrm - the attached package history contains already a jdk ... I didn't see openjdk though, and that's the jdk they mention upstream iirc. I run with the oracle jdk (1.7 or 1.8). Gah - after I eventually managed to install oracle-jdk-bin-1.8.0.51 I realized, that $> eselect java-vm set system icedtea-bin-7 would be fully sufficient to let emerge at least start to emerge dev-ruby/facter (icedtea-bin-6 was set before - and that won't work). well, let me know how it goes :P emerged fine with the new icedtea at the ~amd64 chroot image. :-) ok, I'll add a dep on >=virtual/jdk-1.7 even better... -DUSE_JRUBY_SUPPORT=FALSE fixed in 3.0.2-r1 (In reply to Matthew Thode ( prometheanfire ) from comment #9) > even better... > > -DUSE_JRUBY_SUPPORT=FALSE > > fixed in 3.0.2-r1 This might be needed for that server package you added recently? So it might need to be a USE flag? not needed for puppetserver, puppetserver relies on puppet-agent which conflicts with facter (it installs it's own version with conflicting files). |