Your message dated Wed, 23 Aug 2006 19:19:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line housekeeping
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: grass
Version: 5.7.0+6.0.0beta2-1
Severity: normal
Tags: upstream

There is not much one can do with db.execute these days. The failed
line are commented:

echo ALTER TABLE $c5 ADD COLUMN contour integer|db.execute
#echo UPDATE $c5 SET contour = 3 + 2 WHERE contour \> 0|db.execute
#echo UPDATE $c5 SET contour = 3 + 2 |db.execute
#echo UPDATE $c5 SET contour = cat + 2 |db.execute
echo UPDATE $c5 SET contour = 2|db.execute

--- End Message ---
--- Begin Message ---
tags 305250 + fixed-upstream
tags 305249 + moreinfo

<markusN> frankie: #287589, #305250 are resolved; #305249 not clear to me; 
#305250 is not a bug (he either needs to define the table or deactivate the 
attrib support (lower left button); 
          #305245 not sure because increments seems to imply higher number, but 
it is the next free number which could be lower as the current; 
          #305247 is a problem of his windows manager, not of GRASS (we don't 
          for #305577 he should select PG, MySQL, ODBC, SQLite as backend, not 
DBF (maybe it even works with DBF now);

Francesco P. Lovergine

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

Reply via email to