[Qgis-developer] Plugin [740] qgis2web approval notification.

[noreply]

Plugin qgis2web approval by pcav.
The plugin version "[740] qgis2web 2.16.2" is now approved
Link: http://plugins.qgis.org/plugins/qgis2web/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [1066] Isogeo approval notification.

[noreply]

Plugin Isogeo approval by pcav.
The plugin version "[1066] Isogeo 1.5.0-beta4 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/isogeo_search_engine/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing: gdal_calc generates Python.exe has stopped working on Windows

[Alexander Bruy]

Hi René-Luc,

I have also seen this issue several times, and for me it also happen
not only wth gdal_calc but also with other Python-based GDAL tools.

I did not reported it because I was unable to produce stable test case.

2017-04-25 11:05 GMT+03:00 René-Luc Dhont :
> Hi Jürgen,
>
> Thanks for your answer.
>
> I wonder if other QGIS user on Windows has already tested the GDAL
> calculator and have the same issue as the reporter and my customer.
>
> About Osgeo4W, we have opened a tickets 4 years ago about PHP to help users
> tested Lizmap and QGIS Server on windows, but we nerver have any reaction
> https://trac.osgeo.org/osgeo4w/ticket/343
>
> I know that QGIS is build with some packages coming from OSgeo4W, I suppose
> that some part of the project are maintained and I thank you those who do
> it.
>
> Regards,
>
> René-Luc
>
>
> Le 24/04/2017 à 11:46, Jürgen E. Fischer a écrit :
>
> Hi René-Luc,
>
> On Mon, 24. Apr 2017 at 11:21:50 +0200, René-Luc Dhont wrote:
>
> Does someone else has encountered this issue ?
>
> The reporter.
>
> Do you know if Osgeo4W is maintained ?
>
> Depends how you define it.
>
>
> Jürgen
>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [gdal-dev] GDAL 2.2.0 beta 2 available

[Even Rouault]

> 
> Hum, there might be an intermediate option: revert the change in GDAL 2.2
> branch, and keep it in 2.3dev which will probably be released in one year,
> at a time where QGIS 3 should have been released to.

I've taken another road finally. Build the internal copy of shapelib of QGIS 
with some 
modifications :
* prefix all the SHP* and DBF* symbols of it with qgis_ to avoid symbol name 
clashes
* and use GDAL VSI Large file I/O instead of standard lib FILE API so that 
UTF-8 names are 
properly handled on Windows.

>From my (light) tests, seems to work (on Linux).

==> https://github.com/qgis/QGIS/pull/4413

Even

> 
> > Matthias
> > 
> > On 4/24/17 7:20 PM, Even Rouault wrote:
> > > Hi,
> > > 
> > > > - Shape: do not export Shapelib symbols for builds
> > > > 
> > > > --with-hide-internal-symbols (#6860)
> > > 
> > > It turns out that the above change breaks QGIS 2.18 build, in
> > > particular the DXF2SHP converter native plugin, since it does a nasty
> > > trick: the QGIS build tree has the shapelib 2.10 includes files, but
> > > relies on linking against shapelib symbols exported by libgdal. The
> > > plugin apparently no longer exists in QGIS master, which builds fine
> > > against GDAL 2.2beta2.
> > > 
> > > 
> > > 
> > > So I'm not sure what to do:
> > > 
> > > 1) revert #6860 and export again shapelib symbols from GDAL. But this
> > > apparently breaks some other workflows
> > > 
> > > 2) let distributions apply a patch to do this revert, while they use
> > > QGIS 2.18 or other code that depend on GDAL exporting shapelib symbols
> > > 
> > > 3) Change DXF2SHP plugin to use OGR API instead of shapelib, but I'm
> > > not feeling like I would do that myself.
> > > 
> > > 
> > > 
> > > My opinion would be to favor 2)
> > > 
> > > 
> > > 
> > > Opinions ?
> > > 
> > > 
> > > 
> > > Even
> > > 
> > > 
> > > 
> > > 
> > > Spatialys - Geospatial professional services
> > > 
> > > http://www.spatialys.com
> > > 
> > > 
> > > 
> > > ___
> > > Qgis-developer mailing list
> > > Qgis-developer@lists.osgeo.org
> > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing: gdal_calc generates Python.exe has stopped working on Windows

[Jürgen E . Fischer]

Hi,

On Tue, 25. Apr 2017 at 10:05:43 +0200, René-Luc Dhont wrote:
> About Osgeo4W, we have opened a tickets 4 years ago about PHP to help users
> tested Lizmap and QGIS Server on windows, but we nerver have any reaction
> https://trac.osgeo.org/osgeo4w/ticket/343

The webstuff is not maintained in OSGeo4W (32bit, doesn't exists at all for
64bit - as qgis doesn't strictly need it).  qgis server is there - but for
64bit you need to add apache (probably the best bet for 32bit too - it's apache
is really old).
 
> I know that QGIS is build with some packages coming from OSgeo4W, I suppose
> that some part of the project are maintained and I thank you those who do
> it.

GRASS is maintained by Martin Landa, the rest essentially by me (there are some
people on and off contributing something).

But not everything is actively kept uptodate - dependencies just when QGIS or
some of it's direct dependencies require it.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [gdal-dev] GDAL 2.2.0 beta 2 available

[Nathan Woodrow]

Yeah don't change anything like this in a LTR. It's not a good idea for
trust.

On Tue, 25 Apr 2017, 5:24 PM Matthias Kuhn  wrote:

> > Please don't. Embedded code copies are a PITA. QGIS has too many of
> those already (although they're generally not required).
>
> I agree in general. I think this case here is a bit different, given
> that this is already partially present (in a particularly cumbersome and
> incomplete way) and is going to be phased out soon.
>
> >>> 5) require GDAL < 2.2 for building QGIS 2.18
> > What about
> >
> > 6) #ifdef the offending plugin out in 2.18 for GDAL >= 2.2?
>
> If that's going to be done I would update that to error out in CMake
> with an incompatiblity error and force the packager to make a decision
> (actively disable dxf2shp or pin GDAL to the older version).
>
> Which decision would you propose for the packages provided upstream
> (like OSGeo4W)?
>
> >
> > Given that the plugin is removed in QGIS 3.0 anyway, I think early
> > retirement is a perfectly valid option. It's also the best option for
> > GDAL, and avoids any wasted effort temporarily fixing code which only
> > has a short time left to live anyway...
>
> I was thinking the same, but breaking peoples workflows in patch
> releases is a good way to undermine the trust in LTR.
>
> Matthias
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [gdal-dev] GDAL 2.2.0 beta 2 available

[Matthias Kuhn]

> Please don't. Embedded code copies are a PITA. QGIS has too many of those 
> already (although they're generally not required).

I agree in general. I think this case here is a bit different, given
that this is already partially present (in a particularly cumbersome and
incomplete way) and is going to be phased out soon.

>>> 5) require GDAL < 2.2 for building QGIS 2.18
> What about
>
> 6) #ifdef the offending plugin out in 2.18 for GDAL >= 2.2?

If that's going to be done I would update that to error out in CMake
with an incompatiblity error and force the packager to make a decision
(actively disable dxf2shp or pin GDAL to the older version).

Which decision would you propose for the packages provided upstream
(like OSGeo4W)?

>
> Given that the plugin is removed in QGIS 3.0 anyway, I think early
> retirement is a perfectly valid option. It's also the best option for
> GDAL, and avoids any wasted effort temporarily fixing code which only
> has a short time left to live anyway...

I was thinking the same, but breaking peoples workflows in patch
releases is a good way to undermine the trust in LTR.

Matthias

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer