Send grass-windows mailing list submissions to
grass-windows@lists.osgeo.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.osgeo.org/mailman/listinfo/grass-windows
or, via email, send a message with subject or body 'help' to
grass-windows-requ...@lists.osgeo.org
You can reach the person managing the list at
grass-windows-ow...@lists.osgeo.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-windows digest..."
Today's Topics:
1. Re: v.in.ascii fails with long text file in WinGRASS-6.4.0-1
(Luigi Ponti)
2. Re: Re: v.in.ascii fails with long text file in
WinGRASS-6.4.0-1 (Glynn Clements)
----------------------------------------------------------------------
Message: 1
Date: Mon, 20 Sep 2010 19:22:41 +0200
From: Luigi Ponti <lpo...@inbox.com>
Subject: [GRASS-windows] Re: v.in.ascii fails with long text file in
WinGRASS-6.4.0-1
To: Luigi Ponti <lpo...@inbox.com>
Cc: grass-u...@lists.osgeo.org, grass-windows@lists.osgeo.org
Message-ID: <4c979861.7040...@inbox.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 14/09/2010 17:34, Luigi Ponti wrote:
> Dear list,
>
> [...]
>
> Ticket created.
>
> Any ideas? A change introduced in 6.4.0-1 has rendered WinGRASS
> unusable to me [...]
Thanks for the work on ticket #1159 http://trac.osgeo.org/grass/ticket/1159
I am wondering if there is a way by which I can restore v.in.ascii
functionality in 6.4.0 until a fix is found for the problem. I am
probably asking an unsound question: is there a way to compile the code
in the state it was before the issue arose? During the first half of
this year, Windows installers based on 6.4.svn snapshots have run
smoothly for critical job tasks, and I have started to rely on them.
Kind regards and thank you,
Luigi
------------------------------
Message: 2
Date: Tue, 21 Sep 2010 09:00:25 +0100
From: Glynn Clements <gl...@gclements.plus.com>
Subject: Re: [GRASS-windows] Re: v.in.ascii fails with long text file
in WinGRASS-6.4.0-1
To: Luigi Ponti <lpo...@inbox.com>
Cc: grass-u...@lists.osgeo.org, grass-windows@lists.osgeo.org
Message-ID: <19608.26137.495562.184...@cerise.gclements.plus.com>
Content-Type: text/plain; charset=us-ascii
Luigi Ponti wrote:
> > Any ideas? A change introduced in 6.4.0-1 has rendered WinGRASS
> > unusable to me [...]
>
> Thanks for the work on ticket #1159 http://trac.osgeo.org/grass/ticket/1159
>
> I am wondering if there is a way by which I can restore v.in.ascii
> functionality in 6.4.0 until a fix is found for the problem. I am
> probably asking an unsound question: is there a way to compile the code
> in the state it was before the issue arose?
You can prevent the error with:
--- vector/v.in.ascii/in.c~ 2010-09-04 16:31:59.000000000 +0100
+++ vector/v.in.ascii/in.c 2010-09-21 08:57:12.000000000 +0100
@@ -519,8 +519,7 @@
if (driver) {
G_message(_("Populating table..."));
db_commit_transaction(driver);
- if(db_close_database_shutdown_driver(driver) == DB_FAILED)
- G_fatal_error(_("Could not close attribute table. The DBMI
driver did not accept all attributes"));
+ db_close_database_shutdown_driver(driver);
}
fclose(tmpascii);
}
db_close_database_shutdown_driver() is incorrectly reporting errors on
Windows. v.in.ascii is the only module which checks the return status,
so it's the only module which is affected.
--
Glynn Clements <gl...@gclements.plus.com>
------------------------------
_______________________________________________
grass-windows mailing list
grass-windows@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-windows
End of grass-windows Digest, Vol 49, Issue 7
********************************************
