Re: [Qgis-developer] Point releases

+1 for the point release. And one release a month as scheduled seems reasonable to me. But since every user can not download and install each release, it'll be worth listing the bugs that are fixed. So the user can clearly evaluate if it's worth updating QGIS according to his needs. 2015-11-25

[Qgis-developer] Intensive work with print composer become hard due to some bugs. Any help?

Looking at the quick way FTools bugs have been fixed, I realized once again how FOSS community can be reactive. And this is just amazing, impressive. Big up to u! So, since there are some bugs in print composer that make it hard to use for daily and intensive compositions, can I ask for your help

Re: [Qgis-developer] grass module don't appear

On Wed, Nov 25, 2015 at 3:35 PM, Giovanni Manghi wrote: > > Then I searched for r.mapcalculator, which was present in the old > processing toolbox. I didn't find it > > in the grass7 processing modules list. Although the grass7 stand alone > has r.mapcalc (not

[Qgis-developer] Two different icons for same action?

Hi, I'm trying to write QGIS 2.12 documentation and encounter some issues about icon substitutions. Copy features actions seems to have different icons: - mActionEditCopy [0] (in identify results panel, Configure shortcuts dialog, Edit menus and toolbar, ... [1] ) with a white background -

Re: [Qgis-developer] grass module don't appear

> Then I searched for r.mapcalculator, which was present in the old processing > toolbox. I didn't find it > in the grass7 processing modules list. Although the grass7 stand alone has > r.mapcalc (not r.mapcalculator), > in the grass7 processing toolbox neither r.mapcalculator nor r.mapcalc are

Re: [Qgis-developer] Point releases

ok, I can remove pull request regarding FTool message wonderful team work... we can summarize some "lesson learned" from this bug? cheers Luigi Pirelli ** * Boundless QGIS Support/Development:

[Qgis-developer] QGIS Web Client: WSGI search capabilities using multiple databases

Hi all, For the WSGI Search capabilities on QGIS Web Client, is it possible to establish search capabilities using multiple databases (i.e., tables within multiple databases)? I have QGIS projects which utilize different PostGIS databases and would like to be able to list all the various

Re: [Qgis-developer] Point releases

On 26 November 2015 at 07:51, Luigi Pirelli wrote: > ok, I can remove pull request regarding FTool message > > wonderful team work... we can summarize some "lesson learned" from this bug? Write unit tests for critical stuff like this? Don't accept a replacement for ftools which

[Qgis-developer] QGIS georeferencer / vector georeferencer

Hi, Is there a reason why the QGIS georeferencer is still a plugin and not part of QGIS core? Do you think that the existing QGIS raster georeferencer could be enhanced/extended to also allow the georeferencing of one or more vector layers? I know that there is a Python plugin to do

[Qgis-developer] Qgis Server 2.12 - WFS no data

Hi, I'm using ubuntu 14.04.3 LTS and qgis-server_2.12.0. The wms service is working correctly but wfs no, I can't get data. For testing I install qgis-mapserver, the default package from ubuntu 14.04 and wfs returns data. Any idea? Thanks. ___

Re: [Qgis-developer] Qgis Server 2.12 - WFS no data

Hi, Did you enable the WFS layers in the OWS tab? Note that if a WMS is enabled, it doesn't mean that your layers are automatically published as WFS - you have to opt in for that. If they are enabled, it probably sounds like a bug, at least in your package. Andreas On 25.11.2015 10:18,

Re: [Qgis-developer] Tool to pick up linear referencing measure from mouse

On Tue, Nov 24, 2015 at 10:29 PM, Régis Haubourg wrote: > Radim, do you have plans to extend LRS in 2016? If you have sponsors looking > for co-funders, I would be interested in having it work with existing > M-geometries, and have tools to generate events by

[Qgis-developer] Trouble with creatensis.pl on Ubuntu 14.04 LTS

Hi, I am trying to build a custom QGIS installer using creatensis.pl on Ubuntu 14.04 LTS. Unfortunately I am getting errors during unpacking: "tar: A lone zero block at 380 tar: apps/Qt4: Cannot mkdir: Permission denied" And apps/Qt4 indeed has unknown permissions: "d? ? ? ? ?" After

Re: [Qgis-developer] Point releases

Hi Jürgen > On 25 Nov 2015, at 13:07, Jürgen E. Fischer wrote: > > Hi, > > I updated the release schedule to include dates for the point release[0]. I > think it's easier to have fixes dates there too - instead of a "some-period of > silence" rule. > > The next point release

[Qgis-developer] Point releases

Hi, I updated the release schedule to include dates for the point release[0]. I think it's easier to have fixes dates there too - instead of a "some-period of silence" rule. The next point release for 2.8.x and 2.12.x will be on Friday. Any objections? Nyall and I finished our backports from

Re: [Qgis-developer] Point releases

Hi! According to my tests with Intersect and Union the ftools problem is fixed now .. so this only "leaves" 2.10 without a fix - which we apperently don't need (people using 2.10 should upgrade to 2.12 anyway).. Well done! thanks regards Werner On Wed, Nov 25, 2015 at 12:07 PM, Jürgen E.

Re: [Qgis-developer] Point releases

Il 25/11/2015 12:28, Werner Macho ha scritto: > According to my tests with Intersect and Union the ftools problem is > fixed now .. so this only "leaves" 2.10 without a fix - which we > apperently don't need (people using 2.10 should upgrade to 2.12 > anyway).. > > Well done! What a relief,

Re: [Qgis-developer] Point releases

Hi, That's a good idea - to have fixed dates for point releases. Andreas On 25.11.2015 12:07, Jürgen E. Fischer wrote: Hi, I updated the release schedule to include dates for the point release[0]. I think it's easier to have fixes dates there too - instead of a "some-period of silence"

Re: [Qgis-developer] Point releases

On Wed, Nov 25, 2015 at 12:31 PM, Paolo Cavallini wrote: > Il 25/11/2015 12:28, Werner Macho ha scritto: > > > According to my tests with Intersect and Union the ftools problem is > > fixed now .. so this only "leaves" 2.10 without a fix - which we > > apperently don't