Home
The Toolkit for Online Communities
16689 Community Members, 1 member online, 2111 visitors today
Log In Register
OpenACS Home : Forums : OpenACS Q&A : Debian Installer Update (openacs 5.4.3 debian/ubuntu packages released) : One Message

Forum OpenACS Q&A: Re: Debian Installer Update (openacs 5.4.3 debian/ubuntu packages released)

Hi Frank,

The package is not intended to be used on the stable distribution as you are doing, that's why you are having a painly install experience, it's not a package/age problem.

First of all, I don't think it's a good idea to have a stable/etch-backport/testing system mix.
Some openacs dependencies, like tdom 0.8.3, need a version of the libc6 more recent than the etch version, so you'll have a testing system even if you want it or not.

Also, this configuration has the problem of having to increase the size of apt cache to contain all the packages of the three repositories. I bet that the TCLLIBPATH problem is related to that config too, I have never seen it on lenny installations.

Finally, there is no need to add the compatibility options on postgresql.conf, the installer sets this options directly on the openacs database.

Cheers,
Héctor Romojaro

Frank,

The Debian distribution targeted is mentioned prominently at the wiki page:


"[...] Beware, our packaging activity explicitly targets Debian GNU/Linux unstable ("sid") [...]"

If you plan to support stable, it would be a valuable contribution (by ]project-open[) to provide for official backports from unstable to stable (rather than documenting a "stable/etch-backport/testing system mix, as correctly hinted at by Héctor).

//stefan

Geez a mix like that's going to be just a bit of a maintenance headache ...

The decision to choose one debian version that supports the packages we need is the correct one.

Well, there are actually three strategies available for supporting Debian distributions other than unstable:

1. official backports, contributed to www.backports.org or www.apt-get.org

2. non-official backports in a self-maintained deb repository

3. a "disciplined" mix-and-match strategy using http://wiki.debian.org/AptPinning

just to clarify possible ways of action for Frank and ]project-open[ ...

//stefan

Hi Héctor,

> "[...] Beware, our packaging activity explicitly targets
> Debian GNU/Linux unstable ("sid") [...]"

Good point, I read over this.

And (I've said that this is the first time I'm really starting with Debian, didn't I?) I had no idea that I was setting up a "mixed" system.

And just taking this "novice" route - could somebody please point me to a place where I can download a suitable "sid" cdroom image? I've check the www.debian.org now for at least 10 minutes and didn't find anything...

I think that this would also be a wonderful extension for your http://openacs.com/xowiki/debian page...

Keep up the good work and thanks for the patience guys!
Frank

Frank,


And just taking this "novice" route - could somebody please point me to a place where I can download a suitable "sid" cdroom image? I've check the www.debian.org now for at least 10 minutes and didn't find anything...

There are no distribution images for the unstable/"sid" branch, see http://www.debian.org/CD/faq/#unstable-images.

You have to get a testing/"lenny" installation (released daily and is checked for its soundness and installability), see http://www.debian.org/devel/debian-installer/. Select the appropriate "netinst" platform variant, then proceed with a raw installation. Then:

1. update your sources.list for the deb package manager (basically substituting "testing" occurrences for "unstable").

2. call "apt-get dist-upgrade"

3. your system will upgrade and will so track unstable

However, for production use, Dave Bauer's hint at the ubuntu server installation (preferably the long-time support LTS version 8.04) is the way to go: you get the advantage of an assembled and checked debian unstable, our packages, and security fixes through 2013.

//stefan