Bug#738273: qgis-providers-common: fails to install, should use triggers for crssync

[Andreas Beckmann]

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.
> 
> The trigger is only run when I `dpkg -i`
> qgis-providers-common_2.0.1-2_all.deb from the apt archives cache after
> wards.

Attached patch hasn't been tested, yet.
The trigger stuff can be simplified :-)
And no need to distinguish different triggers until you need to.

You need to activate the trigger also by installing the package
providing the trigger either with an explicit dpkg-trigger in the
postinst or by just running the trigger in in the postinst.

If qgis-providers-common triggers something that is not being awaited
for (because qgis-providers is not yet unpackaged or configured), the
trigger is lost (well, it triggered nothing, so nothing to do).

> Using a file based trigger on the srs.db may be an option, then we'll
No need to, and if the directory is rather dynamic, not a good idea.


Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-simplify-trigger.patch
Type: text/x-patch
Size: 1055 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-grass-devel/attachments/20140210/74fa87c9/attachment.bin>