Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

[Helmut Kudrnovsky]

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's keep discussions in one place.
>>>
>>
>> I agree, and I get the notifications:
>> https://help.github.com/en/articles/watching-and-unwatching-repositories
>>
> 
> 
> Then please all promise to subscribe to the repo notifications and look at
> them :)

already subscribed.

somekind related

in https://trac.osgeo.org/grass/wiki/HowToGit there is mentioned:


# 
vim ...

# list local changes
git status
git add file1.c file2.py ...
git commit -m 'my change with reasonable explanation...'


at least here in the windows world of git I had to use


git commit -am 'my change with reasonable explanation...'


to add also the -a switch that anything happend  :-D

otherwise I get the message:


$ git commit -m 'add missing dependencies libgraphite2.dll and libpcre-1.dll
- see https://trac.osgeo.org/grass/ticket/3870'
On branch wingrass_fixes
Changes not staged for commit:
modified:   mswindows/osgeo4w/package.sh

no changes added to commit




-
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
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wingrass builds status (git recover)

[Helmut Kudrnovsky]

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

see

https://github.com/OSGeo/grass/pull/53




-
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
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3870: add missing depencencies into winGRASS

[GRASS GIS]

#3870: add missing depencencies into winGRASS
+-
  Reporter:  hellik |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:  8.0.0
 Component:  Packaging  |Version:  svn-trunk
Resolution: |   Keywords:
   CPU:  All|   Platform:  MSWindows
+-

Comment (by hellik):

 Replying to [ticket:3870 hellik]:
 >
 > missing dlls libgraphite2.dll and libpcre-1.dll have to be added to
 winGRASS.

 see

 https://github.com/OSGeo/grass/pull/53

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

[GRASS GIS]

#3867: menudata.py: global name 'error_handler' is not defined
--+-
  Reporter:  marisn   |  Owner:  wenzeslaus
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.4.5
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by hcho):

 Also, those who cannot reproduce this specific issue, please check your
 make log and see if there are a lot of "Cannot parse interface for module"
 errors without and with this PR.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

[GRASS GIS]

#3867: menudata.py: global name 'error_handler' is not defined
--+-
  Reporter:  marisn   |  Owner:  wenzeslaus
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.4.5
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by hcho):

 Hm... get_interface_description.. Looks familiar. Maybe, related to
 https://github.com/OSGeo/grass/pull/46. Please try it.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] g.extension: still fetching from SVN?

[Markus Neteler]

Hi

Markus Neteler  schrieb am Mo., 1. Juli 2019, 17:47:

> On Mon, Jul 1, 2019 at 3:37 PM Martin Landa 
> wrote:
> >
> > Hi,
> >
> > ne 30. 6. 2019 v 23:15 odesílatel Markus Neteler 
> napsal:
> > > We have tested it in our office, it still points to SVN.
> >
> > yes, its still pointing to SVN. I will try to take a look on this
> > issue after solving wingrass builds. Volunteers welcome in in case. Ma
>
> After Anika's pull request it points to Github!
> Please just test it...
>
> Note: the only way we found is to use "svn export" in order to fetch a
> subdir from https://github.com/OSGeo/grass-addons/
> A dirty hack but apparently no other way when one does not want to
> clone the entire repo for a single addon.
>


In absence of feedback I have recently merged it.

Still the backports are needed.
I'm traveling with phone only, anyone to do that?

Thanks,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3870: add missing depencencies into winGRASS

[GRASS GIS]

#3870: add missing depencencies into winGRASS
---+-
 Reporter:  hellik |  Owner:  grass-dev@…
 Type:  defect | Status:  new
 Priority:  normal |  Milestone:  8.0.0
Component:  Packaging  |Version:  svn-trunk
 Keywords: |CPU:  All
 Platform:  MSWindows  |
