(Apologies for cross-posting, I thought both groups would be interested in this)
Hi all,
Just a quick heads up to let everyone know that the Debian packages
have a new maintainer. Tonight I will be getting the foreman_proxy
nightly package building again, as that's quite simple to get working.
A nightly for the main foreman package will follow once I have the
bundler issues sorted. After that, we'll be looking towards getting
some release candidate packages up for the testing repository.
I'd like to thank @joschi for his work on the Debian packages up until
now, and personally for helping me get the package build environment
set up 
Cheers,
Greg
> (Apologies for cross-posting, I thought both groups would be interested in this)
>
> Hi all,
>
> Just a quick heads up to let everyone know that the Debian packages
> have a new maintainer. Tonight I will be getting the foreman_proxy
> nightly package building again, as that's quite simple to get working.
> A nightly for the main foreman package will follow once I have the
> bundler issues sorted. After that, we'll be looking towards getting
> some release candidate packages up for the testing repository.
>
> I'd like to thank @joschi for his work on the Debian packages up until
> now, and personally for helping me get the package build environment
> set up
I'll just want to take this opportunity to thank Joschi for his great
help in the last couple of years!
Greg - good luck 
Ohad
···
On 04/20/2012 11:36 PM, Greg Sutcliffe wrote:
>
> Cheers,
> Greg
>
Thanks Ohad
The foreman-proxy nightly should be live now, and the foreman nightly
will start tonight. I'll be checking tomorrow that the repo updates
correctly, but all should be well.
This first cut of the foreman nightly package is very ugly - it
installs a lot of unnecessary stuff, including support for all 3
databases and libvirt, and a ton of other stuff. That said, it does
seem to produce a working sqlite-based foreman install. If you want to
run against a separate db, you should be able to edit the config
appropriately. I have a lot more work to do on the package to get it
where it needs to be, but the opensource way is "release early,
release often" so, here it is, in all it's (horrible) glory
Some caveats:
- The init script doesn't work yet, you'll need to run
"RAILS_ENV=production bundle exec rails s" in /usr/share/foreman.
(This is my next priority to fix :P)
- The foreman-{mysql,pslq,sqlite} are not presently working, so don't
try those just yet (although I have plans for them).
If the adventurous / reckless members of the community want to have a
play, please do. Feel free to file bugs under Packaging and assign
them to me, or to drop me a mail on the foreman-dev list (or even poke
@gwmngilfen on IRC).
I'm going to stop cross-posting to both lists from here on - further
discussion of the nightlies will be on foreman-dev.
Enjoy
Greg
···
On 22 April 2012 11:45, Ohad Levy wrote:
> Greg - good luck ;)
This is (hopefully) fixed - the init script works for me for all
actions. I've also fixed a bug in apt-get remove foreman which
prevented the pacakge from uninstalling. This should hit the repo
tonight.
Greg
···
On 22 April 2012 19:37, Greg Sutcliffe wrote:
> - The init script doesn't work yet, you'll need to run
> "RAILS_ENV=production bundle exec rails s" in /usr/share/foreman.
