>Time schedule:
>https://trac.osgeo.org/grass/milestone/7.8.0
>
>- Proposal of release: 4 Feb 2019 (OSGeo birthday, btw!)
>- Creation of release branch: 11 Feb 2019
>- RC1: 11 Mar 2019
>- RC2: 24 Mar 2019
>- RC3: if needed
>- Final release: 1 Apr 2019 (tentatively)
>
>For sure an "intensive" plan b
fyi
https://lists.osgeo.org/pipermail/proj/2019-February/008167.html
#
All,
I have prepared a release candidate of PROJ 6.0.0. See the release notes
below.
Download it here:
https://download.osgeo.org/proj/proj-6.0.0RC1.tar.gz
(https://download.osgeo.org/proj/pr
[forwarded from
https://lists.osgeo.org/pipermail/proj/2019-March/008287.html]
#
PROJ 6 has undergone extensive changes to increase its functional scope from
a
cartographic projection engine with so-called "early-binding" geodetic datum
transformation capabilities to a more comple
Hi,
it seems the winGRASS7.7.svn dailys are down:
https://wingrass.fsv.cvut.cz/grass77/x86_64/
maybe a full disk?
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-
hi,
just had a look at
https://wingrass.fsv.cvut.cz/grass77/x86_64/
the /grass77/x86_64/osgeo4w-subfolder is empty, also
https://download.osgeo.org/osgeo4w/x86_64/release/grass/grass-daily/
is empty.
any chance that we get winGRASS7.7.svn daily builds back?
-
best regards
Helmut
--
Sen
Hi,
just tried to start the latest OSGeo4W winGRASS77svn daily build:
C:\>grass77svn
Starting GRASS GIS...
Traceback (most recent call last):
File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\gis_set.py", line 34, in
from core import globalvar
File "C:\OSGEO4~1\apps\grass\grass77\gu
Helmut Kudrnovsky wrote
> Hi,
>
> just tried to start the latest OSGeo4W winGRASS77svn daily build:
>
>
> C:\>grass77svn
> Starting GRASS GIS...
> Traceback (most recent call last):
> File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\gis_set.py",
Hi,
looking into winGRASS77svn compilation log:
https://wingrass.fsv.cvut.cz/grass77/x86_64/logs/log-r74459-14/error.log
#
GRASS GIS 7.7.svn r74459M compilation log
--
Started compilation: Sat May 4 15:56:01 2019
--
Errors in:
fyi https://lists.osgeo.org/pipermail/proj/2019-May/008515.html
###
I have prepared candidates for the upcoming releases of PROJ 6.1.0 and
proj-datumgrid-europe-1.3.
Download the archives here:
https://download.osgeo.org/proj/proj-6.1.0RC1.tar.gz
(https://download.osgeo.org
hi Martin,
> In this regard I would like to ask you for ASSISTANCE. All
>tickets with milestone 7.0 [3], 7.2 [4] should be reviewed and either
>to be closed or milestone changed to 7.4 (or 7.6/7.8/8.0).
do we have some date until when tickets should be reviewed?
-
best regards
Helmut
--
Se
Veronica Andreo wrote
> Hola :)
>
> El mar., 7 may. 2019 a las 16:20, Veronica Andreo (<
> veroandreo@
> >)
> escribió:
>
>> El mar., 7 may. 2019 a las 11:54, Martin Landa (<
> landa.martin@
> >)
>> escribió:
>>
>>> Hi,
>>>
>>> út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo <
> veroandreo@
Hi Vero,
>See Martin's original mail and links. The tickets that need to be >reviewed
are those with milestone 7.0.7 and 7.2.4, as to know if >they are still
valid and milestone should be moved to 7.6.2
IMHO when I go through the tickets for 7.0.7 and 7.2.4, an additional check
with trunk (Python
Markus Neteler wrote
> On Fri, May 10, 2019 at 1:12 PM Helmut Kudrnovsky <
> hellik@
> > wrote:
> ...
>> so far I couldn't find a solution for the winGRASS trunk regression
>
> The only way I see is to revert the change and see if it works again.
> If yes,
Anna Petrášová wrote
> Hi,
>
> I am testing some changes in Python library on Windows and when I get over
> the current problem, I run into that I can't import win32file in
> core/gcmd.py. Some problem with packaging?
>
> Thank you,
>
> Anna
>
> ___
>
Markus Neteler wrote
> So, if someone isn't listed yet:
> Please get a GitHub account and/or communicate it to us (name + related
> email).
svn: hellik
gh account: hellik
email: hkmyrica...@gmail.com
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f399189
Anna Petrášová wrote
> standalone
trying here with OSGeo4W-winGRASS7.7.svn
#
C:\>grass77svn ---text D:\grassdata\nc_spm_08_grass7\user1
Starting GRASS GIS...
WARNUNG: Sperren gleichzeitiger Zugriffe auf ein Mapset ist unter Windows
nicht möglich.
Cleaning up tempo
Anna Petrášová wrote
> Hi,
>
> I am testing some changes in Python library on Windows and when I get over
> the current problem, I run into that I can't import win32file in
> core/gcmd.py. Some problem with packaging?
applied locally your commits (r74480), I get:
C:\
Anna Petrášová wrote
>> are the related python packages in the bundled python
>> (Python37\lib\site-packages\win32)?
>>
>
> no, win32 was not there as far as I remember
looking at
https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/setup_x86_64.hint.tmpl
requires: liblas avce00
Anna Petrášová wrote
> Did you compile it with those local changes? It needs to be compiled to
> create the xml files.
no compilation yet, just copied the updated python script.
which is the relevant xml-file?
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-D
Helmut Kudrnovsky wrote
> there is no win32-site package inside.
>
> it's an package issue.
looking at
https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Packager.bat.tmpl#L98
96 @echo.
Markus Neteler wrote
> On Wed, May 15, 2019 at 9:32 PM Helmut Kudrnovsky <
> hellik@
> > wrote:
>>
>> Markus Neteler wrote
>> > So, if someone isn't listed yet:
>> > Please get a GitHub account and/or communicate it to us (name + related
>&
Anna Petrášová wrote
>> which is the relevant xml-file?
>>
>
> it creates gui/wxpython/xml/menudata.xml and module_tree_menudata.xml
> during compilation.
module_tree_menudata.xml is empty here. I have to wait for the next daily
build to test.
-
best regards
Helmut
--
Sent from: http://os
Martin Landa wrote
> Hi,
>
> st 15. 5. 2019 v 21:32 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> svn: hellik
>>
>> gh account: hellik
>> email:
> hkmyricaria@
>
> in the case you have write access to Addons, you can directly
Martin Landa wrote
> čt 16. 5. 2019 v 8:25 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> https://trac.osgeo.org/grass/browser/grass-addons/tools/svn2git
>>
>> which file should be updated/checked?
>
> tools/svn2git/AUTHORS.txt
AUTHORS
Helmut Kudrnovsky wrote
> Anna Petrášová wrote
>>> which is the relevant xml-file?
>>>
>>
>> it creates gui/wxpython/xml/menudata.xml and module_tree_menudata.xml
>> during compilation.
>
> module_tree_menudata.xml is empty here. I have to wait for th
Martin Landa wrote
> Hi,
>
> WinGRASS builds are currently down. It will take some time to update
> build procedure to a new git repo workflow. I will inform you about
> progress.
https://trac.osgeo.org/grass/wiki/CompileOnWindows
which sections have to be updated?
-
best regards
Helmut
Anna Petrášová wrote
> On Wed, May 15, 2019 at 4:14 PM Helmut Kudrnovsky <
> hellik@
> > wrote:
>
>> Anna Petrášová wrote
>> > Did you compile it with those local changes? It needs to be compiled to
>> > create the xml files.
>>
>> no
Martin Landa wrote
> but unfortunately git appeared to be broken in my msys2 installation
> (calling `git` command had no effect). So I am trying to reinstall
> msys2 from scratch.
git in my msys2 installation works.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/G
Martin Landa wrote
> Hi,
>
> so 18. 5. 2019 v 19:48 odesílatel Martin Landa <
> landa.martin@
> > napsal:
>> but unfortunately git appeared to be broken in my msys2 installation
>> (calling `git` command had no effect). So I am trying to reinstall
>> msys2 from scratch.
>
> it helped partially.
see https://lists.osgeo.org/pipermail/qgis-developer/2019-June/057557.html
-
Hi Calvin,
On Tue, 04. Jun 2019 at 14:22:19 -0400, C Hamilton wrote:
> Why does the QGIS 3 OSGeo4W shell default to python 2 when QGIS is running
> python 3? I
hi,
after updating here MSYS2 and MS Visual Studio versions to the latest
versions, I've tried to compile/build winGRASS master 64bit:
--
GRASS GIS 7.7.dev 47e02fc12 compilation log
--
Started compilation: Thu Jun 20 22:
hi,
testing here winGRASS compilation after switch to github. found some issues
here.
where should a report go? github or trac?
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing
hi,
after locally self compiling/building winGRASS master in the MSYS2/OSGeo4W
environment with following build information:
---
C:\>g.version -breg
version=7.7.dev
date=2019
revision=47e02fc12
build_date=2019-06-20
build_platform=x86_64-w64-mingw32
build_off_t_size=8
./conf
Martin Landa wrote
> Hi,
>
> ne 23. 6. 2019 v 23:12 odesílatel Markus Neteler <
> neteler@
> > napsal:
>
> definitely trac, github issue tracker is disabled moreover.
>
> Ma
>
> PS: I will have time on beginning of July to migrate trac issue to github.
any chance to get back winGRASS dailys
Markus Neteler wrote
> Hi,
>
> time to speed up the GRASS GIS 7.8.0 release!
>
> On Mon, Apr 1, 2019 at 10:04 AM Martin Landa <
> landa.martin@
> > wrote:
>> ne 3. 3. 2019 v 19:33 odesílatel Martin Landa <
> landa.martin@
> > napsal:
>> > my +1 for creating 7.8 releasebranch. It's a first ste
>I will try to take a look on this
>issue after solving wingrass builds.
>Volunteers welcome in in case.
Anything to help/test regarding winGRASS builds? After upgrading to the
latest msys2/mingw stuff, compiling works locally here.
-
best regards
Helmut
--
Sent from: http://osgeo-org
Hi Martin,
Martin Landa wrote
> Hi,
>
> I have recovered (at least partially) wingrass builds:
>
> * daily builds (GRASS 7.6 & 7.7: only 64bit builds) [standalone [1] &
> osgeo4w/grass-daily) are operational
>
> Up-to-date maintenance scripts available at [2].
>
> In next days I will re-cover
>Hello, I experienced the exact same issue on Windows. One of my PRs should
fix it.
thanks for your effort.
which of your PR?
next week I'll be able to test it locally in my winGRASS build environment.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f39
Martin Landa wrote
> čt 11. 7. 2019 v 22:54 odesílatel Martin Landa <
> landa.martin@
> > napsal:
>> > ° "inflateValidate" in the dll
>> > C:\OSGeo4W\apps\grass\grass77\bin\libpng16-16.dll can't be found
>
> probably relevant,
> https://github.com/gtk-rs/gtk/issues/539#issuecomment-442993185
>
Hi,
under
https://www.gaia-gis.it/fossil/libspatialite/wiki?name=PROJ.6
there is a nice overview of the new proj library functionality. maybe useful
for further adopting in GRASS GIS.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
>Any opinions on merging PRs related to MS Windows builds to .>master without
testing by another person?
more description why the changes and more testing before merging is welcome.
it seems there is some windows dll hell issue at the moment which should be
solved before the PRs can be tested. f
Martin Landa wrote
> Hi,
>
> ne 7. 7. 2019 v 21:53 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> ° "inflateValidate" in the dll
>> C:\OSGeo4W\apps\grass\grass77\bin\libpng16-16.dll can't be found
>
> after upgrading build msys
>tested now build no. 3, the libng-dll issue seems to be solved; but stilll
>here the problem with
unfortunately the libpng-dll isn't solved with build no. 3; still there.
the issue causes that d.rast doesn't work.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/G
Martin Landa wrote
> Hi,
>
> ne 7. 7. 2019 v 21:53 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> following issue when downloading OSGeo4W grass-daily-7.7.dev-f79c3568d-1:
>>
>> ° g.mkfontcap.exe - system error because libgraphite2.dll
Helmut Kudrnovsky wrote
> Martin Landa wrote
>> Hi,
>>
>> ne 7. 7. 2019 v 21:53 odesílatel Helmut Kudrnovsky <
>
>> hellik@
>
>> > napsal:
>>> following issue when downloading OSGeo4W
>>> grass-daily-7.7.dev-f79c3568d-1:
>&g
Martin Landa wrote
> Hi,
>
> po 15. 7. 2019 v 21:58 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> will open a ticket and hopefully my first PR :-)
>
> great, meanwhile I have applied patch locally, so next build should
> include these dlls. Ma
Markus Neteler wrote
> Hi
>
> Anna Petrášová <
> kratochanna@
> > schrieb am Mo., 15. Juli 2019, 05:57:
>
>>
>>
>> On Fri, Jul 12, 2019 at 12:50 PM Maris Nartiss <
> maris.gis@
> >
>> wrote:
>>
>>> The biggest question is – do we need PR notifications here. I would
>>> vote for no. Better let
Markus Neteler wrote
> Hi
>
> Markus Neteler <
> neteler@
> > schrieb am Mo., 1. Juli 2019, 17:47:
>
>> On Mon, Jul 1, 2019 at 3:37 PM Martin Landa <
> landa.martin@
> >
>> wrote:
>> >
>> > Hi,
>> >
>> > ne 30. 6. 2019 v 23:15 odesílatel Markus Neteler <
> neteler@
> >
>> napsal:
>> > > We
Helmut Kudrnovsky wrote
> see also:
>
> [GRASS-web] How to install GRASS Add-Ons after migration from SVN to
> Github?
> [https://lists.osgeo.org/pipermail/grass-web/2019-July/004919.html]
>
> [GRASS-user] Extensions
> [https://lists.osgeo.org/pipermail/grass-user/2019-Ju
hi,
https://github.com/OSGeo/grass/pull/53
is labelled as backport needed.
in https://trac.osgeo.org/grass/wiki/HowToGit#Backportingofasinglecommit
-
# temporarily switch to master
git checkout master
# update master to fetch the commit to be backported
git fetch --all --prune
# Note
pvanbosgeo wrote
> Hi devs,
>
> I am looking into how to share add-ons with Window users other than
> through the central GRASS GIS repository. First step is to create
> precompiled add-ons for Window users. Are there instructions for
> dummies? Otherwise, for Python scripts this could be done
hi,
actually, there are several complaints that downloading precompiled winGRASS
addons isn't working, see e.g.
https://trac.osgeo.org/grass/ticket/3455#comment:5
https://lists.osgeo.org/pipermail/grass-web/2019-July/004925.html
https://lists.osgeo.org/pipermail/grass-user/2019-July/080557.html
e
See
http://osgeo-org.1560.x6.nabble.com/PROJ-Reviews-requested-On-GDA2020-PROJ-6-and-QGIS-td5411799.html
for a nice sum up on implementing proj 6 Support:
---
Hi list!
I recently spent some time writing up my experiences with porting QGIS
to proj 6, and the lessons learnt and recommendat
Markus Neteler wrote
> Hi devs,
>
> since we now have the 7.8 release branch, I suggest to get rid of
> Python 2 support in master.
+1
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev
Markus Metz-3 wrote
> On Mon, Aug 5, 2019 at 3:55 PM Markus Neteler <
> neteler@
> > wrote:
>>
>> On Mon, Aug 5, 2019 at 9:11 AM Markus Neteler <
> neteler@
> > wrote:
>> > On Mon, Aug 5, 2019 at 8:38 AM Markus Metz
>> > <
> markus.metz.giswork@
> > wrote:
>> > > On Sun, Aug 4, 2019 at 3:20 P
Michael Barton wrote
> I'm getting a bunch of errors trying to compile GRASS master right now and
> they all seem to be calling for python3. Has this become the default as of
> yesterday or today?
yes, see [1]:
[GRASS-git] [OSGeo/grass] be0e59: change Python shebang to python3 (#75)
Markus Nete
Helmut Kudrnovsky wrote
> [GRASS-git] [OSGeo/grass] be0e59: change Python shebang to python3 (#75)
> Markus Neteler
> [GRASS-git] [OSGeo/grass] 6ac803: change Python shebang to python3 (#82)
> Markus Neteler
> [GRASS-git] [OSGeo/grass] 428521: change Python shebang to python3 (
trying to compile an uotodate winGRASS master, I get a lot of following
errors:
e.g.
make[4]: Entering directory '/usr/src/grass_trunk_git/grass/lib/pngdriver'
if [ "" != "" ] ; then
GISRC=/usr/src/grass_trunk_git/grass/dist.x86_64-w64-mingw32/demolocation/.grassrc79
GISBASE=C:/msys64/usr/src/gra
Helmut Kudrnovsky wrote
> trying to compile an uotodate winGRASS master, I get a lot of following
> errors:
>
> e.g.
>
> make[4]: Entering directory '/usr/src/grass_trunk_git/grass/lib/pngdriver'
> if [ "" != "" ] ; then
> GISRC=/usr/src/gras
>2) attempt to update building environment (gcc 4.x to newer version)
compiling with the newest msys2 gcc seems to work here.
>3) various strange problems with new build environment
I have this one here
https://lists.osgeo.org/pipermail/grass-dev/2019-August/093063.html
>4) lack of time to f
>pá 30. 8. 2019 v 17:35 odesílatel Helmut Kudrnovsky <[hidden email]> napsal:
>> Do you have a list of your issues facing while winGRASS compiling?
>
>different ;-) I am closer to successful build. Now it fails compiling
completly fresh git checkout here, still the already ea
Helmut Kudrnovsky wrote
>>pá 30. 8. 2019 v 17:35 odesílatel Helmut Kudrnovsky <[hidden email]>
napsal:
>>> Do you have a list of your issues facing while winGRASS compiling?
>>
>>different ;-) I am closer to successful build. Now it fails compiling
>
> compl
>it's not good idea to mix different version of Python.
it's not easy to keep msys2 and osgeo4w python in sync
>By [1] is
>forced osgeo4w Python version. In [2] he should remove all python
>packages.They are not needed.
does it mean that in msys2 there is no python3 needed at all?
pacman
Martin Landa wrote
> Hi,
>
> pá 30. 8. 2019 v 17:35 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> Do you have a list of your issues facing while winGRASS compiling?
>
> different ;-) I am closer to successful build. Now it fails compiling
>
Helmut Kudrnovsky wrote
> I get a longer log with errors when I'm do make in the ctypes subfolder:
Error: gcc -E -I/c/OSGeo4W64/include -D_FILE_OFFSET_BITS=64
-I/usr/src/grass_trunk_git/grass/dist.x86_64-w64-mingw32/include
-I/usr/src/grass_trunk_git/grass/dist.x86_64-w64-mingw32
Helmut Kudrnovsky wrote
> Helmut Kudrnovsky wrote
>> I get a longer log with errors when I'm do make in the ctypes subfolder:
>
> Error: gcc -E -I/c/OSGeo4W64/include -D_FILE_OFFSET_BITS=64
> -I/usr/src/grass_trunk_git/grass/dist.x86_64-w64-mingw32/include
> -I/usr
Helmut Kudrnovsky wrote
> regarding
>
> Error: C:/msys64/mingw64/x86_64-w64-mingw32/include/corecrt.h:80: Syntax
> error at 'uintptr_t'
> Error: C:/msys64/mingw64/x86_64-w64-mingw32/include/stdio.h:165: Syntax
> error at 'va_list'
>
> and ctypes issue
Martin Landa wrote
> Hi,
>
> so 7. 9. 2019 v 13:28 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> > Error: C:/msys64/mingw64/x86_64-w64-mingw32/include/corecrt.h:80:
>> Syntax
>> > error at 'uintptr_t'
>> > Error:
Martin Landa wrote
> Hi,
>
> so 7. 9. 2019 v 20:38 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> What about this one in display:
>>
>> C:/msys64/usr/src/grass_trunk_git/grass/dist.x86_64-w64-mingw32/include/grass/gis.h:24,
>> Error: gcc -E
Martin Landa wrote
> Hi,
>
> so 7. 9. 2019 v 20:40 odesílatel Martin Landa <
> landa.martin@
> > napsal:
>> not sure. libgrass_display.7.9.dll is successfully built, but cannot
>> be loaded for unknown reasons. Ma
>
> in other words problem is not ctypes compilation, but loading
> libgrass_disp
Martin Landa wrote
> Hi Helmut,
>
> so 7. 9. 2019 v 20:31 odesílatel Martin Landa <
> landa.martin@
> > napsal:
>> so apparently you have the same problem as me. It fails to load
>> libgrass_display.7.9.dll for unknown reason. It also causes that all
>> display modules fails to be compiled (or a
Martin Landa wrote
> Hi,
>
> so 7. 9. 2019 v 22:20 odesílatel Helmut Kudrnovsky <
> hellik@
> > napsal:
>> in both test cases (d.barscale.exe --html-description, r.info.exe
>> --html-description), I get nothing, neither an error message nor
>> --html-d
Helmut Kudrnovsky wrote
> Martin Landa wrote
>> Hi,
>>
>> so 7. 9. 2019 v 22:20 odesílatel Helmut Kudrnovsky <
>
>> hellik@
>
>> > napsal:
>>> in both test cases (d.barscale.exe --html-description, r.info.exe
>>> --html-descr
Martin Landa wrote
> Hi,
>
> so 7. 9. 2019 v 20:40 odesílatel Martin Landa <
> landa.martin@
> > napsal:
>> not sure. libgrass_display.7.9.dll is successfully built, but cannot
>> be loaded for unknown reasons. Ma
>
> in other words problem is not ctypes compilation, but loading
> libgrass_disp
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.
https://trac.osgeo.org/grass/ticket/3882
https://trac.osgeo.org/grass/ticket/3871
https://tra
Hi Anna,
Anna Petrášová wrote
> 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 win
>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?
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
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?
reasoning, mentioned in gdal/news
(https://github.com/OSGeo/gdal/blob/v3.0.1/gdal/NEWS):
== GDAL/OGR 3.0.0 - General Ch
>I am now preparing GRASS 7.8.1RC1.
see comment in:
https://github.com/OSGeo/grass/pull/136#issuecomment-547353924
--
should we now merge also this PR? or do we have to adapt OSGeo4W env first?
-
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Gras
Markus Neteler wrote
> On Tue, Oct 29, 2019 at 8:46 AM Markus Metz
> <
> markus.metz.giswork@
> > wrote:
>> On Mon, Oct 28, 2019 at 9:18 PM Helmut Kudrnovsky <
> hellik@
> > wrote:
>> >
>> > Helmut Kudrnovsky wrote
>> > >&g
Helmut Kudrnovsky wrote
> thanks for the merge!
>
> see https://lists.osgeo.org/pipermail/grass-dev/2019-October/093436.html
>
>
> ##
> see comment in:
>
> https://github.com/OSGeo/grass/pull/136#issuecomment-547353924
>
> --
> should
hi devs,
see
http://osgeo-org.1560.x6.nabble.com/WinGRASS-build-up-WIP-tp5420766p5421066.html
upcoming winGRASS 7.8.1 will be out with gdal3 and proj6:
###
GRASS is now configured for: x86_64-w64-mingw32
Source directory: /usr/src/rc_nexgen/grass-7.8.1RC1
Build direc
>I would like to promote RC2 incl two more fixes, see
>
>https://github.com/OSGeo/grass/compare/7.8.1RC2...releasebranch_7_8
>
>to GRASS GIS 7.8.1 final.
+1
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
_
Pedro Venâncio-2 wrote
> Hi Markus and Markus,
>
> I hope someone else can test, because here in my machine:
>
> - GRASS 7.8.1 standalone 64bits does not work;
> - GRASS 7.8.0 standalone 64bits work fine;
> - GRASS 7.8.1 from OSGeo4W64 does not work, also inside QGIS;
> - GRASS 7.8.0 from OSGeo4W
Pedro Venâncio-2 wrote
> Hi Markus and Markus,
>
> I hope someone else can test, because here in my machine:
>
> - GRASS 7.8.1 standalone 64bits does not work;
> - GRASS 7.8.0 standalone 64bits work fine;
> - GRASS 7.8.1 from OSGeo4W64 does not work, also inside QGIS;
> - GRASS 7.8.0 from OSGeo4W
Helmut Kudrnovsky wrote
> Pedro Venâncio-2 wrote
>> Hi Markus and Markus,
>>
>> I hope someone else can test, because here in my machine:
>>
>> - GRASS 7.8.1 standalone 64bits does not work;
>> - GRASS 7.8.0 standalone 64bits work fine;
>> - GRASS 7.
Markus Neteler wrote
> Hi devs,
>
> some important issues have been discovered:
>
> - gdal300.dll/libgdal.so.26. were not registered in lib/raster/gdal.c
> - missing backport of https://github.com/OSGeo/grass/pull/155 (now done)
>
> open:
> https://trac.osgeo.org/grass/query?status=new&status=as
Pedro Venâncio-2 wrote
> Hi Jurgen,
>
>
>
>> Try dependency walker called from the GRASS prompt and load gdal300.dll.
>> There's probably something missing that the dll needs or conflicting in
>> system32 that takes precendence over something shipped with OSGeo4W (see
>> also
>> [0])
>>
>>
> I'm
Pedro Venâncio-2 wrote
> Hi Jurgen,
>
>
>
>> Try dependency walker called from the GRASS prompt and load gdal300.dll.
>> There's probably something missing that the dll needs or conflicting in
>> system32 that takes precendence over something shipped with OSGeo4W (see
>> also
>> [0])
>>
>>
> I'm
Pedro Venâncio-2 wrote
> Hi Helmut,
>
>
> What is gdalinfo --version in the OSGeo4W shell telling?
>>
>
>
> C:\OSGeo4W64>gdalinfo --version
> GDAL 3.0.2, released 2019/10/28
try to type into the OSGeo4W shell:
C:\>where gdal300.dll
result here:
C:\OSGeo4W64\bin\gdal300.dll
-
best re
Pedro Venâncio-2 wrote
> Hi Helmut,
>
>
> What is gdalinfo --version in the OSGeo4W shell telling?
>>
>
>
> C:\OSGeo4W64>gdalinfo --version
> GDAL 3.0.2, released 2019/10/28
and type the same in a normal windows console, here:
C:\Users\myusername>where gdal300.dll
INFORMATION: no file with t
>Do you see anything suspicious?
Nothing obvious
>The message I get (screenshot attached) is something like "It was >not
possible to find the entry point of the procedure curl_mime_init >in the DLL
C:\OSGEO4~1\bin\gdal300.dll".
ok, I think we're narrowing down the issue now.
I've seen there w
>Updated now, but same error when running any algorithm.
Search in the log files for curl and similar and look which library uses
curl, then repeat where in the OSGeo4W shell and a normal Windows cmd line
with this library name
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6
>I'd
>uninstalled everything related with QGIS, GRASS, GDAL, GMT, etc, >and
installed again from OSGeo4W.
>
>At t
>he final stages of OSGeo4W installation, I get the same >curl_mime_init
error with crssync.exe, but referring to gdal301.dll >(image attached).
Are you installing OSGeo4W stack with
>gdal-dev was because I was also installing QGIS 3.10.
checking here:
QGIS version 3.10.0-A Coruña
Compiled against Qt 5.11.2
Compiled against GDAL/OGR 3.0.2 <=
Compiled against GEOS 3.8.0-CAPI-1.13.1
Compiled against SQLite 3.29.0
PostgreSQL Client Version 11.5
3.10.0 is now available in OSGeo
>>sounds good. more winGRASS testing needed though.
>Is much missing yet?
a little more winGRASS testing done, no blocking issues so far.
+1 for starting the release cycle.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
__
Markus Neteler wrote
> Hi,
>
> GRASS GIS 7.8.2RC2 has been released:
>
> https://github.com/OSGeo/grass/releases/tag/7.8.2RC2
winGRASS 7.8.2RC2 64bit is available for testing in OSGeo4W 64bit when the
experimental/testing tick is activated.
happy testing
-
best regards
Helmut
--
Sent fr
Kiersten wrote
> Hello everyone,
>
> Thank you so much for your speedy response!
>
> I'm using Windows 10, 64-bit. I used the stand-alone installer for GRASS
> 7.8, because I was having trouble with the OSGeo4W package. I got 7.8
> because it was the newest stable version. I downloaded 7.8.2, aga
while starting
--
System Info
GRASS version: 7.9.dev
Code revision: 3a24c8c74
Build date: 2020-01-18
Hi,
just opened OSGeo4W winGRASS 7.8.2 in the OSGeo4W environment. it just
worked up to a few days ago.
build information:
###
C:\>g.version -breg
version=7.8.2
date=2019
revision=3900fb114
build_date=2019-12-11
build_platform=x86_64-w64-mingw32
build_off_t_size=8
./configure --h
901 - 1000 of 1047 matches
Mail list logo