---+-
 see

 https://lists.osgeo.org/pipermail/grass-dev/2019-July/092916.html

 {{{
 >> [1]
 >>
 https://github.com/OSGeo/grass/blob/master/mswindows/osgeo4w/package.sh#L260
 >
 > ok
 >
 > there is libharfbuzz-0.dll in the list; see
 >
 > https://github.com/msys2/MINGW-packages/issues/1322
 >
 > /A new version of harfbuzz is requires -lgraphite2 but graphite2 mingw
 > package dont have libgraphite2.a./
 >
 > so it seems it's a dependency problem with the new dependencies.

 yes it is a dependency problem with the new dependencies. :-)

 looking deeper

 wingrass at DESKTOP-VADT8Q4 MSYS ~
 $ pacman -Ss graphite
 mingw32/mingw-w64-i686-graphite2 1.3.13-1
 Font rendering capabilities for complex non-Roman writing systems
 (mingw-w64)
 mingw64/mingw-w64-x86_64-graphite2 1.3.13-1 [installed]
 Font rendering capabilities for complex non-Roman writing systems
 (mingw-w64)

 C:\msys64\mingw64\bin\libgraphite2.dll


 wingrass at DESKTOP-VADT8Q4 MSYS ~
 $ pacman -Ss pcre
 mingw32/mingw-w64-i686-pcre 8.43-1
 A library that implements Perl 5-style regular expressions (mingw-w64)
 mingw32/mingw-w64-i686-pcre2 10.33-1
 A library that implements Perl 5-style regular expressions (mingw-w64)
 mingw32/mingw-w64-i686-re2 20190701-1
 A fast, safe, thread-friendly alternative to backtracking regular
 expression engines like those used in PCRE, Perl, and Python (mingw-w64)
 mingw64/mingw-w64-x86_64-pcre 8.43-1 [installed]
 A library that implements Perl 5-style regular expressions (mingw-w64)
 mingw64/mingw-w64-x86_64-pcre2 10.33-1
 A library that implements Perl 5-style regular expressions (mingw-w64)
 mingw64/mingw-w64-x86_64-re2 20190701-1
 A fast, safe, thread-friendly alternative to backtracking regular
 expression engines like those used in PCRE, Perl, and Python (mingw-w64)
 msys/libpcre 8.43-2 (libraries) [installed]
 A library that implements Perl 5-style regular expressions
 msys/libpcre16 8.43-2 (libraries) [installed]
 A library that implements Perl 5-style regular expressions
 msys/libpcre2_16 10.33-2 (libraries)
 A library that implements Perl 5-style regular expressions
 msys/libpcre2_32 10.33-2 (libraries)
 A library that implements Perl 5-style regular expressions
 msys/libpcre2_8 10.33-2 (libraries) [installed]
 A library that implements Perl 5-style regular expressions
 msys/libpcre2posix 10.33-2 (libraries)
 A library that implements Perl 5-style regular expressions
 msys/libpcre32 8.43-2 (libraries) [installed]
 A library that implements Perl 5-style regular expressions
 msys/libpcrecpp 8.43-2 (libraries) [installed]
 A library that implements Perl 5-style regular expressions
 msys/libpcreposix 8.43-2 (libraries) [installed]
 A library that implements Perl 5-style regular expressions
 msys/pcre 8.43-2 [installed]
 A library that implements Perl 5-style regular expressions
 msys/pcre-devel 8.43-2 (development)
 PCRE headers and libraries
 msys/pcre2 10.33-2
 A library that implements Perl 5-style regular expressions
 msys/pcre2-devel 10.33-2 (development)
 PCRE headers and libraries

 C:\msys64\mingw64\bin\libpcre-1.dll

 both missing dlls are in my msys2 build environment;

 copying these into C:\OSGeo4W64\apps\grass\grass77\bin solves the problem.

 will open a ticket and hopefully my first PR :-)
 }}}

 missing dlls libgraphite2.dll and libpcre-1.dll have to be added to
 winGRASS.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wingrass builds status (git recover)

[Martin Landa]

Hi,

po 15. 7. 2019 v 21:58 odesílatel Helmut Kudrnovsky  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

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

[Even Rouault]

> 
> Patches in svn tickets sometimes got old too. When no one cares (or has
> time), then it doesn't matter if we use svn or github. I would say PRs on
> github are easier to find and track than what we used before, 

> although seem
> harder to test, but that's what we signed up for.

Given a pull request of number ID, that's just a 2-liner:

git fetch origin pull/{ID}/head:pr-{ID}
git checkout pr-{ID}

(more verbose explanations at
https://help.github.com/en/articles/checking-out-pull-requests-locally )

But actually, you should rarely need to test a pull request locally if you 
take care of checking that the pull request which adds new functionality comes 
with associated tests. And if it is a bugfix, hopefully your test suite should 
already test them modified code. If not, then that's the opportunity for the 
pull request to add that new test.

Pull request do work well with a strong test suite.

Looks like https://github.com/OSGeo/grass/blob/master/.travis/linux.script.sh 
is missing a "make check" target :-)

Even


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wingrass builds status (git recover)

