Your message dated Sat, 10 Dec 2016 16:26:37 +0100
with message-id <[email protected]>
and subject line Re: Bug#676190: grass-gui: gcpmanager fails to list source
mapsets if non-ascii characters in grass data dir path
has caused the Debian Bug report #676190,
regarding grass-gui: gcpmanager fails to list source mapsets if non-ascii
characters in grass data dir path
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
676190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676190
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grass-gui
Version: 6.4.2-1
Severity: normal
Hi,
Using the wxpython GUI Georectify tool is impossible if the path to the grass
data directory (e.g. GRASSDATA) contains non ascii characters (e.g.
'/home/user/Työpöytä/GRASSDATA'). Selecting the source location works, but
the 'Select source mapset:' dropdown menu remains greyed out. The command
console shows the following error message, after selecting the source location:
***
Traceback (most recent call last):
File
"/usr/lib/grass64/etc/wxpython/gui_modules/gcpmanager.py",
line 377, in OnLocation
tmplist = os.listdir(os.path.join(self.grassdatabase,
self.xylocation))
File "/usr/lib/python2.7/posixpath.py", line 71, in join
path += '/' + b
UnicodeDecodeError
:
'ascii' codec can't decode byte 0xc3 in position 15: ordinal
not in range(128)
***
Changing the grass data directory path to only contain ascii characters (e.g.
'/home/user/GRASSDATA') makes the Georectify tool usable. This seems to an
issue with how the python code handles path names and unicode characters.
Cheers,
Torsti
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (700, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grass-gui depends on:
ii gnome-terminal [x-terminal-emulator] 3.4.1.1-1
ii grass-core 6.4.2-1
ii lesstif2 1:0.95.2-1
ii libc6 2.13-33
ii libfreetype6 2.4.9-1
ii libgdal1 1.9.0-2
ii libgl1-mesa-glx [libgl1] 8.0.2-2
ii libglu1-mesa [libglu1] 8.0.2-2
ii libice6 2:1.0.8-2
ii libpng12-0 1.2.49-1
ii libsm6 2:1.2.1-2
ii libtiff5 4.0.1-7
ii libx11-6 2:1.4.99.901-2
ii libxext6 2:1.3.1-2
ii libxmu6 2:1.1.1-1
ii libxt6 1:1.1.3-1
ii python 2.7.2-10
ii python-opengl 3.0.1-1
ii python-wxgtk2.8 2.8.12.1-11
ii tcl8.5 8.5.11-2
ii tk8.5 8.5.11-2
ii xterm [x-terminal-emulator] 278-1
ii zlib1g 1:1.2.7.dfsg-11
Versions of packages grass-gui recommends:
ii ghostscript 9.05~dfsg-6
ii python-imaging 1.1.7-4
grass-gui suggests no packages.
--- End Message ---
--- Begin Message ---
fixed 676190 7.2.0~rc1-1~exp1
thanks
Hi Torsti,
On Sun, 17 Jan 2016 17:26:53 +0100 Sebastiaan Couwenberg wrote:
> As reported in the upstream issue, it should be fixed in trunk, but
> those changes haven't found their way into the 7.0 branch as it's still
> present in 7.0.3 RC2.
The changes from trunk have found their way into GRASS 7.2, the issue is
fixed in the release candidate in experimental.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
