Hello all,
I'm trying to install nav on ubuntu 9.04 and this fails cause of 2 (only 2) dependency failures. a) python < 2.5. 9.04 has python 2.6. b) postgress = 8.1. Ubuntu has postgres 8.3
Is it necessary to pin these 2 dependency versions ? I have knowledge of python but I'd assume that 2.6 is good enough against 2.5 source code. Same goes for postgres
Correct me if I'm wrong. In the mean time I'l try to force install nav.
btw, seems VERY promising.
thx all vassilis
On Thu, 12 Nov 2009 17:40:10 +0100 (CET) vvatikiotis@gmail.com wrote:
Hello all,
I'm trying to install nav on ubuntu 9.04 and this fails cause of 2 (only 2) dependency failures. a) python < 2.5. 9.04 has python 2.6. b) postgress = 8.1. Ubuntu has postgres 8.3
Is it necessary to pin these 2 dependency versions ? I have knowledge of python but I'd assume that 2.6 is good enough against 2.5 source code. Same goes for postgres
This is not necessary for NAV, but the Debian package itself only supports python 2.4 (it installs library modules directly to /usr/lib/python2.4/...).
I'm not sure whether the package contains any specific dependency to PostgreSQL 8.1, but NAV works fine on 8.3 for us.
Morten Werner Forsbring (the Debian package maintainer) is currently working on a revised package for Debian Lenny, but I'm not up-to-date on the status of this work. Care to comment, Werner?
Correct me if I'm wrong. In the mean time I'l try to force install nav.
Since the python libraries are only installed for python 2.4, you will likely have problems finding the libraries when running python 2.5, unless you change your python 2.5 library search path. You may be able to make it work by appending the correct directory to sys.path in /etc/python2.5/sitecustomize.py .
btw, seems VERY promising.
Thanks :)
Morten Brekkevold morten.brekkevold@uninett.no writes:
I'm trying to install nav on ubuntu 9.04 and this fails cause of 2 (only 2) dependency failures. a) python < 2.5. 9.04 has python 2.6. b) postgress = 8.1. Ubuntu has postgres 8.3
Is it necessary to pin these 2 dependency versions ? I have knowledge of python but I'd assume that 2.6 is good enough against 2.5 source code. Same goes for postgres.
This is not necessary for NAV, but the Debian package itself only supports python 2.4 (it installs library modules directly to /usr/lib/python2.4/...).
I'm not sure whether the package contains any specific dependency to PostgreSQL 8.1, but NAV works fine on 8.3 for us.
Morten Werner Forsbring (the Debian package maintainer) is currently working on a revised package for Debian Lenny, but I'm not up-to-date on the status of this work. Care to comment, Werner?
I think the package for Lenny is ready, but I miss an hour or so to document and test the upgrade path from Etch a few more times (pg_upgradecluster does not preserve per database configuration parameters, ref. [1]).
So please try this apt-source (which supports more versions of Python and PostgreSQL 8.3):
deb http://pkg-nav.alioth.debian.org/debian lenny-test local
The package will be moved to the lenny-archive on pkg-nav.alioth.debian.org when documentation after _some_ more testing (will be announced on nav-users).
- Werner
so many cheers!
vassilis
2009/11/16 Morten Werner Forsbring werner@debian.org:
Morten Brekkevold morten.brekkevold@uninett.no writes:
I'm trying to install nav on ubuntu 9.04 and this fails cause of 2 (only 2) dependency failures. a) python < 2.5. 9.04 has python 2.6. b) postgress = 8.1. Ubuntu has postgres 8.3
Is it necessary to pin these 2 dependency versions ? I have knowledge of python but I'd assume that 2.6 is good enough against 2.5 source code. Same goes for postgres.
This is not necessary for NAV, but the Debian package itself only supports python 2.4 (it installs library modules directly to /usr/lib/python2.4/...).
I'm not sure whether the package contains any specific dependency to PostgreSQL 8.1, but NAV works fine on 8.3 for us.
Morten Werner Forsbring (the Debian package maintainer) is currently working on a revised package for Debian Lenny, but I'm not up-to-date on the status of this work. Care to comment, Werner?
I think the package for Lenny is ready, but I miss an hour or so to document and test the upgrade path from Etch a few more times (pg_upgradecluster does not preserve per database configuration parameters, ref. [1]).
So please try this apt-source (which supports more versions of Python and PostgreSQL 8.3):
deb http://pkg-nav.alioth.debian.org/debian lenny-test local
The package will be moved to the lenny-archive on pkg-nav.alioth.debian.org when documentation after _some_ more testing (will be announced on nav-users).
- Werner
Morten Werner Forsbring werner@debian.org writes:
I think the package for Lenny is ready, but I miss an hour or so to document and test the upgrade path from Etch a few more times (pg_upgradecluster does not preserve per database configuration parameters, ref. [1]).
So please try this apt-source (which supports more versions of Python and PostgreSQL 8.3):
deb http://pkg-nav.alioth.debian.org/debian lenny-test local
The package will be moved to the lenny-archive on pkg-nav.alioth.debian.org when documentation after _some_ more testing (will be announced on nav-users).
The package was moved to the lenny-archive before christmans, but the announcement was forgotten. Sorry about that. :/
Anyway Uninett have started using the packages in the lenny-archives, so if you do not want to use my test-packages, please move to the following archive:
deb http://pkg-nav.alioth.debian.org/debian lenny local
The upgrade path is documented here:
http://pkg-nav.alioth.debian.org/upgrade-path-etch-lenny.html
Please send feedback to this list or directly to me.
- Werner
-
Morten Brekkevold -
Morten Werner Forsbring -
Vassilis Vatikiotis -
vvatikiotis＠gmail.com