[GRASS-dev] GRASS GIS 6.4.3RC2 released

GRASS GIS GRASS GIS developer
1

A second release candidate of GRASS GIS 6.4.3 is now available.

Source code:
http://grass.osgeo.org/grass64/source/
http://grass.osgeo.org/grass64/source/grass-6.4.3RC2.tar.gz

Selected Binaries (more will be published)
http://grass.osgeo.org/grass64/binary/mswindows/native/WinGRASS-6.4.3RC2-1-Setup.exe
http://trac.osgeo.org/osgeo4w/wiki/pkg-grass
http://www.public.asu.edu/~cmbarton/files/grass_mac/OSX10.6-snowleopard/GRASS-6.4.3RC2.pkg.zip
http://download.opensuse.org/repositories/home:/tzotsos:/Application:/Geo/

To get the RC2 source code from SVN:
svn checkout https://svn.osgeo.org/grass/grass/tags/release_20121218_grass_6_4_3RC2/

An announcement has been drafted at
http://trac.osgeo.org/grass/wiki/Release/6.4.3RC2-News

Key improvements of the GRASS 6.4.3 release include enhanced
portability for MS-Windows (native support), fixes for the wxPython
based portable graphical interface, improvements for the Python API,
more translations, and some new functionality (image processing tools).

Release candidate management at
http://trac.osgeo.org/grass/wiki/Grass6Planning

Please join us in testing this release candidate for the final release.

Thanks to all contributors!

2

A second release candidate of GRASS GIS 6.4.3 is now available.

since it's more than a month ago now, what about another another RC or
release?

maybe anything for the community sprint next week?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/GRASS-GIS-6-4-3RC2-released-tp5024186p5031708.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

3

On Feb 2, 2013, at 6:36 PM, Helmut Kudrnovsky wrote:

A second release candidate of GRASS GIS 6.4.3 is now available.

since it's more than a month ago now, what about another another RC or
release?

maybe anything for the community sprint next week?

Excellent suggestion. There is a number of unresolved issues, but hopefully not too difficult to fix:

- r3.in.ascii broken handling of input parameters (it runs only with defaults, if you need to change something,
e.g. specify * for nulls it gives error - more details here
http://trac.osgeo.org/grass/ticket/1801

- the isosurfaces now work on macosx10.8 with changes made by Michael - this needs to be further tested and
done for GRASS6.4.3 as well - Michael, can you put your solution into bug report #1736 and then
if it works perhaps this can be closed (btw I found #803 with isosurfaces crashing on linux with segfault -
I am wondering whether this was related).

-wxnviz - in wxnviz for draped vector lines after I change the line width e.g. to 0,
the displayed line goes back to wider line each time something else is drawn
(e.g. fringe or view is changed) but the number is still set to 0. (I haven't submitted a bug report on this yet)

There are numerous other tickets which I am not sure how important it is to have them fixed -
e.g.
#1837 d.rast.edit
#1820 multiple map displays
#1797 r.li.padcv
#1787 profile tool on mac - may be fixed already, I can test
#1784 r3.info and g.region rast3d in wingrass - still an issue? needs to be tested and fixed if still broken
and many others
also, several gui modeler issues (this can be considered as prototype module? )
and d.legend run in command console does not carry over the parameters, d.legend panel sometimes
opens behind the display window leading to user confusion

Not really a bug, but there are various error messages on Windows and Mac that don't seem to cause any problems
except for user confusion - I am not sure how important it is to take care of them - if it is something that
should be fixed I can collect the info and post here (or submit bug report?)

It would be great to use the code sprint to make some progress on the release of GRASS6.4.3,

Helena

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/GRASS-GIS-6-4-3RC2-released-tp5024186p5031708.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

4

Hi,

2013/2/3 Helmut Kudrnovsky <hellik@web.de>:

A second release candidate of GRASS GIS 6.4.3 is now available.

since it's more than a month ago now, what about another another RC or
release?

agreed. After RC3 should come ideally final release.

maybe anything for the community sprint next week?

AFAIK, the community sprint started yesterday. It would be nice to fix
blockers for RC3 and release it, probably reasonable task for the
sprint :slight_smile:

Martin

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

5

On Sun, Feb 3, 2013 at 1:30 AM, Helena Mitasova <hmitaso@ncsu.edu> wrote:

-wxnviz - in wxnviz for draped vector lines after I change the line width e.g. to 0,
the displayed line goes back to wider line each time something else is drawn
(e.g. fringe or view is changed) but the number is still set to 0. (I haven't submitted a bug report on this yet)

I just set the minimum line width to 1 instead of 0 because 0 seems to
be a invalid and a nonsense anyway. Please try if it helps.

Ann

6

Hi,

2013/2/3 Martin Landa <landa.martin@gmail.com>:

maybe anything for the community sprint next week?

AFAIK, the community sprint started yesterday. It would be nice to fix
blockers for RC3 and release it, probably reasonable task for the
sprint :slight_smile:

just to remember critical issues for 6.4.3 (no blocker at this moment)
[1]. It's not clear if someone is working on them (owner not filled).
Not sure about other issues which have been reported in ML (and not as
tickets). It's hard to collect them from ML.

Martin

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

7

Hi,

2013/2/3 Martin Landa <landa.martin@gmail.com>:

since it's more than a month ago now, what about another another RC or
release?

agreed. After RC3 should come ideally final release.

sorry for bringing this issue back. We have 2 RCs released, RC2 is
almost 2(!) month old. I don't see any blocker in trac [1], even
nothing noted on the dev's wiki [2]. Is there any blocker, if so
please collect them in trac or at least note them on trac page [2].
Currently I am afraid that we have no clear idea what is the status of
critical issues which have been reported within various mails in
various threads by various persons.

Martin

[1] http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0
[2] http://trac.osgeo.org/grass/wiki/Grass6Planning#GRASS6.4.3

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

8

Martin,

I think that #1736 is still unresolved and I am afraid that the latest changes might have made it worse, I still have a working version in GRASS6.5 which I have not updated for a while but the most recent version in 6.4.3 seems to be crashing unpredictably,
similar to what it used to do couple years ago in old nviz (see #803). I will try to update and test again to see where it stands
but it may be now crashing on linux as well.

here is the 2d and 3d raster that I have used for testing, it now crashes for isosurface 15 and 16 but works for isosurface 17
(my GRASS6.5 works with it without any trouble for any isosurface)
http://skagit.meas.ncsu.edu/~helena/grasswork/JR_2008_ALL.asci
http://skagit.meas.ncsu.edu/~helena/grasswork/JR_7408MR_2m_t70_nd0.asci
I am doing my testing on Mac OSX10.6 and Mac OSX10.8
(I totally agree with Markus M and Tomas Paudits that ogsf needs to be rewritten but so far I did not have much luck
finding anybody with the right expertise to do it).

I think that #1801was fixed thanks to Markus M, but I did not have time to test. here is a 3d raster with nulls that was causing problems if somebody wants to test
http://skagit.meas.ncsu.edu/~helena/grasswork/JR_7408MR_2m_t70.asci

I can try #1784 on our Windows machines to see whether we have the same problem.
I am not sure about the rest of the critical bugs. The rest of the issues that I posted in emails was not critical,
mostly confusing features and most of them are fixed thanks to Anna,

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmitaso@ncsu.edu

"All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.”

On Feb 13, 2013, at 3:32 PM, Martin Landa wrote:

Hi,

2013/2/3 Martin Landa <landa.martin@gmail.com>:

since it's more than a month ago now, what about another another RC or
release?

agreed. After RC3 should come ideally final release.

sorry for bringing this issue back. We have 2 RCs released, RC2 is
almost 2(!) month old. I don't see any blocker in trac [1], even
nothing noted on the dev's wiki [2]. Is there any blocker, if so
please collect them in trac or at least note them on trac page [2].
Currently I am afraid that we have no clear idea what is the status of
critical issues which have been reported within various mails in
various threads by various persons.

Martin

[1] http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0
[2] http://trac.osgeo.org/grass/wiki/Grass6Planning#GRASS6.4.3

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

9

Hi,

sorry, my time to work on things is still not existant & I've
been trying to get the osgeo live dvd out the door before
starting on remaining issues for 6.4.3 rc3.

without a good look through the bug trac'er yet, the main things
I still want to check:

- make sure g.extension works everywhere; I'm looking into it.

- make sure the WinGrass installer asks y/n before installing the
ms virt runtime system libraries- we have a legal obligation
to handle this cleanly. (note the gdal.org/tmp/ dir package is
dated 2009; someone reported a new dll missing the other day;
I've no idea what files osgeo4w ships from its repo)

- verify that the wxPsmap symbol decoration tool can be refined
later without breaking backwards compatibility

thanks,
Hamish

10

Hi Hamish,

On Wed, Feb 13, 2013 at 11:55 PM, Hamish <hamish_b@yahoo.com> wrote:

Hi,

- verify that the wxPsmap symbol decoration tool can be refined
later without breaking backwards compatibility

sorry, I haven't have time to think about it so far.
So you want to use the grass symbols instead of eps north arrow
images. What is exactly the reason? You probably explained it but I
forgot it. Personally, I am not very fond of this format. Anyway if
you convert the arrow images, there is probably no way not to break
the compatibility. One thing we can then do is to create a script
which could find and convert the eps instruction to a point
instruction in the ps.map instructions file. However, is the
compatibility a real problem?

If you want to convert the arrows, I would suggest to create a new
directory 'north_arrows' (besides basic, extra, ...). This would
simplify the life of users (why on earth are north arrows located in
'extra'?) and me as a developer of the composer (in the north arrow
dialog I would show only the north_arrow directory, otherwise I would
have to filter all the symbols by the name or something like this). I
think we can afford this change in grass 7, maybe we can revise also
the other names like basic and extra?

Regards,
Anna

thanks,
Hamish
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

11

Hi,

2013/2/13 Martin Landa <landa.martin@gmail.com>:

Hi,

2013/2/3 Martin Landa <landa.martin@gmail.com>:

since it's more than a month ago now, what about another another RC or
release?

agreed. After RC3 should come ideally final release.

sorry for bringing this issue back. We have 2 RCs released, RC2 is
almost 2(!) month old. I don't see any blocker in trac [1], even
nothing noted on the dev's wiki [2]. Is there any blocker, if so
please collect them in trac or at least note them on trac page [2].

good, now the situation is much more clear (4 blockers reported by
Hamish within last few days). I hope that it's not forbidden that also
the reporter can fix the bug :wink: Would be the ideal situation. At
least we are much more far from RC3/final that we were in the last
week. Unfortunately my time is very limited now (can do something, but
not so much), so I hope that someone will work on these blockers in
some way ...

Martin

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa