cause of ticket/3882 winGRASS 7.8 isn't really usable for vector editing
cause of ticket/3880 winGRASS 7.8 won't be working with precombiled binary
addons
* is there any plan for a GRASS 7.8.1 ?
* what is the backport status from master to releasebranch_7_8
That’s good news! Thank you. I would like to have some time to fix at least some of the windows issues that popped up with Python3, I need to review what needs to be done, I lost track of it. But I agree we should release fairly soon.
On Mon, Oct 14, 2019 at 2:51 PM Helmut Kudrnovsky <hellik@web.de> wrote:
hi,
as winGRASS is on the way to come back, see [1]. locally here is already
winGRASS 7.8.0 running for testing.
there are already a few reported issues for python3 and git related to
winGRASS etc, e.g.
cause of ticket/3882 winGRASS 7.8 isn’t really usable for vector editing
cause of ticket/3880 winGRASS 7.8 won’t be working with precombiled binary
addons
is there any plan for a GRASS 7.8.1 ?
what is the backport status from master to releasebranch_7_8
cause of ticket/3882 winGRASS 7.8 isn't really usable for vector editing
cause of ticket/3880 winGRASS 7.8 won't be working with precombiled binary
addons
* is there any plan for a GRASS 7.8.1 ?
* what is the backport status from master to releasebranch_7_8
And what's the status of addons for Windows. I have a lot of colleagues suffering from their apparent absence.
That’s good news! Thank you. I would like to have some time to fix at least some of the windows issues that popped up with Python3, I need to review what needs to be done, I lost track of it. But I agree we should release fairly soon.
I agree that we should release soon.
How about RC1 a week?
On Sat, Oct 19, 2019 at 8:20 PM Markus Neteler <neteler@osgeo.org> wrote:
Hi,
Anna Petrášová <kratochanna@gmail.com> schrieb am Mo., 14. Okt. 2019, 21:11:
That's good news! Thank you. I would like to have some time to fix at least some of the windows issues that popped up with Python3, I need to review what needs to be done, I lost track of it. But I agree we should release fairly soon.
Would it make sense to wait if we can get the standalone wingrass and addons (Martin?), I am not sure where it is at, or how much time it’s needed for this. If that might take awhile still, then yes, we can release.
Anna
On Sun, Oct 20, 2019 at 8:30 AM Markus Neteler <neteler@osgeo.org> wrote:
On Sat, Oct 19, 2019 at 8:20 PM Markus Neteler <neteler@osgeo.org> wrote:
That’s good news! Thank you. I would like to have some time to fix at least some of the windows issues that popped up with Python3, I need to review what needs to be done, I lost track of it. But I agree we should release fairly soon.
Would it make sense to wait if we can get the standalone wingrass and
addons (Martin?), I am not sure where it is at, or how much time it's
needed for this. If that might take awhile still, then yes, we can
release.
OSGeo4W-winGRASS 7.8.1 and standalone winGRASS 7.8.1 should be doable.
regarding addons, daily builds depends on Martin's server able to build and
compile.
tested OSGeo4W-winGRASS 7.8.dev a little bit in the last days, some python3
(?) issues are there, e.g.
That’s good news! Thank you. I would like to have some time to fix at least some of the windows issues that popped up with Python3, I need to review what needs to be done, I lost track of it. But I agree we should release fairly soon.
That’s good news! Thank you. I would like to have some time to fix at least some of the windows issues that popped up with Python3, I need to review what needs to be done, I lost track of it. But I agree we should release fairly soon.
On Tue, 29. Oct 2019 at 13:07:47 +1000, Nyall Dawson wrote:
I wonder if there's anything the QGIS project can do to assist here.
The options as I see them:
1. Wait for GRASS to update and release (doesn't seem a great option
-- the whole geo stack is being delayed by this (e.g. gdal 3 missed
the ubuntu 19.10 release)
2. Publish the Windows build with a snapshot of grass, with
cherry-picked unmerged patch for gdal 3/proj 6
3. Try to resurrect the stalled work on the GRASS patch via qgis.org funding
4. ... ?
As said:
On Mon, 28. Oct 2019 at 18:18:05 +0100, Jürgen E. Fischer wrote:
Looks pretty close. And I'm not sure that putting work into workarounds will
get us there any earlier as a little patience would.
On grass-dev:
On Mon, 28. Oct 2019 at 19:13:33 +0100, Markus Neteler wrote:
Markus Metz <markus.metz.giswork@gmail.com> schrieb am Mo., 28. Okt. 2019,
19:06:
> I would like to get PROJ 6 support into G 7.8.1, can we get RC1 out end of
> this week?
Just to be sure, you merge and then RC1?
So it is close. But we still need to coordinate when to update GDAL & PROJ in
OSGeo4W so it's available for a new GRASS build and also that the other reverse
dependencies (ie. QGIS) are rebuilt with it - and then re-issue a new
standalone after that.
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 https://www.norbit.de
QGIS release manager (PSC) Germany IRC: jef on FreeNode
On Tue, Oct 29, 2019 at 10:11 AM Jürgen E. Fischer <jef@norbit.de> wrote:
Hi Nyall,
On Tue, 29. Oct 2019 at 13:07:47 +1000, Nyall Dawson wrote:
> I wonder if there's anything the QGIS project can do to assist here.
> The options as I see them:
>
> 1. Wait for GRASS to update and release (doesn't seem a great option
> -- the whole geo stack is being delayed by this (e.g. gdal 3 missed
> the ubuntu 19.10 release)
> 2. Publish the Windows build with a snapshot of grass, with
> cherry-picked unmerged patch for gdal 3/proj 6
> 3. Try to resurrect the stalled work on the GRASS patch via qgis.org funding
> 4. ... ?
As said:
On Mon, 28. Oct 2019 at 18:18:05 +0100, Jürgen E. Fischer wrote:
> Looks pretty close. And I'm not sure that putting work into workarounds will
> get us there any earlier as a little patience would.
On grass-dev:
On Mon, 28. Oct 2019 at 19:13:33 +0100, Markus Neteler wrote:
> Markus Metz <markus.metz.giswork@gmail.com> schrieb am Mo., 28. Okt. 2019,
> 19:06:
> > I would like to get PROJ 6 support into G 7.8.1, can we get RC1 out end of
> > this week?
>
> Just to be sure, you merge and then RC1?
But we still need to coordinate when to update GDAL & PROJ in
OSGeo4W so it's available for a new GRASS build and also that the other reverse
dependencies (ie. QGIS) are rebuilt with it - and then re-issue a new
standalone after that.
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 https://www.norbit.de
QGIS release manager (PSC) Germany IRC: jef on FreeNode
_______________________________________________
Qgis-psc mailing list
Qgis-psc@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/qgis-psc
On Tue, Oct 29, 2019 at 8:46 AM Markus Metz
<markus.metz.giswork@gmail.com> wrote:
On Mon, Oct 28, 2019 at 9:18 PM Helmut Kudrnovsky <hellik@web.de> wrote:
>
> Helmut Kudrnovsky wrote
> >>I would like to get PROJ 6 support into G 7.8.1, can we get RC1 out >end
> of
> > this week?
> >
> > Will grass support then also GDAL 3?
Yes, GRASS will then work with GDAL 3 + PROJ 6 (just finished some local tests, looks all fine).
Excellent, thanks for the hard work!
Since the QGIS project is eagerly waiting for the release [1], I would
like to prepare RC1 today unless there is a showstopper.
On Mon, Oct 28, 2019 at 9:18 PM Helmut Kudrnovsky <
hellik@
> wrote:
>
> Helmut Kudrnovsky wrote
> >>I would like to get PROJ 6 support into G 7.8.1, can we get RC1 out
>end
> of
> > this week?
> >
> > Will grass support then also GDAL 3?
Yes, GRASS will then work with GDAL 3 + PROJ 6 (just finished some local
tests, looks all fine).
Excellent, thanks for the hard work!
Since the QGIS project is eagerly waiting for the release [1], I would
like to prepare RC1 today unless there is a showstopper.
--------
So it is close. But we still need to coordinate when to update GDAL & PROJ
in
OSGeo4W so it's available for a new GRASS build and also that the other
reverse
dependencies (ie. QGIS) are rebuilt with it - and then re-issue a new
standalone after that.
--------
On Tue, 29. Oct 2019 at 13:07:47 +1000, Nyall Dawson wrote:
1. Wait for GRASS to update and release (doesn't seem a great option
-- the whole geo stack is being delayed by this (e.g. gdal 3 missed
the ubuntu 19.10 release)
GDAL 3 is not in Ubuntu 19.10 because it's not in Debian unstable yet, and Ubuntu syncs its packages from Debian unstable by default.
There is also no one actively maintaining the geospatial packages in Ubuntu, and hence no one to do work that diverges from Debian.
The transition to GDAL 3 in Debian unstable is blocked by the removal of python-gdal as discussed in the transition bugreport: