Your message dated Tue, 01 Oct 2013 21:14:32 +0200
with message-id <>
and subject line Re: Bug#615630: errors upon starting
has caused the Debian Bug report #615630,
regarding errors upon starting
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: thuban
Version: 1.2.2-2+b1
Severity: wishlist

$ thuban
importing gdalwarp
importing osgeo.gdal
No module named export_shapefile
No module named importMP
No module named gMapTiles
Problems with UMN MapServer MapScript (not installed?)
Problems with OWSLib (not installed?)
No thubanstart module available

(python:2096): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion 
`GDK_IS_DRAWABLE (drawable)' failed

(python:2096): Gdk-CRITICAL **: IA__gdk_drawable_get_depth: assertion 
`GDK_IS_DRAWABLE (drawable)' failed

Thuban Release Version 1.2.2

   Currently using:
           Python 2.6.6
           PySQLite 2.4.1
           SQLite 3.7.5
           GDAL - not available
           psycopg - not available

           Internal encoding: UTF8

   No GDAL support because module 'osgeo.gdal' cannot be imported. Python 
exception: 'No module named osgeo.gdal'

Odd, even though I have all the Depends installed.

man page could mention /usr/share/doc/thuban/ has the manual.

Any file argument on the command line causes "SAXParseException:
/home/jidanni/tmp/shape/a.shp:1:0: not well-formed (invalid token)"

Can't deal with non UTF-8 .dbf files.

--- End Message ---
--- Begin Message ---
Control: fixed -1 1.2.2-3+b1

The current version in Debian fixes the Python exception.



GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)

--- End Message ---
Pkg-grass-devel mailing list

Reply via email to