Re: [GRASS-dev] [GRASS GIS] #3422: UnicodeDecodeError in metadata (r.info) call in wxGUI

[GRASS GIS]

#3422: UnicodeDecodeError in metadata (r.info) call in wxGUI
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.4.5
 Component:  wxGUI|Version:  svn-trunk
Resolution:  fixed|   Keywords:  r.info encoding
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by annakrat):

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


Comment:

 Can't reproduce it, feel free to reopen.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Early "warning": upcoming switch of SVN to readonly mode for planned GitHub migration

[Martin Landa]

Hi,

pá 17. 5. 2019 v 16:28 odesílatel Martin Landa  napsal:
> migration done for core repo. Please REVIEW result at
>
> https://github.com/OSGeo/grass

you can also check logs of migration tools (`out` files) and
importantly messages modifications (`txt` files):

http://geo102.fsv.cvut.cz/~landa/grass-svn2git/

Thanks for review. We hope that everything is OK. 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] Early "warning": upcoming switch of SVN to readonly mode for planned GitHub migration

[Martin Landa]

Hi,

pá 17. 5. 2019 v 16:28 odesílatel Martin Landa  napsal:
> migration done for core repo. Please REVIEW result at
>
> https://github.com/OSGeo/grass

in the next step Trac tickets will be migrated to github issue system
(in next days/weeks). This is a reason why issues are disabled at this
time in github.

IMPORTANT - till the date when issues migration will be announced:

* still use trac ticket system to report new issues/edit existing issues
* don't use shortcuts (#) in commit messages(!!!), use FULL URL
instead, eg. "bla, bla (see https://trac.osgeo.org/grass/ticket/2363).

Thanks! 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] Early "warning": upcoming switch of SVN to readonly mode for planned GitHub migration

[Luca Delucchi]

On Fri, 17 May 2019 at 16:28, Martin Landa  wrote:
>
> Hi,
>

Hi,

> pá 17. 5. 2019 v 9:25 odesílatel Martin Landa  napsal:
> > > later tonight or tomorrow (Friday, May 17th, 2010) we'll switch the
> > > GRASS GIS svn server to readonly-mode, in order make the GitHub
> > > migration [1] possible.
> >
> > done, svn is in READ-ONLY mode. Please do not try to commit.
>
> migration done for core repo. Please REVIEW result at
>
> https://github.com/OSGeo/grass
>
> Thanks. Martin
>

thanks a lot!

> PS: Addons and Promo repo migration will be finished tomorrow afternoon (CET).
>


-- 
ciao
Luca

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

Re: [GRASS-dev] Early "warning": upcoming switch of SVN to readonly mode for planned GitHub migration

[Martin Landa]

Hi,

pá 17. 5. 2019 v 9:25 odesílatel Martin Landa  napsal:
> > later tonight or tomorrow (Friday, May 17th, 2010) we'll switch the
> > GRASS GIS svn server to readonly-mode, in order make the GitHub
> > migration [1] possible.
>
> done, svn is in READ-ONLY mode. Please do not try to commit.

migration done for core repo. Please REVIEW result at

https://github.com/OSGeo/grass

Thanks. Martin

PS: Addons and Promo repo migration will be finished tomorrow afternoon (CET).

-- 
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] svn/trac -> git/github migration plan

[Vaclav Petras]

Hi Panos and all,

On Fri, May 17, 2019 at 5:09 AM Panagiotis Mavrogiorgos 
wrote:

>
> I would argue that even core developers should not be using the main repo
> as their
> personal one and that, at least most of the time, they should instead be
> using the same
> procedure as every other contributor.
>

Speaking to people here at the Minneapolis sprint this seems to be the
preferred way, although not always applied fully.

In any case, we should be using this at the beginning to be on the safe
side. Then we can evaluate.


>
> If every core dev starts pushing their personal branches on
> the main repo, very soon  there will be noise that can effectively become
> too much for
> UIs to properly display.
>

This can be mitigated by deleting the branch after merge. There should be a
button for that.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3838: r74307 breaks GUI: UnicodeDecodeError

[GRASS GIS]

