Bug #4286
closed
Added by Duncan Innes over 10 years ago.
Updated over 10 years ago.
Description
I'm installing on RHEL 6.5 via Satellite channels that I've synched and cloned down appropriately (hopefully).
foreman-proxy has a dependency on rubygem(sinatra) which is not being satisfied by ruby193-rubygem-sinatra-1.3.2-12.el6.noarch that I have installed from the Software Collection Library on my Satellite.
In fact, a whole bunch of ruby dependencies seem to be unsatisfied by what I have in the Software Collection Library.
Channels subscribed to by this build:
RHEL 6 Server
- Optional
- RHN Tools
- Software Collections 1
- Puppet (clone of PuppetLabs to get puppet RPM's)
- 3rd Party (pulled EPEL packages into here)
Activation keys ensure that puppet is installed during the build (a requirement of all deployments here), and foreman-installer so that I can run foreman-installer once booted up.
rubygem(sinatra) is supplied by rubygem-sinatra from EPEL, it doesn't use software collections (that would have a ruby193 prefix). I'd guess your 3rd party channel is missing it?
No problem, I'll pull more into the 3rd party channel. I'm getting mighty confused as to how many different versions of rubygem packages I have floating around the Satellite at the moment. Foreman, SCL, Katello, 3rd party etc.
Closing this down.
Cheers
D
- Status changed from New to Rejected
Yeah, there are a lot of variants, so it's confusing.
Our projects fall into SCL or non-SCL: core Foreman requires SCL, but the proxy and installer don't (since Puppet isn't SCL).
Both Foreman and Katello projects build on top of RHSCL now, while the proxy and installer build on top of EPEL.
Also available in: Atom
PDF
Updated by 
Updated by