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
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
Hi Andreas,
Thanks for reporting this issue.
The srs.db provided by qgis-providers-common is updated by crssync
included in qgis-providers.
Because qgis-providers depends on qgis-providers-common, the common
package will be configured first, and I think this will prevent the
trigger in
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.
4 matches
Mail list logo
