Hi all,
Apologies for cross posting, but I think some nightly users might not
be on -dev yet 
This is a formal Here-Be-Dragons warning - the new rubygem packages
will go into nightly int about 30 hours (1am GMT Friday). The new
packages are built using the new Debian rubygems-integration package,
which means we can create a deb for every gem dependancy of Foreman
(like Jason has done for the RPM repo). This means less ugly hacks in
the foreman package (yay!).
However, it also means some restrictions, until I have time to build
for more distros/architectures. The following things should be noted:
- Most packages are arch-independant, however a few are not, and I
have only built them for 64bit. 32bit users will have to wait a bit
longer (sorry) - Ruby1.9 is not supported. It was giving me horrible pain, and as
Foreman itself isn't fully 1.9 compliant yet, I decided to drop it. I
will sort that as soon as I can. - Packages have only been tested on Debian Squeeze (64bit) - other
distros mileage may vary.
There are a number of rough edges on these packages - some are
backports from wheezy, which work fairly well, but others have been
made with gem2deb. Some packages have had their tests disabled
entirely just to make the debs build. There are a number of known
issues at the moment:
- ruby-rake conflicts with rake for the file /usr/bin/rake
- foreman-development is having conflicts due to ruby1.8 and ruby1.9
not getting along - something weird is happening with the excon gem when adding an EC2
resource - more confirmation of this would be good.
I will try to resolve these issues in the next few days - in the
meantime I've seen no harm done by installing file-conflict packages
with dpkg -i --force overwrite <debfile>.
If any of the above are a problem for you, please move to testing or
disable updates for the time being. If you're ok with the above,
please do test these packages! Things will not improve without testers
Assuming no issues, I will promote these packages to testing and
stable next week.
Regards,
Greg