#3838: r74307 breaks GUI: UnicodeDecodeError
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by pmav99):

 I just tried the following using Python 2 both at trunk and at r74305.
 There were no tracebacks in either case.

 {{{
 $ LC_ALL=fr_FR.UTF-8 ./run_grass.sh ~/gdata2/nc_spm_full_v2alpha/PERMANENT
 --text
   __  ___   _____
  / / __ \/   | / ___/ ___/   / /  _/ ___/
 / / __/ /_/ / /| | \__ \\_  \   / / __ / / \__ \
/ /_/ / _, _/ ___ |___/ /__/ /  / /_/ // / ___/ /
\/_/ |_/_/  |_///   \/___///

 Bienvenue dans le SIG GRASS 7.7.svn (exported)
 Page d'accueil du SIG GRASS :https://grass.osgeo.org
 Cette version fonctionne avec :  Z Shell (/usr/bin/zsh)
 L'aide est disponible par la commande :  g.manual -i
 Voir les termes de la licence avec : g.version -c
 Voir les termes de la licence avec : g.version -x
 Démarrer l'interface graphique avec :   g.gui wxpython
 Lors prêt pour la fermeture entrer :exit

 $ d.mon -l
 No monitors running

 $ d.mon start=wx0
 12:22:59: Warning: Mismatch between the program and library build versions
 detected.
 The library used 3.0 (wchar_t,compiler with C++ ABI 1013,wx
 containers,compatible with 2.8),
 and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1011,wx
 containers,compatible with 2.8).
 /usr/lib64/python2.7/site-packages/wx-3.0-gtk3/wx/_core.py:16629:
 UserWarning: wxPython/wxWidgets release number mismatch
   warnings.warn("wxPython/wxWidgets release number mismatch")

 $ d.rast basin
  100%
 }}}

 Since the original traceback has been resolved, I would suggest opening a
 new 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] svn/trac -> git/github migration plan

[Panagiotis Mavrogiorgos]

Dear all,

I would argue that even core developers should not be using the main repo
as their
personal one and that, at least most of the time, they should instead be
using the same
procedure as every other contributor.

Branches in git branches are really "cheap" (especially compared to e.g.
SVN).  They do
make it very easy to experiment and the more proficient you become with git
you do tend
to use them more and more.  If every core dev starts pushing their personal
branches on
the main repo, very soon  there will be noise that can effectively become
too much for
UIs to properly display. For example, please visit
[QGIS](https://github.com/qgis/QGIS) and click on the branch selector.
They only have
release branches (like GRASS) and the UI is already at its limit. Imagine
having e.g.
100+ more branches there...

with kind regards,
Panos
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Early "warning": upcoming switch of SVN to readonly mode for planned GitHub migration

[Martin Landa]

Hi,

čt 16. 5. 2019 v 18:28 odesílatel Markus Neteler  napsal:
> later tonight or tomorrow (Friday, May 17th, 2010) we'll switch the
> GRASS GIS svn server to readonly-mode, in order make the GitHub
> migration [1] possible.

done, svn is in READ-ONLY mode. Please do not try to commit.

Thanks! Martin

-- 
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

[GRASS-dev] [GRASS GIS] #3848: Unexpected error with v.what.rast and v.rast.stats

[GRASS GIS]

#3848: Unexpected error with v.what.rast and v.rast.stats
-+-
 Reporter:  micha|  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:  7.6.2
Component:  Default  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  All  |
-+-
 In general vector modules do not check or honor region settings. (The
 exception is v.to.rast, and this is specifically mentioned in the manual).
 However both v.rast.stats and v.what.rast require that the computational
 region covers the vector being queried.

 When running either of these modules with region settings that do **not**
 cover the vector, the error messages are unhelpful, even misleading:

 {{{
 micha@TP480:~$ v.what.rast weir7 rast=dem_4m col=dem type=centroid
 Reading features from vector map...
 No features of type (centroid) found in vector map 

 micha@TP480:~$ v.rast.stats weir7 rast=dem_4m column_pref=dem
 ERROR: No categories found in raster map
 }}}

 I suggest to add text to the man page of both, similar to the explanation
 in v.to.rast:

   v.to.rast will only affect data in areas lying inside the boundaries
 of the current geographic region.  A grid cell belongs to the area where
 the grid cell center falls into.

Before running v.to.rast, the user should therefore ensure that the
 current geographic region is correctly set and that the region resolution
 is at the desired level.

 In addition, it would be helpful to modify the code of both modules to
 check region settings and output a relevant error message if the vector is
 outside the current region.

-- 
Ticket URL: 
GRASS GIS 

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