NAV 3.4.1 is now available for download at SourceForge: http://sourceforge.net/projects/nav/
This is a bugfix release, the changelog is attached to this message.
Binary packages for Debian will be available soon. The Debian package is maintained by Morten Werner Forsbring, on commission from UNINETT.
We are currently working on migrating NAV from SourceForge.net to Launchpad.net; downloads and issue trackers will be available there once the migration is complete (a separate announcement will be made).
We are also working on complete rewrites of AlertEngine and AlertProfiles in Python, thereby ridding NAV entirely of PHP, and almost entirely of Perl. In the process we will also solve some of the basic problems that have plagued alert profiles and alert dispatching for a while. We are hoping to introduce these rewrites in NAV 3.5, scheduled for this fall.
Happy NAVing everyone!
Morten Brekkevold morten.brekkevold@uninett.no writes:
NAV 3.4.1 is now available for download at SourceForge: http://sourceforge.net/projects/nav/
This is a bugfix release, the changelog is attached to this message.
Binary packages for Debian will be available soon. The Debian package is maintained by Morten Werner Forsbring, on commission from UNINETT.
Hi,
the Debian package is ready. For new installations follow the instructions on the metanav- [1] or Alioth-pages [2]. For upgrades, just do
aptitude update && aptitude upgrade
You might need to do a 'dist-upgrade' to include a new dependency on python-psycopg2.
- Werner
On Tue, 29 Jul 2008 08:31:36 +0200 Morten Werner Forsbring werner@debian.org wrote:
the Debian package is ready. For new installations follow the instructions on the metanav- [1] or Alioth-pages [2]. For upgrades, just do
aptitude update && aptitude upgrade
You might need to do a 'dist-upgrade' to include a new dependency on python-psycopg2.
I would also like to point out that the SQL problems I posted about last week are fixed in this package, which means Debian users won't have to wait for a 3.4.2 release.
I don't know if this is a significant error, but I gett his error at the very end of the upgrade of NAV:
<snip>
E: Could not upgrade database scheme, so disabling NAV in /etc/default/nav. Please do manual upgrade, enable NAV in /etc/default/nav and restart it. Warning: RUN_NAV in /etc/default/nav is not set to 1. Please see /usr/share/doc/nav/README.Debian for details. Warning: RUN_NAV in /etc/default/nav is not set to 1. Please see /usr/share/doc/nav/README.Debian for details. /usr/lib/python2.4/site-packages/nav/web/arnoldhandler.py:0: SyntaxWarning: name 'manage' is assigned to before global declaration
luna:~#
</snip>
Am I the only one receiving this error while upgrading? Running the latest Debian STABLE build.
-Vidar S
-----Opprinnelig melding----- Fra: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sendt: 29. juli 2008 08:53 Til: nav-users@uninett.no Kopi: Morten Werner Forsbring Emne: Re: Announcement: NAV 3.4.1 released
On Tue, 29 Jul 2008 08:31:36 +0200 Morten Werner Forsbring werner@debian.org wrote:
the Debian package is ready. For new installations follow the instructions on the metanav- [1] or Alioth-pages [2]. For upgrades, just do
aptitude update && aptitude upgrade
You might need to do a 'dist-upgrade' to include a new dependency on python-psycopg2.
I would also like to point out that the SQL problems I posted about last week are fixed in this package, which means Debian users won't have to wait for a 3.4.2 release.
-- mvh Morten Brekkevold UNINETT
My upgrade using aptitude worked fine, except when restarting NAV since the "userpw_nav" variable in db.conf had been set to NULL. After copy/paste of the password from my old db.conf, all of NAV's services startet without problems.
- Fredrik
On Tue, Jul 29, 2008 at 09:33, Stokkenes Vidar Vidar.Stokkenes@hn-ikt.nowrote:
I don't know if this is a significant error, but I gett his error at the very end of the upgrade of NAV:
<snip>
E: Could not upgrade database scheme, so disabling NAV in /etc/default/nav. Please do manual upgrade, enable NAV in /etc/default/nav and restart it. Warning: RUN_NAV in /etc/default/nav is not set to 1. Please see /usr/share/doc/nav/README.Debian for details. Warning: RUN_NAV in /etc/default/nav is not set to 1. Please see /usr/share/doc/nav/README.Debian for details. /usr/lib/python2.4/site-packages/nav/web/arnoldhandler.py:0: SyntaxWarning: name 'manage' is assigned to before global declaration
luna:~#
</snip>
Am I the only one receiving this error while upgrading? Running the latest Debian STABLE build.
-Vidar S
-----Opprinnelig melding----- Fra: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sendt: 29. juli 2008 08:53 Til: nav-users@uninett.no Kopi: Morten Werner Forsbring Emne: Re: Announcement: NAV 3.4.1 released
On Tue, 29 Jul 2008 08:31:36 +0200 Morten Werner Forsbring < werner@debian.org> wrote:
the Debian package is ready. For new installations follow the instructions on the metanav- [1] or Alioth-pages [2]. For upgrades, just do
aptitude update && aptitude upgrade
You might need to do a 'dist-upgrade' to include a new dependency on python-psycopg2.
I would also like to point out that the SQL problems I posted about last week are fixed in this package, which means Debian users won't have to wait for a 3.4.2 release.
-- mvh Morten Brekkevold UNINETT
On Tue, 29 Jul 2008 09:50:05 +0200 "Fredrik Holmberg" fredrik.holmberg@gmail.com wrote:
My upgrade using aptitude worked fine, except when restarting NAV since the "userpw_nav" variable in db.conf had been set to NULL. After copy/paste of the password from my old db.conf, all of NAV's services startet without problems.
That would only have happened if you answered yes when asked to replace the old db.conf. You shouldn't uncritically overwrite locally modified configuration files when apt asks (which is why it's default answer is No), you should inspect the changes first.
On Tue, 29 Jul 2008 09:33:15 +0200 Stokkenes Vidar Vidar.Stokkenes@hn-ikt.no wrote:
I don't know if this is a significant error, but I gett his error at the very end of the upgrade of NAV:
<snip>
E: Could not upgrade database scheme, so disabling
This is significant, yes. This means the package was unable to upgrade your database schema (i.e. the SQL fixes that I mentioned in an earlier post).
NAV in /etc/default/nav. Please do manual upgrade, enable NAV in /etc/default/nav and restart it.
The package has disabled your NAV installation, awaiting a manual schema upgrade by you.
See /usr/share/doc/nav/sql/upgrades/3.4.2.sql. Try to follow the instructions and run this manually, see what errors you get, if any (Which, I guess, is basically the instructions given in README.Debian, referred to in your error output).
/usr/lib/python2.4/site-packages/nav/web/arnoldhandler.py:0: SyntaxWarning: name 'manage' is assigned to before global declaration
This is a negligible warning. It's been there since 3.4.0, and will be fixed later.
Stokkenes Vidar Vidar.Stokkenes@hn-ikt.no writes:
I don't know if this is a significant error, but I gett his error at the very end of the upgrade of NAV:
<snip>
E: Could not upgrade database scheme, so disabling NAV in /etc/default/nav. Please do manual upgrade, enable NAV in /etc/default/nav and restart it. Warning: RUN_NAV in /etc/default/nav is not set to 1. Please see /usr/share/doc/nav/README.Debian for details. Warning: RUN_NAV in /etc/default/nav is not set to 1. Please see /usr/share/doc/nav/README.Debian for details. /usr/lib/python2.4/site-packages/nav/web/arnoldhandler.py:0: SyntaxWarning: name 'manage' is assigned to before global declaration
luna:~#
</snip>
Am I the only one receiving this error while upgrading? Running the latest Debian STABLE build.
Hi,
which version did you upgrade from?
- Werner
-
Fredrik Holmberg -
Morten Brekkevold -
Morten Werner Forsbring -
Stokkenes Vidar