Jachym Cepicky wrote
> Hi,
>
> sorry for too rush approach, you can certainly revert the commit
the commit seems to break winGRASS compilation:
https://wingrass.fsv.cvut.cz/grass75/x86_64/logs/log-r72590-111/error.log
[...]
fyi
https://lists.osgeo.org/pipermail/qgis-developer/2018-April/052916.html
---
Hi all,
Please see https://github.com/qgis/QGIS-Enhancement-Proposals/issues/120
for a new QEP regarding handling of optional parameter groups for
processing algorithms,
NikosAlexandris wrote
> Yet my intention was/is to use a hardcoded string of rules. Not a path to
> a file.
>
> It appears the only option is to document, the rules, and suggest a copy
> and paste in to the corresponding field.
>
> Can the parser be extended in this regard with yet another
Radek Novotný wrote
> Hi everybody!
>
> My name is Radek Novotny and I'm an MSc student in geomatics at CTU in
> Prague. I'm very happy that my proposal "Improve GRASS GIS integration in
> QGIS 3" has been selected to GSoC 2018.
>
> There is the link to my proposal:
>
>I have no idea of a possible python command.. I will do some >search.. Have
you any suggestion?
Have a look into pygrass
https://grass.osgeo.org/grass74/manuals/libpython/pygrass_vector.html
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
>Removing the mapset from input name (ztd_temp@meteo --> >ztd_temp) the
module works correctly. I do not know how to solve >this problem. Perhaps it
has an easy solution for you.
Just have a look into GRASS scripts, e.g.
>Now (last related commit is trunk r72522) it's finished. I have >introduced
a new GRASS API that handles both PROJ 4 and PROJ >5, consisting of
Thanks for this Update!
Fyi See
https://lists.osgeo.org/pipermail/osgeo4w-dev/2018-March/003557.html
---
[...]
The API from PROJ 4 lives on in
Markus Neteler wrote
> Hi,
>
> as per
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>
> I have created a "GRASS GIS dev" team here:
> https://github.com/orgs/OSGeo/teams/grass-gis/members
>
> ... who wants to join, please speak up (and send your account
just seen in
https://wingrass.fsv.cvut.cz/grass75/x86_64/logs/log-r72399-97/error.log
that winGRASS daily builds seems to be broken.
Local winGRASS compiling works:
GRASS GIS 7.5.svn r72458M compilation log
--
Started compilation: Wed Mar 21
Some migration hints:
https://kbevers.github.io/development/migration.html
Markus Neteler wrote
> FYI
>
> -- Forwarded message --
> From: Kristian Evers
> kreve@
>
> Date: Thu, Mar 1, 2018 at 9:10 PM
> Subject: Re: [Proj] PROJ 5.0.0 Released
> To: "PROJ.4 and general
Markus Neteler wrote
> Hi devs,
>
> according to our roadmap [1] it is time to prepare 7.4.1RC1:
>
> Time schedule:
>
> Proposal of release: ~14 Mar
> Soft freeze of release branch: ~23 Mar
> RC1: ~23 Apr <<-- we are here
> RC2: ~7 May
> Final release: ~14 May
>
>
>How do we compile and package a single GRASS GIS Addon >binary to proceed
>with testing under Windows?
see
https://wingrass.fsv.cvut.cz/grass77/x86_64/addons/grass-7.7.svn/
for the precompiled wingrass addons.
have a look into one of the zip File how the structure looks like.
-
>3. QGIS GRASS Plugin
I think QGIS GRASS Plugin is something different; it's not about using GRASS
modules/addons in QGIS
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
reading in [1], there are new GRASS dependencies in OSGeo4W available:
- PROJ 5.2.0 (from 4.9.3; plus datumgrids)
- GEOS 3.7.0 (from 3.6.2)
- SpatiaLite 4.3.0a (from 4.3.0; also with lwgeom from postgis 2.5)
- GDAL 2.3.2 (from 2.2.4; including updated/rebuilt dependencies ogdi &
openfyba)
at
there were quite a lot changes lately in the OSGeo4W environment.
---
trying to start the long installed GRASS 7.4.1
C:\>Traceback (most recent call last):
File "C:\OSGEO4~1\apps\grass\grass-7.4.1\gui\wxpython\wxgui.py", line 167,
in
sys.exit(main())
>oh my!
>I'll teach a one week course to windows users next week and I strongly
recommend students to install >GRASS through OSGeo4W because it is the
easiest way to use bash tricks... I'm kinda panicking with this >email, I
tested 3 weeks ago or so and all worked just fine...
it seems to be
Markus Neteler wrote
> On Thu, Oct 18, 2018 at 1:59 PM Martin Landa
> landa.martin@
> wrote:
>> čt 18. 10. 2018 v 13:42 odesílatel Martin Landa
> landa.martin@
> napsal:
>> > About PROJ4/5. My suggestion:
>>
>> New GDAL package is built against PROJ5. Result also PROJ has been
>> switch to
>good news: newly upload 64bit grass package (grass-7.4.1-3) is fixed
confirmed, grass-7.4.1-3 64bit is up again! thanks!
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
wenzeslaus wrote
> On Wed, Oct 17, 2018 at 11:54 AM Helmut Kudrnovsky
> hellik@
> wrote:
>
>> reading in [1], there are new GRASS dependencies in OSGeo4W available:
>>
>> ...
>>
>
> Any chance you can also add dependencies? Specifically,
>5. Ondřej suggested also another possibility: if an Addon is >installed,
maybe
>then, inside QGIS: GRASS GIS Plugin > GRASS GIS shell > run `r.>
--ui`
>would suffice?
>
>Any Windows user possibly to try this last option?
What is a GRASS GIS shell within the QGIS GRASS plugin?
-
best
hi,
while installing the latest OSGeo4W-winGRASS7.7.svn here, I get following
error:
"Unable to extract
/apps/grass/grass-7.7.svn/locale/ar/LC_MESSAGES/grassmods.mo -- corrupt
package?"
maybe related to r73594 or r73596 or r73600?
-
best regards
Helmut
--
Sent from:
Hi,
just tested following here with [1]:
- OSGeo4W-winGRASS-console: starting bash:
C:\>bash
GRASS 7.4.2>
- to see if env var are still there, e.g.
GRASS 7.4.2> echo $GRASS_PYTHON
C:\OSGEO4~1\bin\python.exe
the variables set beforehand are still there
- starting a binary grass module there:
Markus Neteler wrote
> On Wed, Oct 24, 2018 at 6:30 PM Helmut Kudrnovsky
> hellik@
> wrote:
>>
>> hi,
>>
>> while installing the latest OSGeo4W-winGRASS7.7.svn here, I get following
>> error:
>>
>> "Unable to extract
>> /apps/gra
Markus Neteler wrote
> Helmut Kudrnovsky
> hellik@
> schrieb am Fr., 26. Okt. 2018, 17:48:
>
>> Markus Neteler wrote
>> > On Wed, Oct 24, 2018 at 6:30 PM Helmut Kudrnovsky
>>
>> > hellik@
>>
>> > wrote:
>> >>
>> >
>> * fix daily builds (still broken)
>
>64bit were built,
confirmed, 64bit daily builds are up again. thanks Martin!
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
>C:\>grass74
>Cleaning up temporary files...
>Starting GRASS GIS...
>ERROR: Invalid return code from GUI startup script.
>Please advise GRASS developers of this error.
>Exiting...
>Press any key to continue . . .
what is the invalid return code?
is there another python installation on this
>Running GRASS from the command line, works perfectly:
>
>C:\>grass74 -text
>Cleaning up temporary files...
>Starting GRASS GIS...
>ATENÇÃO: Concurrent mapset locking is not supported on Windows
what is happening when you're in text mode and do
C:\>g.gui wxpython
?
-
best regards
Helmut
for the record to the ML, see below
-
Gesendet: Dienstag, 02. Oktober 2018 um 22:45 Uhr
Von: "Charles Karney"
An: "Markus Metz"
Cc: "Kristian Evers", &quo
for the record in the ML see below
Gesendet: Dienstag, 02. Oktober 2018 um 19:30 Uhr
Von: "Charles Karney" <>
An: "Kristian Evers" <>, "Markus Metz" <>
Cc: "G
Markus Neteler wrote
>>> Could you please post a few lines how to properly do the testing with
>>> virtualenv?
>>
>> https://trac.osgeo.org/grass/wiki/Python3Support#Howtotest
>
> Thanks.
> I took liberty to expand that section a bit (a bit more text; and with
> hints for Fedora users as well).
Anna Petrášová wrote
> https://trac.osgeo.org/grass/wiki/Python3Support#Howtotest
>
> also, we have now new small dependency - Python 'six' package
updated the winGRASS compiling guidelines regarding python3 and six.
[1] https://trac.osgeo.org/grass/wiki/CompileOnWindows
-
best regards
>Can you add optparse package? It's weird, it should be part of >standard
Python library:
>https://docs.python.org/3.7/library/optparse.html
Looking at these Docs:
37.1. optparse — Parser for command line options¶
Source code: Lib/optparse.py
Deprecated since version 3.2: The optparse
>compiling winGRASS-python3 along this notes [but forgotten to do svn up
>;-)]
it seems I did svn up, source status was quite new.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev
Helmut Kudrnovsky wrote
> Markus Neteler wrote
>>>> Could you please post a few lines how to properly do the testing with
>>>> virtualenv?
>>>
>>> https://trac.osgeo.org/grass/wiki/Python3Support#Howtotest
>>
>> Thanks.
>&g
[taken from
https://lists.osgeo.org/pipermail/grass-stats/2018-September/001783.html]
---
[...]
I'm also concerned to know how rgrass7 should be maintained going forward?
Should it be on github/r-spatial ? Should it migrate to sf/raster classes?
--
Roger Bivand
Department of
>Here are GRASS area measures for the given geometry:
>In WGS84: 14718097678.6716
tested here with winGRASS 7.7.svn in a wgs84 Location:
m2|km2
14718097678,673|14.718,097679
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
fyi see
https://lists.osgeo.org/pipermail/qgis-developer/2018-September/054644.html
with GRASS mentioned
--
Kristian Evers:
Right, here are the calculated areas as returned by a number of different
GIS applications and the planimeter app of GeographicLib for reference:
Caris
>The question is: do we need a RC cycle or can we release this time
>straight?
as time is very short, not sure if RC 1 will be tested.
I'm in favour to release straight.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
>I am all for it!
>Do we really need a RC2? I checked the post-RC1 changes and >cannot see
>anything untested.
+1 for a release.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev
NikosAlexandris wrote
> At times I think of Linux having some complicated ways
> to combine file (through make), to copy them around and still keep
> programs interacting and working. In the end there is a bigger picture
> and I reach a point of some understanding.
>
> After some
>>>~/.grass7/addons
>>> 'C:\Users\nik\.grass7\addons\bin'.
>>
>>such folder structures like should be avoided; no roaming possible
>
>Perhaps this is where OSGeo4W installs GRASS GIS?
No, Osgeo4w winGRASS doesn't install addons in that directory
-
best regards
Helmut
--
Sent from:
Markus Neteler wrote
> Dear all,
>
> we rather urgently need to publish trunk as the new stable version in
> order to get rid of the current Python2 issues.
> Python2 is close to EOL and being slowly dropped. Our interfaces to
> other software including QGIS require Python3. Also packaging
Markus Neteler wrote
> Hi Luís,
>
> Am Fr., 23. Nov. 2018, 16:32 hat Luís Moreira de Sousa <
> luis.de.sousa@
>> geschrieben:
>
>> Dear all,
>>
>> I bumped over a glitch with the documentation for r.out.gdal. One of the
>> examples is:
>> r.out.gdal in=elevation output=elevation.tif
>Python executable is not present in the directory >"C:\OSGeo4W64\bin"
directory.
have you activated Python in osgeo4w?
how did you start the grass executable from "C:\OSGeo4W64\bin" directory.?
activate the grass package in osgeo4w and see if the package start.
-
best regards
Helmut
--
Markus Neteler wrote
> Hi,
>
> as per
> https://trac.osgeo.org/grass/milestone/7.4.3
> * Final release: 26 Nov 2018
>
> That's today - any objections here?
>
> Markus
> ___
> grass-dev mailing list
> grass-dev@.osgeo
>
Veronica Andreo wrote
>>
>> > If we
>> > want to release Python3-ready GRASS version so early we could
>> > integrate it to upcoming version 7.6.
>>
>
> please don't break the temporal framework in 76
I'm supportive to keep 76 in a productive state
Markus Neteler:
>> If not, then lets better
>If not, then lets better iron out all issues arising from transition
>to 3.
winGRASS7.7.svn (standalone and OSGeo4W) already switched to python3, see:
https://trac.osgeo.org/grass/ticket/3719
first issues already popped up, see:
https://trac.osgeo.org/grass/ticket/3723
more testing welcome.
NikosAlexandris wrote
> Dear Windows experts,
>
> in installing the add-on r.estimap.recreation under Windows, I get this
> error:
>
> ERROR: Unable to read manual page: [Errno 2] No such file or directory:
> 'C:\\OSGEO4~1\\apps\\grass\\grass-7.4.4\\docs\\html\\r.estimap.recreation.html'
>
>
fyi
https://erouault.blogspot.com/2018/12/srs-barn-raising-7th-report.html?m=1
a blog post about GDAL, PROJ, libgeotiff development which may affect also
GRASS.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
Markus Neteler wrote
> Hi devs,
>
> there is the request by the QGIS team to ensure that GRASS 7.4.4 comes
> out before 2019-01-18 (release date of QGIS 2.18.28) in order to offer
> in Processing the much requested "r.mapcalc.simple", see
> https://github.com/qgis/QGIS/pull/8444 .
>
> Since it
>> May we release?
>
>I'll do that later today
thanks for the QGIS friendship release
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
>On Win10 with GRASS 7.4.0 from OSGeo4W I can install and run (open the GUI)
of r.estimap.recreation
>without issue, though, when I run the module from CMD it opens both GUI and
the python script in a text >editor...
I can't reproduce it here.
-
best regards
Helmut
--
Sent from:
Anna Petrášová wrote
> Hi,
> I am trying to install standalone wingrass 7.7 on a Windows 10 virtual
> machine and I am getting zstd.dll not found, so GRASS won't start. Any
> idea?
It seems zstd is missing in the winGRASS package environment. Martin has to
add it there.
in the meantime, you can
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
--
[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
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
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
Dear OSGeo community,
It is time for *GSoC* [1] this year, so this is our starting information to get
involved!
If you are willing to act as a mentor [2], fill in this form:
< https://goo.gl/forms/njL27YLWBVensZ3m1 >
If you want to participate proposing ideas, you just need
to send us
fyi
[https://lists.osgeo.org/pipermail/gdal-dev/2019-January/049681.html]
--
All,
RFC 73 work has now been merged into master. Currently GDAL build
and runtime now depends on PROJ master
More details of the past month work at:
[https://lists.osgeo.org/pipermail/discuss/2019-January/038230.html]
---
Dear OSGeo Community,
this is a gentle reminder to our call for GSoC 2019 mentors and ideas.
If you want to mentor [1], fill in this form:
https://goo.gl/forms/njL27YLWBVensZ3m1
To complete
fyi
[https://lists.osgeo.org/pipermail/discuss/2019-February/038233.html]
---
Dear OSGeo community,
The organization application for GSoC ends on February 6.[1]
There are only a few hours left for your project to prepare an ideas list
for interested
>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
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
>
> ___
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
> č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.txt u
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:
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:
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
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
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.
97
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:
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
>> > em
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:
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 modif
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,
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 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
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
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 step
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@
>
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
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:
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 compil
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.
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
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, break
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
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
--
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
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:
>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:
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.
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
>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:
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
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
801 - 900 of 1003 matches
Mail list logo
