Jürgen E. Fischer wrote:
Nope, I was probably wrong. The package from archive is considered in apt-get rdepends, although it wouldn't be installed. So that doesn't tell us which actually is the package that triggers the dependency.It might still be the or dependency in qgis-plugin-grass, if the dependencies are processed in order and libgdal1-1.6.0-grass is not installed already. I reversed the dependencies for 1.3.0. BTW dpkg -l libgdal1-1.5.0-grass to check whether or not the package is installed.
Done: $ dpkg -l libgdal1-1.5.0-grass Desired=Unknown/Install/Remove/Purge/Hold| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description +++-==============-==============-============================================ pn libgdal1-1.5.0 <none> (no description available)Anyway, everything is back to normality after the upgrade to qgis 1.2.0-2~jaunty1build1
and ligdal1-1.6.0-grass 1.6.0-3~jaunty1 Thanks, Agus
<<attachment: alobolistas.vcf>>
_______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user