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.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
  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