Package: qgis-providers-common
Version: 2.0.1-1
Severity: serious
Usertags: piuparts


during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up qgis-providers-common (2.0.1-1) ...
  /usr/lib/qgis/crssync: error while loading shared libraries: 
cannot open shared object file: No such file or directory
  dpkg: error processing package qgis-providers-common (--configure):
   subprocess installed post-installation script returned error exit status 127
  Setting up libexpat1:amd64 (2.1.0-4) ...
  Setting up libquadmath0:amd64 (4.8.2-14) ...
  Setting up libgfortran3:amd64 (4.8.2-14) ...
  Setting up libblas3 (1.2.20110419-7) ...
  update-alternatives: using /usr/lib/libblas/ to provide 
/usr/lib/ ( in auto mode
  Setting up liblapack3 (3.5.0-2) ...
  update-alternatives: using /usr/lib/lapack/ to provide 
/usr/lib/ ( in auto mode

qgis-providers-common.postinst contains

    if [ "$1" = "configure" ] && [ -x /usr/lib/qgis/crssync ]; then

Looks like checking -x /usr/lib/qgis/crssync is not sufficient due to
libblas and liblapack using the alternatives system.
Since qgis-providers-common looks like a pure data package, adding
strict dependencies does not seem appropriate. So better use triggers
(in the package containing /usr/lib/qgis/crssync) that get activated
upon installation/upgrade of the qgis-providers-common package (by
declaring "interest" on the directories handled by crssync).



Attachment: qgis-mapserver_2.0.1-1.log.gz
Description: GNU Zip compressed data

Pkg-grass-devel mailing list

Reply via email to