Hi,
thank you for answering, actually i did but i guess the pinning got ignored at some point, the two files are still in their place btw.
I think i'll dump the db and start from scratch.
Best reguards, Marco Barbieri.
On 08/02/2018 09:30, Morten Brekkevold wrote:
On Tue, 6 Feb 2018 09:04:29 +0100 Marco Barbieri marco.barbieri@unimore.it wrote:
Hi,
Hi Marco,
i'm trying to re-install nav on debian 9 system, this machine has just been upgraded in place from jessie to stretch during the upgrade nav 4.6.x, that was installed, got discarded for the same error reported below: dependencies unmet, older versions seem required.
Did you read the installation instructions for Debian 9 at https://nav.uninett.no/install-instructions/#debian ?
As the instructions say:
| There are several software packages that NAV depend on, which are not | provided by Debian 9, or are provided in newer versions that are | backwards-incompatible (such as Django and related software). The APT | repository at nav.uninett.no provides these packages in the required | versions, but since some of the packages are available in newer | versions from Debian Stretch, you will experience problems with having | apt installing all the correct dependecies.
| This is the reason for the apt-pinning rule in the above recipe. It | will ensure that packages provided by nav.uninett.no will be preferred | over newer versions from Debian.
| By doing this, you will lose the benefits of Debian security patches | to these packages, and you may have issues installing other Debian | packages that depend on python-django. Proceeed at your own risk.
Which means you will need to give packages from nav.uninett.no priority in your APT configuration, as detailed in the instructions:
| sudo /bin/sh -c "cat > /etc/apt/preferences.d/nav.pref" <<EOF | # Give packages from nav.uninett.no higher priority, at your own risk | Package: * | Pin: origin nav.uninett.no | Pin-Priority: 600 | EOF | sudo apt-get update