On 02/10/2014 12:08 AM, Andreas Beckmann wrote:
> On 2014-02-09 22:52, Sebastiaan Couwenberg wrote:
>> When I upgrade the the qgis 2.0.1-1 packages currently in unstable to
>> 2.0.1-2 from my local repo the triggers are never run.
> I'll take a look.
> Is the debdiff you sent also already in git somewhere? That would make
> it easier for me to experiment.

Yes, the changes are in my personal git repo for the time being.

I heavily rebase this repo before pushing the changes to Alioth, so it's
not the best repo to clone from. Pulling updates won't work most of the


> As I have no idea what your packages do, please give me a bit more
> information about /usr/lib/qgis/crssync. It updates a srs.db - where
> does it look for "input" files? hardcoded directory(ies) (which?) or
> from config file (which?)

The srs.db is updated with the CRS data from GDAL and PROJ.4. crssync
uses the csv and wkt files shipped in libgdal1h:


 /usr/share/gdal/1.10/epsg.wkt (the wkts it includes no longer exist)

The paths are not hardcoded, only the file basename is. The full path is
looked up using CPLFindFile() which is a function from libgdal.

>From reading the source (QgsCoordinateReferenceSystem::syncDb() in
http://hub.qgis.org/issues/5282 where crssync is added to
qgis-providers-common.postinst, and http://hub.qgis.org/issues/3645
where crssync was initially introduced, it also uses the EPSG list from
Proj.4 via the proj API.


The EPSG list from Proj.4 is included in proj-data which is a dependency
of libproj0.

I chose to go with the named trigger first because I envision the gdal
and proj4 packages to activate this trigger too in their postinst when
their data is updated.

Kind Regards,


GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)

Pkg-grass-devel mailing list

Reply via email to