Announcement: NAV 3.5.0 released
NAV 3.5.0 is now available for download at Launchpad: https://launchpad.net/nav/3.5/3.5.0 This is the first stable release of the 3.5 series; the changelog is attached to this message. Binary packages for Debian will be available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission
From UNINETT.
For those upgrading from 3.5.0b3, there are no database changes. If you wish to upgrade directly from NAV 3.4 to this version, the beta releases' SQL upgrade scripts have been merged into a single 3.5.0.sql script, which needs to be run. Please read the upgrade instructions carefully, as the previous four NAV databases need to be merged into a single one. Happy NAVing everyone! -- mvh Morten Brekkevold UNINETT
On Thu, 22 Jan 2009 08:58:24 +0100 Morten Brekkevold <morten.brekkevold@uninett.no> wrote:
NAV 3.5.0 is now available for download at Launchpad: https://launchpad.net/nav/3.5/3.5.0
This is the first stable release of the 3.5 series; the changelog is attached to this message.
In my eager to announce this release, I forgot to actually attach the changelog and release notes :-P Trying again... -- mvh Morten Brekkevold UNINETT
On Thu, Jan 22, 2009 at 09:05:20AM +0100, Morten Brekkevold wrote:
Before running the normal SQL upgrade procedure (i.e. SQL scripts from doc/sql/upgrades/), you MUST merge your four existing NAV databases into a single nav database. The shell script doc/sql/mergedb.sh can help you with this. Se doc/sql/upgrades/README for more information.
Hi again :) So we upgraded nav, and before running the sql script we tried to run the merge script, and it seems to fail because it thinks there already is a database called nav: postgres@nwtraffic:/usr/share/doc/nav/sql$ sh mergedb.sh Creating database nav, owned by nav createdb: database creation failed: ERROR: database "nav" already exists We are currently on v3.4.3. The updates seemed to go OK otherwise, with the django stuff and the new db.conf, etc. Thanks for any tips... Tim
On Mon, 23 Feb 2009 15:27:58 +0000 Tim Chown <tjc@ecs.soton.ac.uk> wrote:
Hi again :)
So we upgraded nav, and before running the sql script we tried to run the merge script, and it seems to fail because it thinks there already is a database called nav:
postgres@nwtraffic:/usr/share/doc/nav/sql$ sh mergedb.sh Creating database nav, owned by nav createdb: database creation failed: ERROR: database "nav" already exists
Hi Tim, Why did you try to do this manually? Did the Debian package not fix this for you already? It's easy to list the existing databases: sudo -u postgres psql -l -- mvh Morten Brekkevold UNINETT
On Wed, Feb 25, 2009 at 08:36:37AM +0100, Morten Brekkevold wrote:
On Mon, 23 Feb 2009 15:27:58 +0000 Tim Chown <tjc@ecs.soton.ac.uk> wrote:
Hi again :)
So we upgraded nav, and before running the sql script we tried to run the merge script, and it seems to fail because it thinks there already is a database called nav:
postgres@nwtraffic:/usr/share/doc/nav/sql$ sh mergedb.sh Creating database nav, owned by nav createdb: database creation failed: ERROR: database "nav" already exists
Hi Tim,
Why did you try to do this manually? Did the Debian package not fix this for you already?
Hmmm. I guess the cause of my confusion (and the possible mistake) is that I read the new README notes and these talk about the upgrade script and running the merge, etc. Hindsight of course makes thing easy, but I guess I was trying to be too diligent in reading the upgrade notes and your mail on 22nd Jan about the new v3.5 release and not realising that your debian package simply does it all. Having re-read your mail of 18th Feb I see this now ("For the automatically database upgrade to complete successfully you need to..."). I think the info from the first release notes were stuck in my mind as something important to do. Having fixed up the apache config all now seems well. We'll give it a whirl and send any feedback as usual. Sometimes it pays not to think too much it seems :) Thanks again, -- Tim
On Wed, 25 Feb 2009 11:10:32 +0000 Tim Chown <tjc@ecs.soton.ac.uk> wrote:
new v3.5 release and not realising that your debian package simply does it all. Having re-read your mail of 18th Feb I see this now ("For the automatically database upgrade to complete successfully you need to...").
That was Morten Werner, not me :)
I think the info from the first release notes were stuck in my mind as something important to do.
Having fixed up the apache config all now seems well. We'll give it a whirl and send any feedback as usual.
Glad it works! We expect the first bugfix release to come next week, in response to some of the initial issues people have had with 3.5.0. -- mvh Morten Brekkevold UNINETT
That is indeed good news! When can we expect a debian release, Werner? :-) Best regards, Vidar S -----Opprinnelig melding----- Fra: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sendt: 22. januar 2009 08:58 Til: nav-users@uninett.no Emne: Announcement: NAV 3.5.0 released NAV 3.5.0 is now available for download at Launchpad: https://launchpad.net/nav/3.5/3.5.0 This is the first stable release of the 3.5 series; the changelog is attached to this message. Binary packages for Debian will be available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission From UNINETT. For those upgrading from 3.5.0b3, there are no database changes. If you wish to upgrade directly from NAV 3.4 to this version, the beta releases' SQL upgrade scripts have been merged into a single 3.5.0.sql script, which needs to be run. Please read the upgrade instructions carefully, as the previous four NAV databases need to be merged into a single one. Happy NAVing everyone! -- mvh Morten Brekkevold UNINETT
No pressure on Werner at all :) I guess the extra dependency changes will add a little delay, so we need to be patient. The notes look good, looking forward to trying it out. Presumbly there's just a one-off schema fix coming from 3.4.3, and the files that 'should' be removed need to be handled manually. Tim On Thu, Jan 22, 2009 at 09:26:37AM +0100, Stokkenes Vidar wrote:
That is indeed good news!
When can we expect a debian release, Werner? :-)
Best regards,
Vidar S
-----Opprinnelig melding----- Fra: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sendt: 22. januar 2009 08:58 Til: nav-users@uninett.no Emne: Announcement: NAV 3.5.0 released
NAV 3.5.0 is now available for download at Launchpad: https://launchpad.net/nav/3.5/3.5.0
This is the first stable release of the 3.5 series; the changelog is attached to this message.
Binary packages for Debian will be available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission From UNINETT.
For those upgrading from 3.5.0b3, there are no database changes. If you wish to upgrade directly from NAV 3.4 to this version, the beta releases' SQL upgrade scripts have been merged into a single 3.5.0.sql script, which needs to be run. Please read the upgrade instructions carefully, as the previous four NAV databases need to be merged into a single one.
Happy NAVing everyone!
-- mvh Morten Brekkevold UNINETT
-- Tim
Stokkenes Vidar <Vidar.Stokkenes@hn-ikt.no> writes:
NAV 3.5.0 is now available for download at Launchpad: https://launchpad.net/nav/3.5/3.5.0
This is the first stable release of the 3.5 series; the changelog is attached to this message.
Binary packages for Debian will be available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission From UNINETT.
That is indeed good news!
When can we expect a debian release, Werner? :-)
Hi, and sorry for the delay. A 3.5.0-package is now present in the etch archive. There are two things you should be aware of: * For the automatically database upgrade to complete successfully you need to copy the password for the nav-user from /etc/nav/db.conf to /etc/nav/db.conf.dpkg-new when the upgrade process asks about replaceing the db.conf with a new upstream version. More information about this should be printed in a dialog-box early in the upgrade process. * You now need backports.org-archive in your /etc/apt/sources.list for the python-django dependency: deb http://backports.org/debian etch-backports main Please ask if you have questions, and I'll try my best to answer them. - Werner
Morten Werner Forsbring <werner@debian.org> writes:
and sorry for the delay. A 3.5.0-package is now present in the etch archive. There are two things you should be aware of:
* For the automatically database upgrade to complete successfully you need to copy the password for the nav-user from /etc/nav/db.conf to /etc/nav/db.conf.dpkg-new when the upgrade process asks about replaceing the db.conf with a new upstream version. More information about this should be printed in a dialog-box early in the upgrade process.
* You now need backports.org-archive in your /etc/apt/sources.list for the python-django dependency:
deb http://backports.org/debian etch-backports main
Please ask if you have questions, and I'll try my best to answer them.
I forgot one more thing. The webpages are moved from /var/www/nav/ to /usr/share/nav/htdocs/. This means that the Apache config must be changed. The easiest is to remove the /etc/apache2/conf.d/nav file or where you placed the apache config, and run 'a2ensite nav-default'. If you want to do it even more careful, copy /etc/apache2/sites-available/nav-default to e.g. /etc/apach2/sites-available/nav-local, modify it for your needs (perhaps even with SSL?) and run 'a2ensite nav-local'. :) - Werner
This might just be me on an early thursday, but I can`t seem to find nav under the available packages for update when I run "apt-get upgrade" (after update ofcourse) I got the following lines in my /etc/apt/sources.lst related to NAV: # NAV deb http://pkg-nav.alioth.debian.org/debian etch local deb http://backports.org/debian etch-backports main Am I doing something wrong this time? -Vidar ________________________________________ From: Morten Werner Forsbring [werner@debian.org] Sent: Wednesday, February 18, 2009 11:38 PM To: nav-users@uninett.no Subject: Re: Announcement: NAV 3.5.0 released Morten Werner Forsbring <werner@debian.org> writes:
and sorry for the delay. A 3.5.0-package is now present in the etch archive. There are two things you should be aware of:
* For the automatically database upgrade to complete successfully you need to copy the password for the nav-user from /etc/nav/db.conf to /etc/nav/db.conf.dpkg-new when the upgrade process asks about replaceing the db.conf with a new upstream version. More information about this should be printed in a dialog-box early in the upgrade process.
* You now need backports.org-archive in your /etc/apt/sources.list for the python-django dependency:
deb http://backports.org/debian etch-backports main
Please ask if you have questions, and I'll try my best to answer them.
I forgot one more thing. The webpages are moved from /var/www/nav/ to /usr/share/nav/htdocs/. This means that the Apache config must be changed. The easiest is to remove the /etc/apache2/conf.d/nav file or where you placed the apache config, and run 'a2ensite nav-default'. If you want to do it even more careful, copy /etc/apache2/sites-available/nav-default to e.g. /etc/apach2/sites-available/nav-local, modify it for your needs (perhaps even with SSL?) and run 'a2ensite nav-local'. :) - Werner
On Thu, 19 Feb 2009 11:21:16 +0100 Stokkenes Vidar <Vidar.Stokkenes@hn-ikt.no> wrote:
This might just be me on an early thursday, but I can`t seem to find nav under the available packages for update when I run "apt-get upgrade" (after update ofcourse)
I got the following lines in my /etc/apt/sources.lst related to NAV:
# NAV deb http://pkg-nav.alioth.debian.org/debian etch local deb http://backports.org/debian etch-backports main
Am I doing something wrong this time?
I have no problems finding the nav package when using the first of those two lines in my sources.list. Are you sure you did a proper update first? -- mvh Morten Brekkevold UNINETT
You are indeed right. Actually my Debian installation is keeping back my package for whatever reason.. Neither "apt-get upgrade" or "apt-get dist-upgrade" wants to update the package. Any idea why? -Vidar -----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: 19. februar 2009 16:00 To: Stokkenes Vidar Cc: nav-users@uninett.no Subject: Re: Announcement: NAV 3.5.0 released On Thu, 19 Feb 2009 11:21:16 +0100 Stokkenes Vidar <Vidar.Stokkenes@hn-ikt.no> wrote:
This might just be me on an early thursday, but I can`t seem to find nav under the available packages for update when I run "apt-get upgrade" (after update ofcourse)
I got the following lines in my /etc/apt/sources.lst related to NAV:
# NAV deb http://pkg-nav.alioth.debian.org/debian etch local deb http://backports.org/debian etch-backports main
Am I doing something wrong this time?
I have no problems finding the nav package when using the first of those two lines in my sources.list. Are you sure you did a proper update first? -- mvh Morten Brekkevold UNINETT
Stokkenes Vidar wrote:
You are indeed right.
Actually my Debian installation is keeping back my package for whatever reason.. Neither "apt-get upgrade" or "apt-get dist-upgrade" wants to update the package.
Any idea why?
When doing this on a new system I had a conflict with some package (can't remember which), but it work when issuing "aptitude install nav", try using aptitude instead of apt-get as it seems to be 'smarter' in some cases. -- Erik
On Fri, 20 Feb 2009 11:58:23 +0100 Erik Weber <twiztar@gmail.com> wrote:
When doing this on a new system I had a conflict with some package (can't remember which), but it work when issuing "aptitude install nav", try using aptitude instead of apt-get as it seems to be smarter' in some cases.
Actually, Debian recommends using aptitude for all package management, as a replacement for apt-get. Aptitude knows whether a package has been deliberately installed by you, or just pulled in as a dependency on another package. This means that it is also able to automatically remove unused dependencies as other packages are removed. -- mvh Morten Brekkevold UNINETT
On Fri, Feb 20, 2009 at 11:58:23AM +0100, Erik Weber wrote:
Stokkenes Vidar wrote:
You are indeed right.
Actually my Debian installation is keeping back my package for whatever reason.. Neither "apt-get upgrade" or "apt-get dist-upgrade" wants to update the package.
Any idea why?
When doing this on a new system I had a conflict with some package (can't remember which), but it work when issuing "aptitude install nav", try using aptitude instead of apt-get as it seems to be 'smarter' in some cases.
Hi, We've just tried to run the aptitude upgrade on our NAV server and hit an error (or two). Here is our sources: # cat sources.list # # deb cdrom:[Debian GNU/Linux 4.0 r3 _Etch_ - Official i386 NETINST Binary-1 20080218-14:15]/ etch contrib main # deb cdrom:[Debian GNU/Linux 4.0 r3 _Etch_ - Official i386 NETINST Binary-1 20080218-14:15]/ etch contrib main deb http://debian.man.ac.uk/debian/ etch main deb-src http://debian.man.ac.uk/debian/ etch main deb http://mirror.ox.ac.uk/debian/ stable main deb-src http://mirror.ox.ac.uk/debian/ stable main deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib # TJC 12/08/08 Added NAV source (see http://pkg-nav.alioth.debian.org/) deb http://pkg-nav.alioth.debian.org/debian/ etch local deb http://ftp.no.debian.org/debian/ etch main non-free # TJC 23/02/09 Added for Nav 3.5.0 deb http://backports.org/debian etch-backports main And here is the output of the update: nwtraffic:/etc/apt# aptitude update Ign http://pkg-nav.alioth.debian.org etch Release.gpg Ign http://pkg-nav.alioth.debian.org etch Release Ign http://pkg-nav.alioth.debian.org etch/local Packages/DiffIndex Get:1 http://debian.man.ac.uk etch Release.gpg [386B] Get:2 http://pkg-nav.alioth.debian.org etch/local Packages [2905B] Get:3 http://debian.man.ac.uk etch Release [58.2kB] Get:4 http://ftp.no.debian.org etch Release.gpg [386B] Get:5 http://backports.org etch-backports Release.gpg [189B] Get:6 http://security.debian.org etch/updates Release.gpg [189B] Get:7 http://mirror.ox.ac.uk stable Release.gpg [386B] Get:8 http://ftp.no.debian.org etch Release [58.2kB] Get:9 http://mirror.ox.ac.uk stable Release [63.2kB] Get:10 http://backports.org etch-backports Release [72.8kB] Ign http://debian.man.ac.uk etch/main Packages/DiffIndex Ign http://debian.man.ac.uk etch/main Sources/DiffIndex Get:11 http://security.debian.org etch/updates Release [37.6kB] Ign http://mirror.ox.ac.uk stable/main Packages/DiffIndex Ign http://backports.org etch-backports Release Ign http://mirror.ox.ac.uk stable/main Sources/DiffIndex Get:12 http://mirror.ox.ac.uk stable/main Packages [6909kB] Get:13 http://backports.org etch-backports/main Packages [547kB] Ign http://ftp.no.debian.org etch/main Packages/DiffIndex Get:14 http://debian.man.ac.uk etch/main Packages [5620kB] Ign http://ftp.no.debian.org etch/non-free Packages/DiffIndex Get:15 http://ftp.no.debian.org etch/main Packages [5620kB] Ign http://security.debian.org etch/updates/main Packages/DiffIndex Ign http://security.debian.org etch/updates/contrib Packages/DiffIndex Ign http://security.debian.org etch/updates/main Sources/DiffIndex Ign http://security.debian.org etch/updates/contrib Sources/DiffIndex Get:16 http://security.debian.org etch/updates/main Packages [404kB] Hit http://security.debian.org etch/updates/contrib Packages Get:17 http://security.debian.org etch/updates/main Sources [62.8kB] Hit http://security.debian.org etch/updates/contrib Sources Get:18 http://mirror.ox.ac.uk stable/main Sources [2978kB] Get:19 http://debian.man.ac.uk etch/main Sources [1656kB] Get:20 http://ftp.no.debian.org etch/non-free Packages [102kB] Fetched 24.2MB in 13s (1831kB/s) Reading package lists... Error! W: There is no public key available for the following key IDs: 4D270D06F42584E6 W: GPG error: http://backports.org etch-backports Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EA8E8B2116BA136C E: Dynamic MMap ran out of room E: Error occurred while processing wmcdplay (NewVersion1) E: Problem with MergeList /var/lib/apt/lists/mirror.ox.ac.uk_debian_dists_stable_main_binary-i386_Packages E: The package lists or status file could not be parsed or opened. E: Couldn't rebuild package cache The public key warning is a warning, but there are hard errors after that. Is our source list appropriate or do we need some changes? Or is it some aptitude config elsewhere that needs changing or do we need to flush out the cache we have built up over time (the 'clean' option)? As you can probably tell, I'm not an aptitude guru. Thanks! -- Tim
Tim Chown wrote:
On Fri, Feb 20, 2009 at 11:58:23AM +0100, Erik Weber wrote:
Stokkenes Vidar wrote:
You are indeed right.
Actually my Debian installation is keeping back my package for whatever reason.. Neither "apt-get upgrade" or "apt-get dist-upgrade" wants to update the package.
Any idea why?
When doing this on a new system I had a conflict with some package (can't remember which), but it work when issuing "aptitude install nav", try using aptitude instead of apt-get as it seems to be 'smarter' in some cases.
Hi,
We've just tried to run the aptitude upgrade on our NAV server and hit an error (or two).
Here is our sources:
# cat sources.list # # deb cdrom:[Debian GNU/Linux 4.0 r3 _Etch_ - Official i386 NETINST Binary-1 20080218-14:15]/ etch contrib main
# deb cdrom:[Debian GNU/Linux 4.0 r3 _Etch_ - Official i386 NETINST Binary-1 20080218-14:15]/ etch contrib main
deb http://debian.man.ac.uk/debian/ etch main deb-src http://debian.man.ac.uk/debian/ etch main
deb http://mirror.ox.ac.uk/debian/ stable main deb-src http://mirror.ox.ac.uk/debian/ stable main
deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib
# TJC 12/08/08 Added NAV source (see http://pkg-nav.alioth.debian.org/) deb http://pkg-nav.alioth.debian.org/debian/ etch local deb http://ftp.no.debian.org/debian/ etch main non-free
# TJC 23/02/09 Added for Nav 3.5.0 deb http://backports.org/debian etch-backports main
That's a whole lot of sources... Most likely you can narrow it down to something like this: deb http://debian.man.ac.uk/debian/ etch main non-free contrib deb-src http://debian.man.ac.uk/debian/ etch main non-free contrib deb http://security.debian.org/ etch/updates main contrib non-free deb-src http://security.debian.org/ etch/updates main contrib # TJC 12/08/08 Added NAV source (see http://pkg-nav.alioth.debian.org/) deb http://pkg-nav.alioth.debian.org/debian/ etch local deb http://backports.org/debian etch-backports main aptitude clean aptitude update aptitude install debian-backports-keyring -- Erik
On Mon, Feb 23, 2009 at 03:49:34PM +0100, Erik Weber wrote:
That's a whole lot of sources... Most likely you can narrow it down to something like this:
deb http://debian.man.ac.uk/debian/ etch main non-free contrib deb-src http://debian.man.ac.uk/debian/ etch main non-free contrib
deb http://security.debian.org/ etch/updates main contrib non-free deb-src http://security.debian.org/ etch/updates main contrib
# TJC 12/08/08 Added NAV source (see http://pkg-nav.alioth.debian.org/) deb http://pkg-nav.alioth.debian.org/debian/ etch local deb http://backports.org/debian etch-backports main
aptitude clean aptitude update aptitude install debian-backports-keyring
Seems to have worked a treat, thanks Erik for the swift and helpful reply :) -- Tim
On Fri, 20 Feb 2009 11:42:55 +0100 Stokkenes Vidar <Vidar.Stokkenes@hn-ikt.no> wrote:
You are indeed right.
Actually my Debian installation is keeping back my package for whatever reason.. Neither "apt-get upgrade" or "apt-get dist-upgrade" wants to update the package.
Any idea why?
What is the output from command apt-get policy nav ? - Vegard V -
participants (6)
-
Erik Weber -
Morten Brekkevold -
Morten Werner Forsbring -
Stokkenes Vidar -
Tim Chown -
Vegard Vesterheim