Bug #2744
closed
rubygems removed from the foreman yum repo
Added by Kal Aeolian almost 12 years ago.
Updated almost 12 years ago.
Description
On Monday, foreman-proxy installed correctly. Today (Wednesday), it does not as the rubygems RPM was removed from the foreman yum repo.
From a Monday server (1.2 release repo) -
rubygems noarch 1.8.10-1.el6 @foreman 555 k
Today, 'rubygems not found'. This will block installs using the foreman yum repo on RHEL 6 and most likely CentOS 6 as well.
There are a few deps that also break when you need rubygems (like rubygem-rake). Perhaps updating the proxy to use the 1.93 ruby tree would be easier than adding all these deps.
Sorry for the multiple quick updates.
If you are experiencing this bug, the easiest workaround is to have both 1.1 and 1.2 repos enabled at the same time. This will pull in the ruby gems that are required by foreman-proxy (rubygems, rubygem-rack, rubygem-sinatra, rubygem-rkerberos, rubygem-json, rubygem-rake, and rubygem-rack-test). After the deps are installed you can remove the 1.1 repo.
- Category set to Packaging
This is intentional, the RHEL 6 optional channel provides it. You need to ensure this is enabled, it isn't as standard. If you're using RHN then you'll need to subscribe to this as an additional child channel.
We are trying to avoid duplicating and/or updating packages that are already provided in the OS or EPEL.
Edit: the proxy can't use ruby193 because it then wouldn't be able to use puppet packages supplied by EPEL or Puppet Labs, we don't want to redistribute them for ruby193.
- Status changed from New to Rejected
Also available in: Atom
PDF
Updated by 
Updated by