Hi all,
With the release of Debian 7 (Wheezy) last Sunday, I'm happy to report
there is now a Wheezy repo on deb.theforeman.org.
Currently there are only nightly packages, as I'm still ironing out the
dependencies. Given that we are not far from starting RCs for 1.2, I'm
probably not going to backport 1.1 to Wheezy - rather, we will push the RCs
for 1.2 to Wheezy as they come along, with 1.2 being the first stable
Wheezy release.
There's currently an issue with all the nightlies around migrating the
settings table during the initial setup (see
https://github.com/theforeman/foreman/pull/574 for a possible fix that is
under review). Apart from that, the wheezy packages seem to work for a
casual test.
The foreman-installer seems to work fine on wheezy, assuming you tell it to
use the nightlies.
Please do test and report back any:
*) Missing dependencies
*) Unnecessary dependencies
*) Other broken things 
Cheers,
Greg
Hi Greg,
I've started playing around with the nightly packages under Wheezy. When
upgrading from a previous Squeeze install the foreman package fails to
install - it gets stuck building json as it needs mkmf from
ruby-1.9.1-dev. However the foreman package requires ruby-dev which is
fulfilled by ruby1.8-dev that was pulled in by my 1.1 install.
Would it be better to explicitly depend on ruby-1.9.1-dev for those of
us not installing on a fresh Wheezy?
Dan
···
On 07/05/13 00:18, Greg Sutcliffe wrote:
> Hi all,
>
> With the release of Debian 7 (Wheezy) last Sunday, I'm happy to report
> there is now a Wheezy repo on deb.theforeman.org
> .
>
> Currently there are only nightly packages, as I'm still ironing out
> the dependencies. Given that we are not far from starting RCs for 1.2,
> I'm probably not going to backport 1.1 to Wheezy - rather, we will
> push the RCs for 1.2 to Wheezy as they come along, with 1.2 being the
> first stable Wheezy release.
>
> There's currently an issue with all the nightlies around migrating the
> settings table during the initial setup
> (see https://github.com/theforeman/foreman/pull/574 for a possible fix
> that is under review). Apart from that, the wheezy packages seem to
> work for a casual test.
>
> The foreman-installer seems to work fine on wheezy, assuming you tell
> it to use the nightlies.
>
> Please do test and report back any:
>
> *) Missing dependencies
> *) Unnecessary dependencies
> *) Other broken things ;)
>
> Cheers,
> Greg
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Indeed, this is already logged as
Bug #2557: Debian Wheezy RC1 can miss the ruby1.9.1-dev dependency - Packaging - Foreman but
I'd only considered it from the foreman-installer viewpoint. I'll get that
updated before RC2 is out. Thanks for the heads up!
···
On 29 May 2013 10:23, Daniel Piddock wrote:
Hi Greg,
I’ve started playing around with the nightly packages under Wheezy. When
upgrading from a previous Squeeze install the foreman package fails to
install - it gets stuck building json as it needs mkmf from ruby-1.9.1-dev.
However the foreman package requires ruby-dev which is fulfilled by
ruby1.8-dev that was pulled in by my 1.1 install.
Would it be better to explicitly depend on ruby-1.9.1-dev for those of us
not installing on a fresh Wheezy?