[Helmut Kudrnovsky]

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.mkfontcap.exe - system error because libgraphite2.dll and
>>> libpcre-1.dll
>>> can't be found
>>> ° "inflateValidate" in the dll
>>> C:\OSGeo4W\apps\grass\grass77\bin\libpng16-16.dll can't be found
>> 
>> hm, something related to a new build environment. No idea at this moment.
>> 
>>> regarding the last issue item, in C:\OSGeo4W\apps\grass\grass77\bin\
>>> there
>>> shouldn't be any foreign dll, right?
>> 
>> These libraries are copied from msys2 build environment [1]. They are
>> needed since GRASS is built against them. Btw, they are not copied to
>> C:\OSGeo4W64\bin to avoid any potential conflict with other osgeo4w
>> packages (GRASS is the only one osgeo4w package built in msys2
>> environment I guess).
>> 
>> Ma
>> 
>> [1]
>> https://github.com/OSGeo/grass/blob/master/mswindows/osgeo4w/package.sh#L260
> 
> ok
> 
> there is libharfbuzz-0.dll in the list; see
> 
> https://github.com/msys2/MINGW-packages/issues/1322
> 
> /A new version of harfbuzz is requires -lgraphite2 but graphite2 mingw
> package dont have libgraphite2.a./
> 
> so it seems it's a dependency problem with the new dependencies.

yes it is a dependency problem with the new dependencies. :-)

looking deeper

wingrass@DESKTOP-VADT8Q4 MSYS ~
$ pacman -Ss graphite
mingw32/mingw-w64-i686-graphite2 1.3.13-1
Font rendering capabilities for complex non-Roman writing systems
(mingw-w64)
mingw64/mingw-w64-x86_64-graphite2 1.3.13-1 [installed]
Font rendering capabilities for complex non-Roman writing systems
(mingw-w64)

C:\msys64\mingw64\bin\libgraphite2.dll


wingrass@DESKTOP-VADT8Q4 MSYS ~
$ pacman -Ss pcre
mingw32/mingw-w64-i686-pcre 8.43-1
A library that implements Perl 5-style regular expressions (mingw-w64)
mingw32/mingw-w64-i686-pcre2 10.33-1
A library that implements Perl 5-style regular expressions (mingw-w64)
mingw32/mingw-w64-i686-re2 20190701-1
A fast, safe, thread-friendly alternative to backtracking regular
expression engines like those used in PCRE, Perl, and Python (mingw-w64)
mingw64/mingw-w64-x86_64-pcre 8.43-1 [installed]
A library that implements Perl 5-style regular expressions (mingw-w64)
mingw64/mingw-w64-x86_64-pcre2 10.33-1
A library that implements Perl 5-style regular expressions (mingw-w64)
mingw64/mingw-w64-x86_64-re2 20190701-1
A fast, safe, thread-friendly alternative to backtracking regular
expression engines like those used in PCRE, Perl, and Python (mingw-w64)
msys/libpcre 8.43-2 (libraries) [installed]
A library that implements Perl 5-style regular expressions
msys/libpcre16 8.43-2 (libraries) [installed]
A library that implements Perl 5-style regular expressions
msys/libpcre2_16 10.33-2 (libraries)
A library that implements Perl 5-style regular expressions
msys/libpcre2_32 10.33-2 (libraries)
A library that implements Perl 5-style regular expressions
msys/libpcre2_8 10.33-2 (libraries) [installed]
A library that implements Perl 5-style regular expressions
msys/libpcre2posix 10.33-2 (libraries)
A library that implements Perl 5-style regular expressions
msys/libpcre32 8.43-2 (libraries) [installed]
A library that implements Perl 5-style regular expressions
msys/libpcrecpp 8.43-2 (libraries) [installed]
A library that implements Perl 5-style regular expressions
msys/libpcreposix 8.43-2 (libraries) [installed]
A library that implements Perl 5-style regular expressions
msys/pcre 8.43-2 [installed]
A library that implements Perl 5-style regular expressions
msys/pcre-devel 8.43-2 (development)
PCRE headers and libraries
msys/pcre2 10.33-2
A library that implements Perl 5-style regular expressions
msys/pcre2-devel 10.33-2 (development)
PCRE headers and libraries

C:\msys64\mingw64\bin\libpcre-1.dll

both missing dlls are in my msys2 build environment;

copying these into C:\OSGeo4W64\apps\grass\grass77\bin solves the problem.

will open a ticket and hopefully my first PR :-)




-
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
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3861: winGRASS master (git) - g.proj not found at startup

[GRASS GIS]

#3861: winGRASS master (git) - g.proj not found at startup
--+
  Reporter:  hellik   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Startup  |Version:  svn-trunk
Resolution:  fixed|   Keywords:  python3, py3, wingrass
   CPU:  x86-64   |   Platform:  MSWindows
--+
Changes (by martinl):

 * status:  new => closed
 * resolution:   => fixed


-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

[Anna Petrášová]

On Mon, Jul 15, 2019 at 12:07 PM Huidae Cho  wrote:

> Hi,
>
> The oldest PR is 2 months old. Using git for collaboration is very
> different from svn, I believe. Unlike with svn, you have to "actively"
> merge these PRs into your branch for testing (e.g., features interesting to
> you?) and wait for an approval from reviewers (?). Why did it not happen to
> these old PRs? Now, a less bigger question is no one cares about them and
> who is supposed to be responsible for reviewing and approving them?
>

Patches in svn tickets sometimes got old too. When no one cares (or has
time), then it doesn't matter if we use svn or github. I would say PRs on
github are easier to find and track than what we used before, although seem
harder to test, but that's what we signed up for.
If you want someone's review, you can request it. If not, you can merge it
yourself.

>
> For example, https://github.com/OSGeo/grass/pull/52 fixes a very obvious
> formatting issue, which still needs to be approved? Tried to approve it
> myself, but self-nominating myself as a reviewer is pending... Hmm... Can I
> even merge it? The merge button seems to be activated. Confused...
>

I actually asked in the related ticket for testing because I couldn't
reproduce the problem (the formatting influences unicode/bytes). I didn't
merge it because there is always a chance more changes might be needed and
then you can update the PR and squash the commits and keep it nice and
clean.

Anna

>
> Best,
> Huidae
>
> On Mon, Jul 15, 2019 at 6:53 AM Markus Neteler  wrote:
>
>> Hi
>>
>> Anna Petrášová  schrieb am Mo., 15. Juli 2019,
>> 05:57:
>>
>>>
>>>
>>> On Fri, Jul 12, 2019 at 12:50 PM Maris Nartiss 
>>> wrote:
>>>
 The biggest question is – do we need PR notifications here. I would
 vote for no. Better let's keep discussions in one place.

>>>
>>> I agree, and I get the notifications:
>>> https://help.github.com/en/articles/watching-and-unwatching-repositories
>>>
>>
>>
>> Then please all promise to subscribe to the repo notifications and look
>> at them :)
>>
>> Thanks
>> Markus
>>
>> PS: with "lost" I meant that nobody cares/d. Perhaps since many didn't
>> subscribe to notifications yet...
>>
>>>

>
> --
> Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE
> Open Source GIS Developer, GRASS GIS Development Team
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wingrass builds status (git recover)

[Helmut Kudrnovsky]

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 and
>> libpcre-1.dll
>> can't be found
>> ° "inflateValidate" in the dll
>> C:\OSGeo4W\apps\grass\grass77\bin\libpng16-16.dll can't be found
> 
> hm, something related to a new build environment. No idea at this moment.
> 
>> regarding the last issue item, in C:\OSGeo4W\apps\grass\grass77\bin\
>> there
>> shouldn't be any foreign dll, right?
> 
> These libraries are copied from msys2 build environment [1]. They are
> needed since GRASS is built against them. Btw, they are not copied to
> C:\OSGeo4W64\bin to avoid any potential conflict with other osgeo4w
> packages (GRASS is the only one osgeo4w package built in msys2
> environment I guess).
> 
> Ma
> 
> [1]
> https://github.com/OSGeo/grass/blob/master/mswindows/osgeo4w/package.sh#L260

ok

there is libharfbuzz-0.dll in the list; see

https://github.com/msys2/MINGW-packages/issues/1322

/A new version of harfbuzz is requires -lgraphite2 but graphite2 mingw
package dont have libgraphite2.a./

so it seems it's a dependency problem with the new dependencies.



-
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
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wingrass builds status (git recover)

[Helmut Kudrnovsky]

>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/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3861: winGRASS master (git) - g.proj not found at startup

[GRASS GIS]

#3861: winGRASS master (git) - g.proj not found at startup
--+
  Reporter:  hellik   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Startup  |Version:  svn-trunk
Resolution:   |   Keywords:  python3, py3, wingrass
   CPU:  x86-64   |   Platform:  MSWindows
--+

Comment (by hellik):

 Replying to [comment:1 hcho]:
 > https://github.com/OSGeo/grass/pull/48 This PR should fix it.

 the issue seems to be fixed; closing the ticket.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wingrass builds status (git recover)

[Helmut Kudrnovsky]

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 msys2 environment it seems that this problem
> disappeared. Please try build no. 2+. Ma

tested now build no. 3, the libng-dll issue seems to be solved; but stilll
here the problem with

° g.mkfontcap.exe - system error because libgraphite2.dll and libpcre-1.dll
can't be found

>probably relevant,
>https://github.com/gtk-rs/gtk/issues/539#issuecomment-442993185

in that link:

>I had the same issue with msys2 and Qt. It turned out that there was
another version of zlib1.dll in PATH. 

zlib1.dll is here in 

C:\OSGeo4W64\apps\grass\grass77\bin
C:\OSGeo4W64\apps\Python37\lib\site-packages\wx
C:\OSGeo4W64\bin
C:\OSGeo4W64\apps\saga\dll

If I start a winGRASS77 daily session:

C:\>where zlib1.dll
C:\OSGeo4W64\apps\grass\grass77\bin\zlib1.dll
C:\OSGeo4W64\bin\zlib1.dll

If a search in a windows command line:

C:\Users\>where zlib1.dll
C:\Program Files\Intel\WiFi\bin\zlib1.dll




-
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
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

[Huidae Cho]

Hi,

The oldest PR is 2 months old. Using git for collaboration is very
different from svn, I believe. Unlike with svn, you have to "actively"
merge these PRs into your branch for testing (e.g., features interesting to
you?) and wait for an approval from reviewers (?). Why did it not happen to
these old PRs? Now, a less bigger question is no one cares about them and
who is supposed to be responsible for reviewing and approving them?

For example, https://github.com/OSGeo/grass/pull/52 fixes a very obvious
formatting issue, which still needs to be approved? Tried to approve it
myself, but self-nominating myself as a reviewer is pending... Hmm... Can I
even merge it? The merge button seems to be activated. Confused...

Best,
Huidae

On Mon, Jul 15, 2019 at 6:53 AM Markus Neteler  wrote:

> Hi
>
> Anna Petrášová  schrieb am Mo., 15. Juli 2019,
> 05:57:
>
>>
>>
>> On Fri, Jul 12, 2019 at 12:50 PM Maris Nartiss 
>> wrote:
>>
>>> The biggest question is – do we need PR notifications here. I would
>>> vote for no. Better let's keep discussions in one place.
>>>
>>
>> I agree, and I get the notifications:
>> https://help.github.com/en/articles/watching-and-unwatching-repositories
>>
>
>
> Then please all promise to subscribe to the repo notifications and look at
> them :)
>
> Thanks
> Markus
>
> PS: with "lost" I meant that nobody cares/d. Perhaps since many didn't
> subscribe to notifications yet...
>
>>
>>>

-- 
Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE
Open Source GIS Developer, GRASS GIS Development Team
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS GIS at FOSS4G

[Martin Landa]

Hi,

po 15. 7. 2019 v 11:00 odesílatel Ondřej Pešek  napsal:
>> - Have you all booked housing already ? If not, should we try to find
>>   some place (e.g. appartment) which could also be a place to work
>>   together, or should we ask whether a room might be available at the
>>   FOSS4G premises ?
>>
>
> So what's the state of this? Should I book something on myself or do we want 
> to try to set up a grassy place?

at the end I would be also interested to join. Our plan to come with
family will be probably cancelled. Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

[Markus Neteler]

Hi

Anna Petrášová  schrieb am Mo., 15. Juli 2019, 05:57:

>
>
> On Fri, Jul 12, 2019 at 12:50 PM Maris Nartiss 
> wrote:
>
>> The biggest question is – do we need PR notifications here. I would
>> vote for no. Better let's keep discussions in one place.
>>
>
> I agree, and I get the notifications:
> https://help.github.com/en/articles/watching-and-unwatching-repositories
>


Then please all promise to subscribe to the repo notifications and look at
them :)

Thanks
Markus

PS: with "lost" I meant that nobody cares/d. Perhaps since many didn't
subscribe to notifications yet...

>
>>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS GIS at FOSS4G

[Ondřej Pešek]

Hi,

st 5. 6. 2019 v 22:21 odesílatel Moritz Lennert <
mlenn...@club.worldonline.be> napsal:

> - Have you all booked housing already ? If not, should we try to find
>   some place (e.g. appartment) which could also be a place to work
>   together, or should we ask whether a room might be available at the
>   FOSS4G premises ?
>
>
So what's the state of this? Should I book something on myself or do we
want to try to set up a grassy place?

Ondrej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev