Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi all, I'll tag the release later today. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On 26/07/13 09:47, Markus Neteler wrote: On Wed, Jul 24, 2013 at 12:13 AM, Luca Delucchi wrote: On 23 July 2013 12:30, Hamish wrote: screenshots for that? Yes, please provide some catchy screenshots! Some already existing candidates I see as fitting: http://grasswiki.osgeo.org/wiki/File:Georectifier_berlin.png http://grasswiki.osgeo.org/wiki/File:CartographicComposer.png + http://grasswiki.osgeo.org/wiki/File:CCPreview.png http://grasswiki.osgeo.org/wiki/File:WxGUI-modeler-if-else-0.png http://grasswiki.osgeo.org/wiki/File:Wxgui-location-wizard.png Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, Jul 24, 2013 at 12:13 AM, Luca Delucchi wrote: > On 23 July 2013 12:30, Hamish wrote: >> Markus Neteler wrote: Today could be a great rlease-6.4.3-day :) >> >> since on the 24th we are +2 weeks since RC4 without any major bugs being >> reported I think we are ok to release any time now. I don't know about >> anyone else but I can't say I've really tested rc4 very much beyond >> making sure the debian package building still works. too busy :-/ >> >> >> Luca: >>> we are so close to 30 July that we could wait a week and release >>> in the same day of his born :-) ok. however, we need to internally release before to get the binaries ready (a strategy adopted since some releases). >> It would be a nice little something for the release announcement too. :) ... > please Hamish start it you could use some pad He did in SVN. >> Also MarkusN's "visual changelog" idea is nice, the trac news items for >> the earlier RCs should give some ideas. anyone like to start on I have merged all RC news into the final (draft) announcement. Please check in trac. >> screenshots for that? Yes, please provide some catchy screenshots! >> maybe host/compose in the more thumbnail- >> friendly/prettier grass mediawiki? Not surwe what that means? Please explain... > markus we could also create a video like this > http://www.youtube.com/watch?feature=player_embedded&v=suyDqmGXoWk Done. I have recalculated the entire thing with camera tracking and more It is a 11GB MP$ file, 10min duration. It looks pretty nice. I have uploaded it to youtube, yet hidden, though. Audio (free music) would be great but I have no competence/time to add that. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On 23 July 2013 12:30, Hamish wrote: > Markus Neteler wrote: >>> Today could be a great rlease-6.4.3-day :) > > since on the 24th we are +2 weeks since RC4 without any major bugs being > reported I think we are ok to release any time now. I don't know about > anyone else but I can't say I've really tested rc4 very much beyond > making sure the debian package building still works. too busy :-/ > > > Luca: >> we are so close to 30 July that we could wait a week and release >> in the same day of his born :-) > > It would be a nice little something for the release announcement too. :) > Speaking of which, do we want to write the formal release announcement + > 2 paragraph abstract as we have for earlier releases in grass-web svn, or > do something different now? I think we need something higher-level than > the trac wiki's detailed changelog highlights, and that it should be > done before release. I might try a first draft tomorrow if no one > else has started on it. > please Hamish start it you could use some pad > Also MarkusN's "visual changelog" idea is nice, the trac news items for > the earlier RCs should give some ideas. anyone like to start on > > screenshots for that? maybe host/compose in the more thumbnail- > friendly/prettier grass mediawiki? > markus we could also create a video like this http://www.youtube.com/watch?feature=player_embedded&v=suyDqmGXoWk > > best, > Hamish -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
>> >> Today could be a great rlease-6.4.3-day :) >> > >we are so close to 30 July that we could wait a week and release in >the same day of his born :-) +1 - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GRASS-6-4-3-release-planning-tp4995930p5068316.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
Re: [GRASS-dev] GRASS 6.4.3 release planning
Markus Neteler wrote: >> Today could be a great rlease-6.4.3-day :) since on the 24th we are +2 weeks since RC4 without any major bugs being reported I think we are ok to release any time now. I don't know about anyone else but I can't say I've really tested rc4 very much beyond making sure the debian package building still works. too busy :-/ Luca: > we are so close to 30 July that we could wait a week and release > in the same day of his born :-) It would be a nice little something for the release announcement too. :) Speaking of which, do we want to write the formal release announcement + 2 paragraph abstract as we have for earlier releases in grass-web svn, or do something different now? I think we need something higher-level than the trac wiki's detailed changelog highlights, and that it should be done before release. I might try a first draft tomorrow if no one else has started on it. Also MarkusN's "visual changelog" idea is nice, the trac news items for the earlier RCs should give some ideas. anyone like to start on screenshots for that? maybe host/compose in the more thumbnail- friendly/prettier grass mediawiki? fyi the only bug I'm actively thinking on in 6.x is m.proj (and so r.in.wms) on WinGrass when the location uses a grid transform file. It fails due to a cs2cs quoting problem + spaces in $GISBASE/etc/ path to the NTv2 grid file. I've got it close to working in 6.5svn (but not quite) and can prototype it working on the command line in wingrass 6.4, but still it gives bad results from the script. Things are quite busy for me right now so unless someone else wants to help I think that can wait for the next train. It's listed in the rc4 errata and I think the next step is working on some known-good transforms of modern and pre-satellite era datum transforms into a new m.proj test_suite/ script. best, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On 23 July 2013 10:29, Markus Neteler wrote: > > Today could be a great rlease-6.4.3-day :) > we are so close to 30 July that we could wait a week and release in the same day of his born :-) > Markus > -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Thu, Jul 18, 2013 at 6:42 PM, Markus Neteler wrote: > Hi all, > > after the publication of 6.4.3RC4 > http://grass.osgeo.org/news/25/15/GRASS-GIS-6-4-3RC4-released/ > let's think about the final release in these days: > > See also: > * all GRASS 6 bugs ordered by topic: https://trac.osgeo.org/grass/report/16 > > I would note that there is no blocker bug report at time. 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 > Greetings from Prague > (http://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Prague_2013) Today could be a great rlease-6.4.3-day :) Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi all, after the publication of 6.4.3RC4 http://grass.osgeo.org/news/25/15/GRASS-GIS-6-4-3RC4-released/ let's think about the final release in these days: See also: * all GRASS 6 bugs ordered by topic: https://trac.osgeo.org/grass/report/16 I would note that there is no blocker bug report at time. Greetings from Prague (http://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Prague_2013) Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
(ok, tagging has been done. Currently various binaries are built so that I can send out the announcement in 10-12 hours from now including binary download links) cheers Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
MarkusN: > Maybe "fail message" is better for 6.4.3 and then we (once in a > decade) will have 6.4.4 shortly, i.e. less than 6 months? Once wxPython 2.10 is released and starts making it into distros, that will be a good motivation for us to release a 6.4.4 version of GRASS without waiting too long. :-) regards, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, Jul 10, 2013 at 12:03 AM, Anna Petrášová wrote: > On Tue, Jul 9, 2013 at 3:12 PM, Martin Landa wrote: >> 2013/7/9 Maris Nartiss : >> > Current situation that wxgui fails with cryptic error is also not a >> > solution. If you consider compatibility with 2.9 to not easy solvable, >> > is it possible to enforce wxpython <2.9 then? Or make it fail with >> > "2.8 required" error message? >> >> +1 for fail message. >> >> Martin > > done in r57050 Any objections for RC4? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Tue, Jul 9, 2013 at 3:12 PM, Martin Landa wrote: > Hi, > > 2013/7/9 Maris Nartiss : > > Current situation that wxgui fails with cryptic error is also not a > > solution. If you consider compatibility with 2.9 to not easy solvable, > > is it possible to enforce wxpython <2.9 then? Or make it fail with > > "2.8 required" error message? > > +1 for fail message. > > Martin > done in r57050 Anna ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Martin: > I would not say that GRASS 6 supports wxPython 2.9. Please note > that 2.9 is dev version! added to "known issues", https://trac.osgeo.org/grass/wiki/Release/6.4.3RC4-News#Knownissues go go go, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Tue, Jul 9, 2013 at 3:12 PM, Martin Landa wrote: > Hi, > > 2013/7/9 Maris Nartiss : >> Current situation that wxgui fails with cryptic error is also not a >> solution. If you consider compatibility with 2.9 to not easy solvable, >> is it possible to enforce wxpython <2.9 then? Or make it fail with >> "2.8 required" error message? > > +1 for fail message. Maybe "fail message" is better for 6.4.3 and then we (once in a decade) will have 6.4.4 shortly, i.e. less than 6 months? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2013/7/9 Maris Nartiss : > Current situation that wxgui fails with cryptic error is also not a > solution. If you consider compatibility with 2.9 to not easy solvable, > is it possible to enforce wxpython <2.9 then? Or make it fail with > "2.8 required" error message? +1 for fail message. Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2013/7/9 Maris Nartiss : > Sorry, Markus, to interrupt you. > Don't release without backporting r51052 as 6.4.3 g.gui fails to start > with wxpython 2.9.1 > http://trac.osgeo.org/grass/changeset/51052 I would not say that GRASS 6 supports wxPython 2.9. Please note that 2.9 is dev version! Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Current situation that wxgui fails with cryptic error is also not a solution. If you consider compatibility with 2.9 to not easy solvable, is it possible to enforce wxpython <2.9 then? Or make it fail with "2.8 required" error message? With r54916 and r51052 at least wxgui came up and I was able to display a map. No serious testing tough as I just wanted to see if #1893 is fixed. Maris. 2013/7/9 Anna Petrášová : > > > > On Tue, Jul 9, 2013 at 2:29 PM, Maris Nartiss wrote: >> >> Sorry, Markus, to interrupt you. >> Don't release without backporting r51052 as 6.4.3 g.gui fails to start >> with wxpython 2.9.1 >> http://trac.osgeo.org/grass/changeset/51052 >> > > This is not the only change which has to be done to make it work with > wxpython 2.9. There are quite a lot of them and not all problems are fixed > in grass 7 yet. I thought we agreed on leaving this for next version. Or? > If you consider this important, I can backport the fixes but I cannot be > sure I won't break something. > > Anna > >> Maris. >> >> 2013/7/9 Markus Neteler : >> > (back to this thread) >> > >> > On Tue, Jul 9, 2013 at 5:28 AM, Helena Mitasova >> > wrote: >> >> >> >> I am happy to report that the expressions with || now work on windows >> >> from >> >> command console when quotes are used. >> >> Thank you Anna and Glynn for solving this long standing problem for >> >> wingrass users, >> >> >> >> Helena >> > >> > Great! At this point time to release RC4! >> > >> > Markus >> > ___ >> > grass-dev mailing list >> > grass-dev@lists.osgeo.org >> > http://lists.osgeo.org/mailman/listinfo/grass-dev > > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Tue, Jul 9, 2013 at 2:29 PM, Maris Nartiss wrote: > Sorry, Markus, to interrupt you. > Don't release without backporting r51052 as 6.4.3 g.gui fails to start > with wxpython 2.9.1 > http://trac.osgeo.org/grass/changeset/51052 > > This is not the only change which has to be done to make it work with wxpython 2.9. There are quite a lot of them and not all problems are fixed in grass 7 yet. I thought we agreed on leaving this for next version. Or? If you consider this important, I can backport the fixes but I cannot be sure I won't break something. Anna Maris. > > 2013/7/9 Markus Neteler : > > (back to this thread) > > > > On Tue, Jul 9, 2013 at 5:28 AM, Helena Mitasova > wrote: > >> > >> I am happy to report that the expressions with || now work on windows > from > >> command console when quotes are used. > >> Thank you Anna and Glynn for solving this long standing problem for > >> wingrass users, > >> > >> Helena > > > > Great! At this point time to release RC4! > > > > Markus > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Aaaaw! Seems that there are more wxpython 2.9 related fixes that haven't made from trunk to release branch :( r54916 is also necessary to display any raster/vector in wxgui. As there have been no complaints about truk, I assume it's safe change. Maris. 2013/7/9 Maris Nartiss : > Sorry, Markus, to interrupt you. > Don't release without backporting r51052 as 6.4.3 g.gui fails to start > with wxpython 2.9.1 > http://trac.osgeo.org/grass/changeset/51052 > > Maris. > > 2013/7/9 Markus Neteler : >> (back to this thread) >> >> On Tue, Jul 9, 2013 at 5:28 AM, Helena Mitasova wrote: >>> >>> I am happy to report that the expressions with || now work on windows from >>> command console when quotes are used. >>> Thank you Anna and Glynn for solving this long standing problem for >>> wingrass users, >>> >>> Helena >> >> Great! At this point time to release RC4! >> >> Markus >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Sorry, Markus, to interrupt you. Don't release without backporting r51052 as 6.4.3 g.gui fails to start with wxpython 2.9.1 http://trac.osgeo.org/grass/changeset/51052 Maris. 2013/7/9 Markus Neteler : > (back to this thread) > > On Tue, Jul 9, 2013 at 5:28 AM, Helena Mitasova wrote: >> >> I am happy to report that the expressions with || now work on windows from >> command console when quotes are used. >> Thank you Anna and Glynn for solving this long standing problem for >> wingrass users, >> >> Helena > > Great! At this point time to release RC4! > > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
(back to this thread) On Tue, Jul 9, 2013 at 5:28 AM, Helena Mitasova wrote: > > I am happy to report that the expressions with || now work on windows from > command console when quotes are used. > Thank you Anna and Glynn for solving this long standing problem for > wingrass users, > > Helena Great! At this point time to release RC4! Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning, mapcalc expressions in wingrass
I am happy to report that the expressions with || now work on windows from
command console when quotes are used.
Thank you Anna and Glynn for solving this long standing problem for wingrass
users,
Helena
On Jul 4, 2013, at 4:45 PM, Anna Petrášová wrote:
>
>
>
> On Tue, Jul 2, 2013 at 8:57 PM, Anna Petrášová wrote:
> Hi,
>
>
> On Fri, Jun 28, 2013 at 2:29 AM, Helena Mitasova wrote:
> regarding the r.mapcalc issue in command console on wingrass -
> (sorry I did not make it clear it was for wingrass - it always worked well on
> Mac and linux)
>
> It is not critical, windows users can still use the mapcalculator GUI where
> it runs OK,
> but the r.mapcalc in the command console still does not seem to work - tried
> by a student
> using June 26 snapshot this is what she says:
>
> Here are examples of the commands run and the errors received:
> r.mapcalc urban2_30m=if(landuse96_28m==1 ||
> landuse96_28m==2,landuse96_28m,null())
> syntax error, unexpected $end, expecting ')'
> Parse error
> 'landuse96_28m' is not recognized as an internal or external
>
> command,
> operable program or batch file.
>
> r.mapcalc MASK=if((elevation<100 && elevation>60) && (landuse96_28m==1 ||
> landuse96_28m==2),1,null())
> 1 was unexpected at this time.
>
> This is the same we were getting in GRASS6.4.3RC2 and apparently the proposed
> solutions did not work
> http://lists.osgeo.org/pipermail/grass-dev/2013-February/062047.html
> http://lists.osgeo.org/pipermail/grass-dev/2013-March/062607.html
>
>
> I had the opportunity to test Glynn's patch (the second link above) on
> Windows and it seems to solve the problems. From the discussion I can see
> that Markus already tested it but he was not successful, so I applied the
> patch to 6.5 first.
> All the commands causing problems are now working with both (", ') quotes and
> without, only the command with || requires quotes.
>
> Anna
>
> Seems to work, I applied it to all branches, please test (using e.g. the
> commands above).
>
> Anna
>
>
>
>
> if I get this confirmed I will file a bug report (I thought I already did,
> but it is not there).
> If it is not fixable it should be at least mentioned on the known issues web
> page
> http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Raster_modules
>
> Helena
>
>
>
>
> >
> > Helena:
> >> I am also wondering whether the r.mapcalc expressions with || (or)
> >> now run from the wxGUI command console.
> >
> > I just tried on linux 6.4.3svn wxGUI command console:
>
> > r.mapcalc "either = 0 || 1"
> > and it worked.
> >
> > In general I wouldn't be surprised if full command line quoting took
> > years and huge amounts of effort to (re)perfect. And even then, does
> > it try to follow Bash conventions, or python, or DOS, or some mix of
> > all those? How much do we try to (re)teach about command line
> > techniques in our own docs? Will unquoted input=C:\Users\files\data.txt
> > always be parsed to input=C:Usersfilesdata.txt (literal \U, \f, \d)
> > in the command console in that case?
> >
> >
> > best,
>
> > Hamish
> >
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/grass-dev
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Tue, Jul 2, 2013 at 8:57 PM, Anna Petrášová wrote:
> Hi,
>
>
> On Fri, Jun 28, 2013 at 2:29 AM, Helena Mitasova wrote:
>
>> regarding the r.mapcalc issue in command console on wingrass -
>> (sorry I did not make it clear it was for wingrass - it always worked
>> well on Mac and linux)
>>
>> It is not critical, windows users can still use the mapcalculator GUI
>> where it runs OK,
>> but the r.mapcalc in the command console still does not seem to work -
>> tried by a student
>> using June 26 snapshot this is what she says:
>>
>> Here are examples of the commands run and the errors received:
>> r.mapcalc urban2_30m=if(landuse96_28m==1 ||
>> landuse96_28m==2,landuse96_28m,null())
>> syntax error, unexpected $end, expecting ')'
>> Parse error
>> 'landuse96_28m' is not recognized as an internal or external
>>
>> command,
>> operable program or batch file.
>>
>> r.mapcalc MASK=if((elevation<100 && elevation>60) && (landuse96_28m==1 ||
>> landuse96_28m==2),1,null())
>> 1 was unexpected at this time.
>>
>> This is the same we were getting in GRASS6.4.3RC2 and apparently the
>> proposed solutions did not work
>> http://lists.osgeo.org/pipermail/grass-dev/2013-February/062047.html
>> http://lists.osgeo.org/pipermail/grass-dev/2013-March/062607.html
>
>
>
> I had the opportunity to test Glynn's patch (the second link above) on
> Windows and it seems to solve the problems. From the discussion I can see
> that Markus already tested it but he was not successful, so I applied the
> patch to 6.5 first.
> All the commands causing problems are now working with both (", ') quotes
> and without, only the command with || requires quotes.
>
> Anna
>
Seems to work, I applied it to all branches, please test (using e.g. the
commands above).
Anna
>
>>
>> if I get this confirmed I will file a bug report (I thought I already
>> did, but it is not there).
>> If it is not fixable it should be at least mentioned on the known issues
>> web page
>> http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Raster_modules
>>
>> Helena
>>
>>
>>
>>
>> >
>> > Helena:
>> >> I am also wondering whether the r.mapcalc expressions with || (or)
>> >> now run from the wxGUI command console.
>> >
>> > I just tried on linux 6.4.3svn wxGUI command console:
>>
>> > r.mapcalc "either = 0 || 1"
>> > and it worked.
>> >
>> > In general I wouldn't be surprised if full command line quoting took
>> > years and huge amounts of effort to (re)perfect. And even then, does
>> > it try to follow Bash conventions, or python, or DOS, or some mix of
>> > all those? How much do we try to (re)teach about command line
>> > techniques in our own docs? Will unquoted input=C:\Users\files\data.txt
>> > always be parsed to input=C:Usersfilesdata.txt (literal \U, \f, \d)
>> > in the command console in that case?
>> >
>> >
>> > best,
>>
>> > Hamish
>> >
>> > ___
>> > grass-dev mailing list
>> > grass-dev@lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi,
On Fri, Jun 28, 2013 at 2:29 AM, Helena Mitasova wrote:
> regarding the r.mapcalc issue in command console on wingrass -
> (sorry I did not make it clear it was for wingrass - it always worked well
> on Mac and linux)
>
> It is not critical, windows users can still use the mapcalculator GUI
> where it runs OK,
> but the r.mapcalc in the command console still does not seem to work -
> tried by a student
> using June 26 snapshot this is what she says:
>
> Here are examples of the commands run and the errors received:
> r.mapcalc urban2_30m=if(landuse96_28m==1 ||
> landuse96_28m==2,landuse96_28m,null())
> syntax error, unexpected $end, expecting ')'
> Parse error
> 'landuse96_28m' is not recognized as an internal or external
> command,
> operable program or batch file.
>
> r.mapcalc MASK=if((elevation<100 && elevation>60) && (landuse96_28m==1 ||
> landuse96_28m==2),1,null())
> 1 was unexpected at this time.
>
> This is the same we were getting in GRASS6.4.3RC2 and apparently the
> proposed solutions did not work
> http://lists.osgeo.org/pipermail/grass-dev/2013-February/062047.html
> http://lists.osgeo.org/pipermail/grass-dev/2013-March/062607.html
I had the opportunity to test Glynn's patch (the second link above) on
Windows and it seems to solve the problems. From the discussion I can see
that Markus already tested it but he was not successful, so I applied the
patch to 6.5 first.
All the commands causing problems are now working with both (", ') quotes
and without, only the command with || requires quotes.
Anna
>
> if I get this confirmed I will file a bug report (I thought I already did,
> but it is not there).
> If it is not fixable it should be at least mentioned on the known issues
> web page
> http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Raster_modules
>
> Helena
>
>
>
>
> >
> > Helena:
> >> I am also wondering whether the r.mapcalc expressions with || (or)
> >> now run from the wxGUI command console.
> >
> > I just tried on linux 6.4.3svn wxGUI command console:
> > r.mapcalc "either = 0 || 1"
> > and it worked.
> >
> > In general I wouldn't be surprised if full command line quoting took
> > years and huge amounts of effort to (re)perfect. And even then, does
> > it try to follow Bash conventions, or python, or DOS, or some mix of
> > all those? How much do we try to (re)teach about command line
> > techniques in our own docs? Will unquoted input=C:\Users\files\data.txt
> > always be parsed to input=C:Usersfilesdata.txt (literal \U, \f, \d)
> > in the command console in that case?
> >
> >
> > best,
> > Hamish
> >
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/grass-dev
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I just tested and all the extensions below install OK (didn't test v.points.cog) in GRASS 6.4 release branch compiled 10 June. Michael __ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www:http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton On Jun 11, 2013, at 12:50 PM, Hamish wrote: > Michael wrote: >> I did a test of g.extension in GRASS >> 6.4 svn and 6.5. It works fine on the Mac for the test case >> of r.fuzzy. >> >> GRASS 7 still does not work for me, at least with wxPython >> 2.8 (will be doing more testing on 2.9 later today), but >> that is not relevant for the 6.4.3 release. > > thanks Michael, I've been looking forward to hearing about > the state of that. > > for a thorough test, it would be good to check the combination(s) > of shell script, python script, and compiled C code, both from > the grass command line (g.extension.sh) and the wxGUI (g.exension.py). > > if it helps save you a few moments of searching, here are some > nice examples of those from each category > > shell: r.surf.volcano, v.points.cog, (plug:) d.anaglyph > python: r.diversity, r.in.wms2 > C code: r.fuzzy, v.in.gshhs > > > Other than that, I'm not seeing any reason to wait on the last > RC for 6.4.3, then write release announcements and make sure all > the packing scripts still work in the next week or two while > that is being tested, and then get the final release out by the > end of the month, hopefully without much in the way of changes. > ? > > > thanks, > Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Helena wrote:
> regarding the r.mapcalc issue in command console on wingrass -
> (sorry I did not make it clear it was for wingrass - it always worked
> well on Mac and linux)
ah, ok, yes it still fails there for me to.
6.4.3svn on XP from the wxGUI command console:
{{{
r.mapcalc "either = 0 || 1"
unterminated string
syntax error, unexpected $end, expecting NAME or STRING
Parse error
'1\""' is not recognized as an internal or external command,
operable program or batch file.
}}}
I've no idea how to fix it.
> It is not critical, windows users can still use the mapcalculator
> GUI where it runs OK, but the r.mapcalc in the command console
> still does not seem to work -
another suggestion to bypass the problem is to start with the MSys or
C:\> command windows; that's actually the default in wingrass7. if a
real terminal should open or not when grass is started with the default
desktop icon remains an open question.
> if I get this confirmed I will file a bug report (I thought I
> already did, but it is not there).
I thought it was there too, maybe it was in the comments of one of
the long tickets about the C:\Files having the \F being treated as
a quoted literal "F"? eg https://trac.osgeo.org/grass/ticket/1447
shrug, nothing here:
https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&component=wxGUI&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&milestone=!7.0.0&keywords=~wingrass
so maybe it needs its own ticket.
> If it is not fixable it should be at least mentioned on the
> known issues web page
> http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Raster_modules
right, a ticket to refer back to would be good though.
Hamish
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
regarding the r.mapcalc issue in command console on wingrass - (sorry I did not make it clear it was for wingrass - it always worked well on Mac and linux) It is not critical, windows users can still use the mapcalculator GUI where it runs OK, but the r.mapcalc in the command console still does not seem to work - tried by a student using June 26 snapshot this is what she says: Here are examples of the commands run and the errors received: r.mapcalc urban2_30m=if(landuse96_28m==1 || landuse96_28m==2,landuse96_28m,null()) syntax error, unexpected $end, expecting ')' Parse error 'landuse96_28m' is not recognized as an internal or external command, operable program or batch file. r.mapcalc MASK=if((elevation<100 && elevation>60) && (landuse96_28m==1 || landuse96_28m==2),1,null()) 1 was unexpected at this time. This is the same we were getting in GRASS6.4.3RC2 and apparently the proposed solutions did not work http://lists.osgeo.org/pipermail/grass-dev/2013-February/062047.html http://lists.osgeo.org/pipermail/grass-dev/2013-March/062607.html if I get this confirmed I will file a bug report (I thought I already did, but it is not there). If it is not fixable it should be at least mentioned on the known issues web page http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Raster_modules Helena > > Helena: >> I am also wondering whether the r.mapcalc expressions with || (or) >> now run from the wxGUI command console. > > I just tried on linux 6.4.3svn wxGUI command console: > r.mapcalc "either = 0 || 1" > and it worked. > > In general I wouldn't be surprised if full command line quoting took > years and huge amounts of effort to (re)perfect. And even then, does > it try to follow Bash conventions, or python, or DOS, or some mix of > all those? How much do we try to (re)teach about command line > techniques in our own docs? Will unquoted input=C:\Users\files\data.txt > always be parsed to input=C:Usersfilesdata.txt (literal \U, \f, \d) > in the command console in that case? > > > best, > Hamish > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hamish wrote: > > anything else to add? MarkusN: > It is not clear to me (lost in too many emails): > - if g.extension is sufficiently ok now AFAIK, yes. On Mac OSX Michael reported some success for grass6, but problems remain with grass7. > - if Python scripts run on Windows which ones? addons or in-built wxgui ones? python addons for grass6 via g.extension are only working on *NIX afaik, but I think python addons for wingrass are not a blocker. they are only a few and we can worry about it in grass-addons svn after release. Perhaps a new include/make/PythonScipt.make for 6.4.4 with .bat file wrappers and rename as needed if the .py extension association remains unsolved? Also the wingrass g.extension[.py] addons come pre-built, so we can apply any fixes post-release there via the server. I am more concerned about people's own custom python scripts and giving them good advice about how to use them in developing their own projects. But that issue could be beyond the scope of any particular release. > - for both, if it improved in the upcoming RC4 categorically I'd say yes, although RC3 likely was the main improvement. is it perfect? probably not but generally working and no longer a reason to delay IMO. > So, perhaps either some related remarks would be good or > a link to the (to be updated) > http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Known_Issues ok, now added to the RC4 news wiki page along with a link to open GRASS 6.x tickets, but the wingrass wiki known issues page is well out of date and needs a cleanup. Helena: > I am also wondering whether the r.mapcalc expressions with || (or) > now run from the wxGUI command console. I just tried on linux 6.4.3svn wxGUI command console: r.mapcalc "either = 0 || 1" and it worked. In general I wouldn't be surprised if full command line quoting took years and huge amounts of effort to (re)perfect. And even then, does it try to follow Bash conventions, or python, or DOS, or some mix of all those? How much do we try to (re)teach about command line techniques in our own docs? Will unquoted input=C:\Users\files\data.txt always be parsed to input=C:Usersfilesdata.txt (literal \U, \f, \d) in the command console in that case? best, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Thu, Jun 27, 2013 at 4:49 PM, Helena Mitasova wrote: > I am also wondering whether the r.mapcalc expressions with || (or) now run > from the wxGUI command console. Probably yes (no idea). > Is this the place to get the right binary to try it out? > http://wingrass.fsv.cvut.cz/grass64/ yes. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I am also wondering whether the r.mapcalc expressions with || (or) now run from the wxGUI command console. Is this the place to get the right binary to try it out? http://wingrass.fsv.cvut.cz/grass64/ Helena On Jun 27, 2013, at 9:33 AM, Markus Neteler wrote: > On Wed, Jun 26, 2013 at 10:29 PM, Hamish wrote: >> I've worked through the changelog and the 6.4.3rc4 release summary page >> seems in order now, >> >> https://trac.osgeo.org/grass/wiki/Release/6.4.3RC4-News > > Thanks. > >> anything else to add? > > It is not clear to me (lost in too many emails): > - if g.extension is sufficiently ok now > - if Python scripts run on Windows > - for both, if it improved in the upcoming RC4 > > So, perhaps either some related remarks would be good or > a link to the (to be updated) > http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Known_Issues > > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, Jun 26, 2013 at 10:29 PM, Hamish wrote: > I've worked through the changelog and the 6.4.3rc4 release summary page seems > in order now, > > https://trac.osgeo.org/grass/wiki/Release/6.4.3RC4-News Thanks. > anything else to add? It is not clear to me (lost in too many emails): - if g.extension is sufficiently ok now - if Python scripts run on Windows - for both, if it improved in the upcoming RC4 So, perhaps either some related remarks would be good or a link to the (to be updated) http://grasswiki.osgeo.org/wiki/WinGRASS_Current_Status#Known_Issues Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I've worked through the changelog and the 6.4.3rc4 release summary page seems in order now, https://trac.osgeo.org/grass/wiki/Release/6.4.3RC4-News anything else to add? thanks, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hamish wrote: > status update time, no blockers, critical bugs triaged, AFAICT we're good to go. > the main two remaining from my perspective are GRASS_PYTHON > in env.bat For wingrass GRASS_PYTHON in env.bat is now set in all branches to C:\Program Files\GRASS\etc\extrabin\python.exe, and PYTHONPATH similarly. So no more startup errors because those two are different, but it doesn't help if you want matplotlib or some other feature from a parallel system-wide install. Also it's unknown how .py associated system-wide by a generic python install will interact. fingers crossed. > and the d.mon Cairo lockup from wxGUI. It seems the G_spawn() in d.mon will need to be changed to a G_spawn_ex() + extra signal/pipe handling. It is both a bit beyond what I know well, and such a critical module that I would not risk to make changes to it in the releasebranch days before release. So hopefully can be fixed asap in devbr6 and backported for 6.4.4 after the 6.4.3 release. For now I have commented out the cairo driver from the wxGUI preferences page in relbr64, so the bug will not be triggered. > > #1428: still some missing some dlls > > We'll have to wait and see how many people complain about > missing msvcr80.dll and msvcr90.dll, and direct them to the > .NET Frameworks package. But it should be fewer than > before.. > > Users stuck behind a proxy server may still have a bad time > trying to download the MS runtimes. NSIS expert needed to > solve that one. (a real issue for students at my univ., but > not a general blocker IMO) fingers crossed.. > > #1971: r.in.bin: fix LFS support in G_ftell() > done, ready to go. (I hope) fingers crossed.. > > #1952: package 'more.exe' with msys (pager for g.list) > > (also +tac.exe +seq.exe +xml2.exe and > >> #1275 (about zip.exe) These apparently take some work, so will wait until Martin has more time; they're not critical, we'll get them next time. I've got local standalone .exe versions of all the core unix powertools from back in the DJGPP days, they could be added into the wingrass package as an extra step if needed. They are a little bit old but because we stay compatible with the SUS for MacOSX they should all work even without the latest new features. > > #854: building addons on Mac Michael reports r.fuzzy building ok on 6.4. (but broken in trunk) > > #: go through changelog for "new and fix" bullet > > points, add to trac wiki page > > #: write the 6.4.3 release announcement and press release > > todo. regards, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Markus N wrote: > >> the RC4 will be released on Thursday, June 20th... > >> so we move on! Hamish: > > why not tag it today? MarkusN: > You had a few things you wanted to get in before given your > previous emails... AFAIK that's all solved or postponed now, & we're ready to go. > (and I am busy to prepare my talks for this FOSS4G-CEE > conference). no worries. regards, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Sat, Jun 15, 2013 at 12:15 PM, Hamish wrote: > Markus N wrote: >> given the code sprint next week: >> http://wiki.osgeo.org/wiki/FOSS4G_CEE_2013_Code_Sprint#GRASS_GIS >> >> the RC4 will be released on Thursday, June 20th... so we >> move on! > > why not tag it today? You had a few things you wanted to get in before given your previous emails... (and I am busy to prepare my talks for this FOSS4G-CEE conference). Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Markus N wrote: > given the code sprint next week: > http://wiki.osgeo.org/wiki/FOSS4G_CEE_2013_Code_Sprint#GRASS_GIS > > the RC4 will be released on Thursday, June 20th... so we > move on! why not tag it today? :o) Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi all, given the code sprint next week: http://wiki.osgeo.org/wiki/FOSS4G_CEE_2013_Code_Sprint#GRASS_GIS the RC4 will be released on Thursday, June 20th... so we move on! Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Michael wrote: > I did a test of g.extension in GRASS > 6.4 svn and 6.5. It works fine on the Mac for the test case > of r.fuzzy. > > GRASS 7 still does not work for me, at least with wxPython > 2.8 (will be doing more testing on 2.9 later today), but > that is not relevant for the 6.4.3 release. thanks Michael, I've been looking forward to hearing about the state of that. for a thorough test, it would be good to check the combination(s) of shell script, python script, and compiled C code, both from the grass command line (g.extension.sh) and the wxGUI (g.exension.py). if it helps save you a few moments of searching, here are some nice examples of those from each category shell: r.surf.volcano, v.points.cog, (plug:) d.anaglyph python: r.diversity, r.in.wms2 C code: r.fuzzy, v.in.gshhs Other than that, I'm not seeing any reason to wait on the last RC for 6.4.3, then write release announcements and make sure all the packing scripts still work in the next week or two while that is being tested, and then get the final release out by the end of the month, hopefully without much in the way of changes. ? thanks, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I did a test of g.extension in GRASS 6.4 svn and 6.5. It works fine on the Mac for the test case of r.fuzzy. GRASS 7 still does not work for me, at least with wxPython 2.8 (will be doing more testing on 2.9 later today), but that is not relevant for the 6.4.3 release. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Jun 5, 2013, at 6:17 PM, William Kyngesburye wrote: > I was partly right - though the demolocation was installed, the Mac install > target did not update the .grassrc70 in it. Update svn and try it now. > > On Jun 5, 2013, at 4:05 PM, Michael Barton wrote: > >> It is located inside the app >> >> GRASS-7.0.app/Contents/MacOS/demolocation >> >> Michael >> >> C. Michael Barton >> Director, Center for Social Dynamics & Complexity >> Professor of Anthropology, School of Human Evolution & Social Change >> Arizona State University >> >> voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) >> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) >> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu >> >> >> >> >> >> >> >> >> >> >> >> On Jun 5, 2013, at 1:44 PM, Markus Neteler >> wrote: >> >>> On Wed, Jun 5, 2013 at 10:40 PM, Michael Barton >>> wrote: The problem with this path... >> LOCATION >> >> not available ...is that it assumes that the user has the source distribution. This path does not exist with a binary-only distribution. >>> >>> ok, then we are almost there: >>> where is demolocation in your binary-only package? >>> That path should be actually used. >>> >>> Markus >> >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev > > - > William Kyngesburye > http://www.kyngchaos.com/ > > First Pogril: Why is life like sticking your head in a bucket filled with > hyena offal? > Second Pogril: I don't know. Why IS life like sticking your head in a bucket > filled with hyena offal? > First Pogril: I don't know either. Wretched, isn't it? > > -HitchHiker's Guide to the Galaxy > > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I was partly right - though the demolocation was installed, the Mac install target did not update the .grassrc70 in it. Update svn and try it now. On Jun 5, 2013, at 4:05 PM, Michael Barton wrote: > It is located inside the app > > GRASS-7.0.app/Contents/MacOS/demolocation > > Michael > > C. Michael Barton > Director, Center for Social Dynamics & Complexity > Professor of Anthropology, School of Human Evolution & Social Change > Arizona State University > > voice:480-965-6262 (SHESC), 480-727-9746 (CSDC) > fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) > www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > > > > > > > > > > > > On Jun 5, 2013, at 1:44 PM, Markus Neteler > wrote: > >> On Wed, Jun 5, 2013 at 10:40 PM, Michael Barton >> wrote: >>> The problem with this path... >>> > LOCATION > > not available >>> >>> ...is that it assumes that the user has the source distribution. This path >>> does not exist with a binary-only distribution. >> >> ok, then we are almost there: >> where is demolocation in your binary-only package? >> That path should be actually used. >> >> Markus > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev - William Kyngesburye http://www.kyngchaos.com/ First Pogril: Why is life like sticking your head in a bucket filled with hyena offal? Second Pogril: I don't know. Why IS life like sticking your head in a bucket filled with hyena offal? First Pogril: I don't know either. Wretched, isn't it? -HitchHiker's Guide to the Galaxy ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
It is located inside the app GRASS-7.0.app/Contents/MacOS/demolocation Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Jun 5, 2013, at 1:44 PM, Markus Neteler wrote: > On Wed, Jun 5, 2013 at 10:40 PM, Michael Barton > wrote: >> The problem with this path... >> LOCATION not available >> >> ...is that it assumes that the user has the source distribution. This path >> does not exist with a binary-only distribution. > > ok, then we are almost there: > where is demolocation in your binary-only package? > That path should be actually used. > > Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Ah, the make install target for OS X is a clone of the main install target, because it needs some custom handling on OS X. It probably needs to be updated to include the demolocation files. On Jun 5, 2013, at 3:37 PM, Markus Neteler wrote: > On Wed, Jun 5, 2013 at 10:08 PM, Michael Barton > wrote: >> I just was able to test g.extension on GRASS 7 compiled yesterday. I tried >> it with r.fuzzy because (IIRC) Markus said it is not broken and should >> install. >> >> Unfortunately, it does not yet work. Here is the error. Note that the >> demolocation is NOT my default or explicitly specified install location >> ($GRASS_ADDON_BASE is /Users/cmbarton/Library/GRASS/7.0/Modules). > > It seems that demolocation is not found? It is used in the virtual session > set up during the compilation process which fails below: > >> g.extension extension=r.fuzzy operation=add >> Fetching from GRASS-Addons SVN (be patient)... >> Compiling... >> main.c: In function 'main': > ... >> ERROR: LOCATION >> >> not available > > Is it possible that the copying of demolocation to that target is not > happening on Mac? It is actually needed. > > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev - William Kyngesburye http://www.kyngchaos.com/ "I ache, therefore I am. Or in my case - I am, therefore I ache." - Marvin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, Jun 5, 2013 at 10:40 PM, Michael Barton wrote: > The problem with this path... > >>> LOCATION >>> >>> not available > > ...is that it assumes that the user has the source distribution. This path > does not exist with a binary-only distribution. ok, then we are almost there: where is demolocation in your binary-only package? That path should be actually used. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
The problem with this path... >> LOCATION >> >> not available ...is that it assumes that the user has the source distribution. This path does not exist with a binary-only distribution. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Jun 5, 2013, at 1:37 PM, Markus Neteler wrote: > On Wed, Jun 5, 2013 at 10:08 PM, Michael Barton > wrote: >> I just was able to test g.extension on GRASS 7 compiled yesterday. I tried >> it with r.fuzzy because (IIRC) Markus said it is not broken and should >> install. >> >> Unfortunately, it does not yet work. Here is the error. Note that the >> demolocation is NOT my default or explicitly specified install location >> ($GRASS_ADDON_BASE is /Users/cmbarton/Library/GRASS/7.0/Modules). > > It seems that demolocation is not found? It is used in the virtual session > set up during the compilation process which fails below: > >> g.extension extension=r.fuzzy operation=add >> Fetching from GRASS-Addons SVN (be patient)... >> Compiling... >> main.c: In function 'main': > ... >> ERROR: LOCATION >> >> not available > > Is it possible that the copying of demolocation to that target is not > happening on Mac? It is actually needed. > > Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, Jun 5, 2013 at 10:08 PM, Michael Barton wrote: > I just was able to test g.extension on GRASS 7 compiled yesterday. I tried it > with r.fuzzy because (IIRC) Markus said it is not broken and should install. > > Unfortunately, it does not yet work. Here is the error. Note that the > demolocation is NOT my default or explicitly specified install location > ($GRASS_ADDON_BASE is /Users/cmbarton/Library/GRASS/7.0/Modules). It seems that demolocation is not found? It is used in the virtual session set up during the compilation process which fails below: > g.extension extension=r.fuzzy operation=add > Fetching from GRASS-Addons SVN (be patient)... > Compiling... > main.c: In function 'main': ... > ERROR: LOCATION > > not available Is it possible that the copying of demolocation to that target is not happening on Mac? It is actually needed. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I'm using it on Mt. Lion with no problems. I'm compiling with backward compatibility to OSX 10.6. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Jun 5, 2013, at 1:26 PM, William Kyngesburye wrote: > Does the GUI work with wxpython 2.8 on Mt Lion? Or on Lion? > > On Jun 5, 2013, at 3:11 PM, Michael Barton wrote: > >> I agree about NOT moving to wxPython 2.9 with this release. We should do it >> with the next one. >> >> Michael >> >> C. Michael Barton >> Director, Center for Social Dynamics & Complexity >> Professor of Anthropology, School of Human Evolution & Social Change >> Arizona State University >> >> voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) >> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) >> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu >> >> >> >> >> >> >> >> >> >> >> >> On Jun 5, 2013, at 1:08 PM, >> wrote: >> >>> From: Martin Landa >>> Subject: Re: [GRASS-dev] GRASS 6.4.3 release planning >>> Date: June 5, 2013 12:43:54 PM MST >>> To: Anna Petrášová >>> Cc: GRASS developers list >>> >>> >>> Hi, >>> >>> 2013/6/5 Anna Petrášová : >>>>> I think it's not good idea to apply wx2.9 patches for 6.4.3. Please >>>>> bear in mind, that we have already 3 release candidates for 6.4.3 (RC1 >>>>> from 10/24/2012 !!!). In this way we will never release 6.4.3... Let's >>>>> move such things to 6.4.4. Let's release the software otherwise most >>>>> of the user will use dev snapshots from SVN... >>>>> >>>> >>>> +1 >>>> >>>> It would be time consuming to fix it, then test, fix again and so on... But >>>> of course, if we plan to release 6.4.3. in July or even later, it's enough >>>> time. I think we should have some deadline. >>> >>> it was discussed several times in the past. We definitely need some >>> deadlines, otherwise we end up always in the same situation when RC >>> covers several months (see, 6.4.0, 6.4.2, 6.4.3 history). Every RC >>> requires some time & energy (MarkusN knows it very well). >>> >>> Martin >> >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev > > - > William Kyngesburye > http://www.kyngchaos.com/ > > The equator is so long, it could encircle the earth completely once. > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Does the GUI work with wxpython 2.8 on Mt Lion? Or on Lion? On Jun 5, 2013, at 3:11 PM, Michael Barton wrote: > I agree about NOT moving to wxPython 2.9 with this release. We should do it > with the next one. > > Michael > > C. Michael Barton > Director, Center for Social Dynamics & Complexity > Professor of Anthropology, School of Human Evolution & Social Change > Arizona State University > > voice:480-965-6262 (SHESC), 480-727-9746 (CSDC) > fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) > www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > > > > > > > > > > > > On Jun 5, 2013, at 1:08 PM, > wrote: > >> From: Martin Landa >> Subject: Re: [GRASS-dev] GRASS 6.4.3 release planning >> Date: June 5, 2013 12:43:54 PM MST >> To: Anna Petrášová >> Cc: GRASS developers list >> >> >> Hi, >> >> 2013/6/5 Anna Petrášová : >>>> I think it's not good idea to apply wx2.9 patches for 6.4.3. Please >>>> bear in mind, that we have already 3 release candidates for 6.4.3 (RC1 >>>> from 10/24/2012 !!!). In this way we will never release 6.4.3... Let's >>>> move such things to 6.4.4. Let's release the software otherwise most >>>> of the user will use dev snapshots from SVN... >>>> >>> >>> +1 >>> >>> It would be time consuming to fix it, then test, fix again and so on... But >>> of course, if we plan to release 6.4.3. in July or even later, it's enough >>> time. I think we should have some deadline. >> >> it was discussed several times in the past. We definitely need some >> deadlines, otherwise we end up always in the same situation when RC >> covers several months (see, 6.4.0, 6.4.2, 6.4.3 history). Every RC >> requires some time & energy (MarkusN knows it very well). >> >> Martin > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev - William Kyngesburye http://www.kyngchaos.com/ The equator is so long, it could encircle the earth completely once. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I agree about NOT moving to wxPython 2.9 with this release. We should do it with the next one. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Jun 5, 2013, at 1:08 PM, wrote: > From: Martin Landa > Subject: Re: [GRASS-dev] GRASS 6.4.3 release planning > Date: June 5, 2013 12:43:54 PM MST > To: Anna Petrášová > Cc: GRASS developers list > > > Hi, > > 2013/6/5 Anna Petrášová : >>> I think it's not good idea to apply wx2.9 patches for 6.4.3. Please >>> bear in mind, that we have already 3 release candidates for 6.4.3 (RC1 >>> from 10/24/2012 !!!). In this way we will never release 6.4.3... Let's >>> move such things to 6.4.4. Let's release the software otherwise most >>> of the user will use dev snapshots from SVN... >>> >> >> +1 >> >> It would be time consuming to fix it, then test, fix again and so on... But >> of course, if we plan to release 6.4.3. in July or even later, it's enough >> time. I think we should have some deadline. > > it was discussed several times in the past. We definitely need some > deadlines, otherwise we end up always in the same situation when RC > covers several months (see, 6.4.0, 6.4.2, 6.4.3 history). Every RC > requires some time & energy (MarkusN knows it very well). > > Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
I just was able to test g.extension on GRASS 7 compiled yesterday. I tried it with r.fuzzy because (IIRC) Markus said it is not broken and should install. Unfortunately, it does not yet work. Here is the error. Note that the demolocation is NOT my default or explicitly specified install location ($GRASS_ADDON_BASE is /Users/cmbarton/Library/GRASS/7.0/Modules). g.extension extension=r.fuzzy operation=add Fetching from GRASS-Addons SVN (be patient)... Compiling... main.c: In function 'main': main.c:152: warning: format not a string literal and no format arguments main.c:156: warning: format not a string literal and no format arguments main.c: In function 'main': main.c:152: warning: format not a string literal and no format arguments main.c:156: warning: format not a string literal and no format arguments access: No such file or directory ERROR: LOCATION not available make[1]: *** [r.fuzzy.set.tmp.html] Error 1 access: No such file or directory ERROR: LOCATION not available make[1]: *** [r.fuzzy.logic.tmp.html] Error 1 main.c: In function 'main': main.c:151: warning: format not a string literal and no format arguments main.c:155: warning: format not a string literal and no format arguments main.c:157: warning: format not a string literal and no format arguments main.c: In function 'main': main.c:151: warning: format not a string literal and no format arguments main.c:155: warning: format not a string literal and no format arguments main.c:157: warning: format not a string literal and no format arguments map_parser.c: In function 'parse_map_file': map_parser.c:92: warning: format not a string literal and no format arguments map_parser.c: In function 'parse_map_file': map_parser.c:92: warning: format not a string literal and no format arguments rule_parser.c: In function 'parse_rules': rule_parser.c:132: warning: format not a string literal and no format arguments rule_parser.c: In function 'parse_rules': rule_parser.c:132: warning: format not a string literal and no format arguments access: No such file or directory ERROR: LOCATION not available make[1]: *** [r.fuzzy.system.tmp.html] Error 1 Installing... make: *** No rule to make target `install'. Stop. WARNING: Installation failed, sorry. Please check above error messages. (Wed Jun 5 13:05:17 2013) Command finished (4 sec) C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On May 25, 2013, at 12:04 PM, epi wrote: > Hi All, > > i just tried to build grass6_release from the svn grass64 svn, Revision: > 56411 > build is fine, no errors detected, but without GUI (wx or tcltk are not > working in my case, montain lion 64 bit build ***) > > to test the extension build i tried : > > g.extension extension=i.landsat.dehaze > > and it worked without errors. > > note : > from the g.extension page the example point to i.landsat.toar (now included > as default in grass) we should change it. > > > *** > i was wondering if the WXgui changes in grass7, to have it running with > wx2.9-cocoa > can be back ported to grass6.x .. is this possible ? > > > thank you, > > Massimo > > > > Il giorno 25/mag/2013, alle ore 12:05, William Kyngesburye > ha scritto: > >> On May 25, 2013, at 5:31 AM, Markus Neteler wrote: >> #854: building addons on Mac (assume we can handle post-release in pkg'ing) --what's the situation? >>> >>> Commonly our Mac packagers package the release (candidate) versions, >>> so we'll know ex-post only. >> >> >> I had some time to look at this, and it should be fixed now, for 6.4 at >> least. (Mac makefile was out of sync with the main makefile) >> >> Michael, if you're back or have dev Mac available, (and Hamish, do you have >> a Mac to try?) - can you verify it works for you? >> >> - >> William Kyngesburye >> http://www.kyngchaos.com/ >> >> "Mon Dieu! but they are all alike. Cheating, murdering, lying, fighting, >> and all for things that the beasts of the jungle would not deign to possess >> - money to purchase the effeminate pleasures of weaklings. And yet withal >> bound down by silly customs that make them slaves to their unhappy lot while >> firm in the belief that they be the lords of creation enjoying the only real >> pleasures of existence >> >> - the wisdom of Tarzan >> >> >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2013/6/5 Anna Petrášová : >> I think it's not good idea to apply wx2.9 patches for 6.4.3. Please >> bear in mind, that we have already 3 release candidates for 6.4.3 (RC1 >> from 10/24/2012 !!!). In this way we will never release 6.4.3... Let's >> move such things to 6.4.4. Let's release the software otherwise most >> of the user will use dev snapshots from SVN... >> > > +1 > > It would be time consuming to fix it, then test, fix again and so on... But > of course, if we plan to release 6.4.3. in July or even later, it's enough > time. I think we should have some deadline. it was discussed several times in the past. We definitely need some deadlines, otherwise we end up always in the same situation when RC covers several months (see, 6.4.0, 6.4.2, 6.4.3 history). Every RC requires some time & energy (MarkusN knows it very well). Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, Jun 5, 2013 at 1:27 PM, Martin Landa wrote: > Hi, > > 2013/6/5 epi : > > i can provide feedback in testing 6.4.x running with wx2.9, > > if you have any kind of patch that i can apply and test > > i'll be happy to try it > > I think it's not good idea to apply wx2.9 patches for 6.4.3. Please > bear in mind, that we have already 3 release candidates for 6.4.3 (RC1 > from 10/24/2012 !!!). In this way we will never release 6.4.3... Let's > move such things to 6.4.4. Let's release the software otherwise most > of the user will use dev snapshots from SVN... > > +1 It would be time consuming to fix it, then test, fix again and so on... But of course, if we plan to release 6.4.3. in July or even later, it's enough time. I think we should have some deadline. Anna > Martin > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
ok, is my understanding that there is a lack of tester on mac, i'll be happy to test any patch or svn update if available (with or without having it included in next release) i agree wx2.9 is not "stable" .. but is also true that is More Than 2 Years that osx user with a full 64bit system are without a working WX-GRASS-GUI hopeful tcltk still work on grass64 :) Il giorno 05/giu/2013, alle ore 07:27, Martin Landa ha scritto: > Hi, > > 2013/6/5 epi : >> i can provide feedback in testing 6.4.x running with wx2.9, >> if you have any kind of patch that i can apply and test >> i'll be happy to try it > > I think it's not good idea to apply wx2.9 patches for 6.4.3. Please > bear in mind, that we have already 3 release candidates for 6.4.3 (RC1 > from 10/24/2012 !!!). In this way we will never release 6.4.3... Let's > move such things to 6.4.4. Let's release the software otherwise most > of the user will use dev snapshots from SVN... > > Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2013/6/5 epi : > i can provide feedback in testing 6.4.x running with wx2.9, > if you have any kind of patch that i can apply and test > i'll be happy to try it I think it's not good idea to apply wx2.9 patches for 6.4.3. Please bear in mind, that we have already 3 release candidates for 6.4.3 (RC1 from 10/24/2012 !!!). In this way we will never release 6.4.3... Let's move such things to 6.4.4. Let's release the software otherwise most of the user will use dev snapshots from SVN... Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
i can provide feedback in testing 6.4.x running with wx2.9, if you have any kind of patch that i can apply and test i'll be happy to try it thanks! Il giorno 05/giu/2013, alle ore 06:16, Hamish ha scritto: > status update time, > > the main two remaining from my perspective are GRASS_PYTHON > in env.bat and the d.mon Cairo lockup from wxGUI. > > i.e. not much. > > > perhaps wx2.9 + Mac if there is movement on it, if stalled > go without it. > > > >> #1428: still some missing some dlls > > We'll have to wait and see how many people complain about > missing msvcr80.dll and msvcr90.dll, and direct them to the > .NET Frameworks package. But it should be fewer than before.. > > Users stuck behind a proxy server may still have a bad time > trying to download the MS runtimes. NSIS expert needed to > solve that one. (a real issue for students at my univ., but > not a general blocker IMO) > > moving on, > > >> #943: selecting cairo rendering locks up the wxGUI > > After the gui code runs 'd.mon start=cairo' it locks up and > you need to use `xkill` to recover. > > I suspect it's some simple waiting for a pipe to close after > a stderr message or so in the wxGUI's custom RunCommand() > python function, but it's not my area of expertise so help > needed. > > If it won't be fixed in the final release we should grey out the > option, but with all the other bugs around that now fixed it > feels so very close to being solved.. > > > >> use full path to GRASS's python.exe in env.bat > > keeps coming up, so seems important & simple to do. > > > >> #1971: r.in.bin: fix LFS support in G_ftell() > > done, ready to go. (I hope) > > > >> #1849: g.proj datum transforms broken for epsg and proj4 terms >> #1967: wxPy loc'n wiz: doesn't allow ellipsoid without datum > > both done, ready to go. (I hope) > lesser issues moved to new tickets targeted at 6.4.4. > > >> #1952: package 'more.exe' with msys (pager for g.list) >>(also +tac.exe +seq.exe +xml2.exe and >>> #1275 (about zip.exe) >> --what controls what unix powertools are packaged >> in extrabin/? > > ? > > zip is there, but unzip (for r.in.srtm) is not. > > xml2.exe makes a big difference for r.in.wms[.sh] which > *now works on wingrass* (!!) / except for the xml2 :) > > seq we could live without but it is nice. > same for tac, we work around it missing for Mac as well. > > but if we figure out how to add one binary we could easily > add them all. > > >> #854: building addons on Mac > > there was some progress in the last week, what was the outcome? > > >> It seems we should also add discussion of wx2.9 + mac to this >> todo or not todo list, and get that into devbr6 ASAP for the >> trial and error. > > if it is not happening now, maybe release a quick 6.4.4 as soon > as that's ready. > > >> #: go through changelog for "new and fix" bullet points, add to trac wiki >> page >> #: write the 6.4.3 release announcement and press release > > todo. > > > regards, > Hamish > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
status update time, the main two remaining from my perspective are GRASS_PYTHON in env.bat and the d.mon Cairo lockup from wxGUI. i.e. not much. perhaps wx2.9 + Mac if there is movement on it, if stalled go without it. > #1428: still some missing some dlls We'll have to wait and see how many people complain about missing msvcr80.dll and msvcr90.dll, and direct them to the .NET Frameworks package. But it should be fewer than before.. Users stuck behind a proxy server may still have a bad time trying to download the MS runtimes. NSIS expert needed to solve that one. (a real issue for students at my univ., but not a general blocker IMO) moving on, > #943: selecting cairo rendering locks up the wxGUI After the gui code runs 'd.mon start=cairo' it locks up and you need to use `xkill` to recover. I suspect it's some simple waiting for a pipe to close after a stderr message or so in the wxGUI's custom RunCommand() python function, but it's not my area of expertise so help needed. If it won't be fixed in the final release we should grey out the option, but with all the other bugs around that now fixed it feels so very close to being solved.. > use full path to GRASS's python.exe in env.bat keeps coming up, so seems important & simple to do. > #1971: r.in.bin: fix LFS support in G_ftell() done, ready to go. (I hope) > #1849: g.proj datum transforms broken for epsg and proj4 terms > #1967: wxPy loc'n wiz: doesn't allow ellipsoid without datum both done, ready to go. (I hope) lesser issues moved to new tickets targeted at 6.4.4. > #1952: package 'more.exe' with msys (pager for g.list) > (also +tac.exe +seq.exe +xml2.exe and >> #1275 (about zip.exe) > --what controls what unix powertools are packaged > in extrabin/? ? zip is there, but unzip (for r.in.srtm) is not. xml2.exe makes a big difference for r.in.wms[.sh] which *now works on wingrass* (!!) / except for the xml2 :) seq we could live without but it is nice. same for tac, we work around it missing for Mac as well. but if we figure out how to add one binary we could easily add them all. > #854: building addons on Mac there was some progress in the last week, what was the outcome? > It seems we should also add discussion of wx2.9 + mac to this > todo or not todo list, and get that into devbr6 ASAP for the > trial and error. if it is not happening now, maybe release a quick 6.4.4 as soon as that's ready. > #: go through changelog for "new and fix" bullet points, add to trac wiki page > #: write the 6.4.3 release announcement and press release todo. regards, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GRASS 6.4.3 release planning
IMHO it's time GRASS 6.4.3 should go out into the wild... >#1967: wxPy loc'n wiz: doesn't allow ellipsoid without datum > --both now in svn, please help test the local projections you know. > You need to check the final result, not just the wizard Summary. > If the location setup terms are bad from offset, we break people's > data silently, ... ouch, first impression of the software too in > case it tracebacks. > --please everyone help test, bad new location def'ns mean > all the work that happens after is also broken-- some teste here http://lists.osgeo.org/pipermail/grass-user/2013-May/068240.html http://lists.osgeo.org/pipermail/grass-user/2013-May/068241.html http://lists.osgeo.org/pipermail/grass-user/2013-May/068242.html - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GRASS-6-4-3-release-planning-tp4995930p5057930.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
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hamish wrote: > > the main thing remaining IMO is to get the location wizard > > working correctly with proj 4.8.0. (the datum transform opts > > were getting reset to the new proj4 defaults regardless of > > what you selected) ... > > changes now ported to all branches. MarkusN wrote: > Good - no break was reported in the past 7 days. but no idea if anyone else tested it, you often get a result, the question is if it's the one you expected. plea for testers now sent to the users ML. > So most issues should be addressed, right? yes, with the exception of from-georef file and from-WKT file not asking you for datum transform opts. (they are left undefined and proj4 decides what default to use (perhaps sometimes none?) depending on what version of PROJ.4 you have installed) > Am I right that r56172 still needs to be backported to > relbranch? It's already backported with the rest. wizard.py is identical in relbr64 and devbr6. in trunk there is the extra planetary ellipsoid support, so a little bit different (but otherwise includes all fixes AFAIK). > > #1428: still some missing some dlls > > ... I don't think that this one is critial since no > complaints came. if dependency walker says there is a missing DLL, it will most likely break the first time someone tries that module; we don't need a complaint to know it. I just tried on a day-old install of Windows7 (GRASS installed after a number of other 3rd party apps), dependency walker was happy for all the DLLs I looked at except for a missing IESHIMS.DLL which seems to be some sort of Vista IE specific thing and e.g. libgis works ok without it. As of a couple of weeks ago a Wingrass install on XP was reporting the following missing DLLs: libpq.dll req's msvcr80.dll tk85.dllreq's msvcr90.dll geotiff.dll req's msvcp90.dll (most probably others too) Either there is different pathways depending on the Windows version, or the osgeo4w buildchain was fully updated to use msvcp100.dll and friends in the last days, it would need to be retested there. > > #1971: r.in.bin: fix LFS support in G_ftell() now in devbr6 for testing. > > #943: cairo rendering fixes > > --Preferences > rendering mode > cairo in grass 6.x doesn't > > work!! > > Opened 3 years ago, hence a "nice to have" fix which should > not block the release. in that case the option should be greyed out in relbr64. I think it's a pretty simple thing, probably with setting some GRASS_RENDER_IMMEDIATE or similar I think it could work. I feel we are very close with it, so don't want to give up trying just yet. The sibling bug is all the tmp and tmp.ppm files piling up in /tmp and %TEMP%, never deleted. > > cleanup/wish-to-dos: > > > > #1952: package 'more.exe' with msys (pager for g.list) > > (also +tac.exe +seq.exe +xml2.exe and maybe +wget.exe) > > --what controls what unix powertools are packaged > > in extrabin/? > > See also ticket #1275 (about zip.exe) ... > > #1936a: Move "Click here to show search module engine" > > to "Search module" tab, freeing up valuable screen real > > estate for the output text window & making the gui > > tab-to-be-in more logical. > > --discussion and wxGUI authors buy-in needed > > ... hence unrelated to the 6.4.3 release. It is not a blocker for 6.4.3, but I fear if it doesn't get discussion now it will stay like that forever. > > #854: building addons on Mac (active efforts) It seems we should also add discussion of wx2.9 + mac to this todo or not todo list, and get that into devbr6 ASAP for the trial and error. (then atomically backport something known to be working instead of experiemnting in the relbr) > I am afraid that we need an RC4 now due to the too many > changes after RC3. maybe so, but in that case RC4 could be short and near identical to final. I feel the release will be much stronger thanks to all the fixes over the last month (working loc'n wizard, PDF output on WinGrass, DLL startup problems finally history, ...) > > see also > >> all grass 6 bugs: https://trac.osgeo.org/grass/report/16 > >> all wingrass bugs: https://trac.osgeo.org/grass/report/14 > >> all wxgui bugs: https://trac.osgeo.org/grass/report/15 thanks, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Sun, May 26, 2013 at 6:02 AM, William Kyngesburye wrote: > On May 25, 2013, at 2:52 PM, Anna Petrášová wrote: > > >> i was wondering if the WXgui changes in grass7, to have it running > with wx2.9-cocoa > >> can be back ported to grass6.x .. is this possible ? > >> > > I haven't really thought about backporting it but yes, it's possible > because the changes consist mainly of renaming (wx.Color -> wx.Colour) and > shifting lines (related to sizers). I would have to find relevant > changesets. I would leave 6.4.3 as it is and do it after release not to > break anything. > > Oh, I thought 6.4.3 was already fixed for wxpython 2.9 (as I try and see > it fail). This is really needed to run the GRASS GUI on OS X 10.7+, > especially 10.8. > So you want to fix it for 6.4.3 now? I can fix some major problems but there are much more, less obvious, problems, especially on Mac. Anna > > - > William Kyngesburye > http://www.kyngchaos.com/ > > [Trillian] What are you supposed to do WITH a maniacally depressed robot? > > [Marvin] You think you have problems? What are you supposed to do if you > ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 > times more intelligent than you and even I don't know the answer... > > - HitchHiker's Guide to the Galaxy > > > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On May 25, 2013, at 2:52 PM, Anna Petrášová wrote: >> i was wondering if the WXgui changes in grass7, to have it running with >> wx2.9-cocoa >> can be back ported to grass6.x .. is this possible ? >> > I haven't really thought about backporting it but yes, it's possible because > the changes consist mainly of renaming (wx.Color -> wx.Colour) and shifting > lines (related to sizers). I would have to find relevant changesets. I would > leave 6.4.3 as it is and do it after release not to break anything. Oh, I thought 6.4.3 was already fixed for wxpython 2.9 (as I try and see it fail). This is really needed to run the GRASS GUI on OS X 10.7+, especially 10.8. - William Kyngesburye http://www.kyngchaos.com/ [Trillian] What are you supposed to do WITH a maniacally depressed robot? [Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer... - HitchHiker's Guide to the Galaxy ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Sat, May 25, 2013 at 9:04 PM, epi wrote: > Hi All, > > i just tried to build grass6_release from the svn grass64 svn, Revision: > 56411 > build is fine, no errors detected, but without GUI (wx or tcltk are not > working in my case, montain lion 64 bit build ***) > > to test the extension build i tried : > > g.extension extension=i.landsat.dehaze > > and it worked without errors. > > note : > from the g.extension page the example point to i.landsat.toar (now > included as default in grass) we should change it. > > > *** > i was wondering if the WXgui changes in grass7, to have it running with > wx2.9-cocoa > can be back ported to grass6.x .. is this possible ? > I haven't really thought about backporting it but yes, it's possible because the changes consist mainly of renaming (wx.Color -> wx.Colour) and shifting lines (related to sizers). I would have to find relevant changesets. I would leave 6.4.3 as it is and do it after release not to break anything. Anna > > > thank you, > > Massimo > > > > Il giorno 25/mag/2013, alle ore 12:05, William Kyngesburye < > wokl...@kyngchaos.com> ha scritto: > > > On May 25, 2013, at 5:31 AM, Markus Neteler wrote: > > > >>> #854: building addons on Mac (assume we can handle post-release in > pkg'ing) > >>> --what's the situation? > >> > >> Commonly our Mac packagers package the release (candidate) versions, > >> so we'll know ex-post only. > > > > > > I had some time to look at this, and it should be fixed now, for 6.4 at > least. (Mac makefile was out of sync with the main makefile) > > > > Michael, if you're back or have dev Mac available, (and Hamish, do you > have a Mac to try?) - can you verify it works for you? > > > > - > > William Kyngesburye > > http://www.kyngchaos.com/ > > > > "Mon Dieu! but they are all alike. Cheating, murdering, lying, > fighting, and all for things that the beasts of the jungle would not deign > to possess - money to purchase the effeminate pleasures of weaklings. And > yet withal bound down by silly customs that make them slaves to their > unhappy lot while firm in the belief that they be the lords of creation > enjoying the only real pleasures of existence > > > > - the wisdom of Tarzan > > > > > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/grass-dev > > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi All, i just tried to build grass6_release from the svn grass64 svn, Revision: 56411 build is fine, no errors detected, but without GUI (wx or tcltk are not working in my case, montain lion 64 bit build ***) to test the extension build i tried : g.extension extension=i.landsat.dehaze and it worked without errors. note : from the g.extension page the example point to i.landsat.toar (now included as default in grass) we should change it. *** i was wondering if the WXgui changes in grass7, to have it running with wx2.9-cocoa can be back ported to grass6.x .. is this possible ? thank you, Massimo Il giorno 25/mag/2013, alle ore 12:05, William Kyngesburye ha scritto: > On May 25, 2013, at 5:31 AM, Markus Neteler wrote: > >>> #854: building addons on Mac (assume we can handle post-release in pkg'ing) >>> --what's the situation? >> >> Commonly our Mac packagers package the release (candidate) versions, >> so we'll know ex-post only. > > > I had some time to look at this, and it should be fixed now, for 6.4 at > least. (Mac makefile was out of sync with the main makefile) > > Michael, if you're back or have dev Mac available, (and Hamish, do you have a > Mac to try?) - can you verify it works for you? > > - > William Kyngesburye > http://www.kyngchaos.com/ > > "Mon Dieu! but they are all alike. Cheating, murdering, lying, fighting, and > all for things that the beasts of the jungle would not deign to possess - > money to purchase the effeminate pleasures of weaklings. And yet withal > bound down by silly customs that make them slaves to their unhappy lot while > firm in the belief that they be the lords of creation enjoying the only real > pleasures of existence > > - the wisdom of Tarzan > > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Thanks. I won't be able to test until next week, but hope to do some recompiles then. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On May 25, 2013, at 6:05 PM, William Kyngesburye wrote: > On May 25, 2013, at 5:31 AM, Markus Neteler wrote: > >>> #854: building addons on Mac (assume we can handle post-release in pkg'ing) >>> --what's the situation? >> >> Commonly our Mac packagers package the release (candidate) versions, >> so we'll know ex-post only. > > > I had some time to look at this, and it should be fixed now, for 6.4 at > least. (Mac makefile was out of sync with the main makefile) > > Michael, if you're back or have dev Mac available, (and Hamish, do you have a > Mac to try?) - can you verify it works for you? > > - > William Kyngesburye > http://www.kyngchaos.com/ > > "Mon Dieu! but they are all alike. Cheating, murdering, lying, fighting, and > all for things that the beasts of the jungle would not deign to possess - > money to purchase the effeminate pleasures of weaklings. And yet withal > bound down by silly customs that make them slaves to their unhappy lot while > firm in the belief that they be the lords of creation enjoying the only real > pleasures of existence > > - the wisdom of Tarzan > > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On May 25, 2013, at 5:31 AM, Markus Neteler wrote: >> #854: building addons on Mac (assume we can handle post-release in pkg'ing) >> --what's the situation? > > Commonly our Mac packagers package the release (candidate) versions, > so we'll know ex-post only. I had some time to look at this, and it should be fixed now, for 6.4 at least. (Mac makefile was out of sync with the main makefile) Michael, if you're back or have dev Mac available, (and Hamish, do you have a Mac to try?) - can you verify it works for you? - William Kyngesburye http://www.kyngchaos.com/ "Mon Dieu! but they are all alike. Cheating, murdering, lying, fighting, and all for things that the beasts of the jungle would not deign to possess - money to purchase the effeminate pleasures of weaklings. And yet withal bound down by silly customs that make them slaves to their unhappy lot while firm in the belief that they be the lords of creation enjoying the only real pleasures of existence - the wisdom of Tarzan ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2013/5/25 Markus Neteler : > MartinL? https://trac.osgeo.org/grass/ticket/1971#comment:7 truly to say, I don't remember any details. Unfortunately I didn't find any relevant discussion on ML or in private channel. Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi,
On Sat, May 18, 2013 at 1:33 PM, Hamish wrote:
> time for the weekend update,
>
> Hamish wrote:
>> fwiw, my to-fix list is now shorter, the main thing remaining
>> IMO is to get the location wizard working correctly with proj
>> 4.8.0. (the datum transform opts were getting reset to the new
>> proj4 defaults regardless of what you selected) There are so many
>> combinations and permutations that every change means many things
>> to re-test and verify, e.g. I haven't even tested from a file or
>> .prj,.wkt at all yet, and that it doesn't break for older proj4s.
>
> (i.e. test the new changes don't break was working with proj 4.7.0)
>
>> --please everyone help test, bad new location def'ns mean
>> all the work that happens after is also broken--
>
> changes now ported to all branches.
Good - no break was reported in the past 7 days.
> breakage:
>
> #1849: g.proj datum transforms broken for epsg and proj4 terms
> (g.proj needed -t flag (as a hack-around) for datum transforms)
https://trac.osgeo.org/grass/ticket/1849#comment:13
So most issues should be addressed, right?
> #1967: wxPy loc'n wiz: doesn't allow ellipsoid without datum
> --both now in svn, please help test the local projections you know.
>You need to check the final result, not just the wizard Summary.
>If the location setup terms are bad from offset, we break people's
>data silently, ... ouch, first impression of the software too in
>case it tracebacks.
Am I right that r56172 still needs to be backported to relbranch? I
don't think that waiting helps since just a few people use devbranch6.
> #1428: still some missing some dlls (were in earlier pkges)
> --needs Dependency Walker testers to experiement on diff't Windows
>versions, with the %PATH% fully set drag dlls from extralibs/+
>onto depends.exe and look for big red "X"s. -> msvcr{80,90}.dll
>another important due to first impressions issue.
>what controls which dlls are packaged in extralib/?
... I don't think that this one is critial since no complaints came. The
recent installer enhancement appear to have addressed most issues.
> #1971: r.in.bin: fix LFS support in G_ftell() (Martin: comments?)
MartinL? https://trac.osgeo.org/grass/ticket/1971#comment:7
> #943: cairo rendering fixes
> --Prefences > rendering mode > cairo in grass 6.x doesn't work!!
Opened 3 years ago, hence a "nice to have" fix which should not
block the release. We are withholding too many goodies if we don't
release 6.4.3 soon.
> cleanup/wish-to-dos:
>
> #1952: package 'more.exe' with msys (pager for g.list)
> (also +tac.exe +seq.exe +xml2.exe and maybe +wget.exe)
> --what controls what unix powertools are packaged in extrabin/?
See also ticket #1275 (about zip.exe)
> #1936a: Move "Click here to show search module engine" to "Search module"
> tab, freeing up valuable screen real estate for the output text
> window & making the gui tab-to-be-in more logical.
> --discussion and wxGUI authors buy-in needed
... hence unrelated to the 6.4.3 release.
> #854: building addons on Mac (assume we can handle post-release in pkg'ing)
> --what's the situation?
Commonly our Mac packagers package the release (candidate) versions,
so we'll know ex-post only.
> #: go through changelog for "new and fix" bullet points, add to trac wiki page
> #: write the 6.4.3 release announcement and press release
I am afraid that we need an RC4 now due to the too many changes after
RC3.
> see also
>> all grass 6 bugs: https://trac.osgeo.org/grass/report/16
>> all wingrass bugs: https://trac.osgeo.org/grass/report/14
>> all wxgui bugs:https://trac.osgeo.org/grass/report/15
>
> thanks & not far to go now,
> Hamish
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
time for the weekend update,
Hamish wrote:
> fwiw, my to-fix list is now shorter, the main thing remaining
> IMO is to get the location wizard working correctly with proj
> 4.8.0. (the datum transform opts were getting reset to the new
> proj4 defaults regardless of what you selected) There are so many
> combinations and permutations that every change means many things
> to re-test and verify, e.g. I haven't even tested from a file or
> .prj,.wkt at all yet, and that it doesn't break for older proj4s.
(i.e. test the new changes don't break was working with proj 4.7.0)
> --please everyone help test, bad new location def'ns mean
> all the work that happens after is also broken--
changes now ported to all branches.
> > > here's my wish list of things to get done before 6.4.3-final-
...
breakage:
#1849: g.proj datum transforms broken for epsg and proj4 terms
(g.proj needed -t flag (as a hack-around) for datum transforms)
#1967: wxPy loc'n wiz: doesn't allow ellipsoid without datum
--both now in svn, please help test the local projections you know.
You need to check the final result, not just the wizard Summary.
If the location setup terms are bad from offset, we break people's
data silently, ... ouch, first impression of the software too in
case it tracebacks.
#1428: still some missing some dlls (were in earlier pkges)
--needs Dependency Walker testers to experiement on diff't Windows
versions, with the %PATH% fully set drag dlls from extralibs/+
onto depends.exe and look for big red "X"s. -> msvcr{80,90}.dll
another important due to first impressions issue.
what controls which dlls are packaged in extralib/?
#1971: r.in.bin: fix LFS support in G_ftell() (Martin: comments?)
#943: cairo rendering fixes
--Prefences > rendering mode > cairo in grass 6.x doesn't work!!
cleanup/wish-to-dos:
#1952: package 'more.exe' with msys (pager for g.list)
(also +tac.exe +seq.exe +xml2.exe and maybe +wget.exe)
--what controls what unix powertools are packaged in extrabin/?
#1936a: Move "Click here to show search module engine" to "Search module"
tab, freeing up valuable screen real estate for the output text
window & making the gui tab-to-be-in more logical.
--discussion and wxGUI authors buy-in needed
#854: building addons on Mac (assume we can handle post-release in pkg'ing)
--what's the situation?
#: go through changelog for "new and fix" bullet points, add to trac wiki page
#: write the 6.4.3 release announcement and press release
see also
> all grass 6 bugs: https://trac.osgeo.org/grass/report/16
> all wingrass bugs: https://trac.osgeo.org/grass/report/14
> all wxgui bugs:https://trac.osgeo.org/grass/report/15
thanks & not far to go now,
Hamish
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hamish: > > #1428: still some missing some dlls (were in earlier pkges) MarkusN: > https://trac.osgeo.org/grass/ticket/1428 > -> It changed from potentially illegal to "perhaps these > will fail", so not critical for the release I think it is better stated as "expected to fail" since dependency walker shows them as big red "X" missing, and so still critical. (anyone using PostGIS + WinGrass who can test?) > > #1952: package 'more.exe' with msys (pager for g.list) > https://trac.osgeo.org/grass/ticket/1952 > -> enhancement, so not critical for the release also in that ticket are some more missing .exes; as above for the dlls, it is unclear to me where the what-to-include selection for that is done. (+wget +tac +seq +xml2 +more) but more.exe is the most important, for GRASS_PAGER= when not at a cmd.exe prompt (so the built-in isn't available) best, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Markus wrote: > this just arrived: ... > ... I hope that we don't miss the train again to get 6.4.3 > into the upcoming OSGeoLive release... don't worry, we won't. (I'm taking care of the grass packaging on the live dvd, end-to-end) fwiw, my to-fix list is now shorter, the main thing remaining IMO is to get the location wizard working correctly with proj 4.8.0. (the datum transform opts were getting reset to the new proj4 defaults regardless of what you selected) There are so many combinations and permutations that every change means many things to re-test and verify, e.g. I haven't even tested from a file or .prj,.wkt at all yet, and that it doesn't break for older proj4s. I'm trying to get it working in devbr6 wingrass first, then porting from there. --please everyone help test, bad new location def'ns mean all the work that happens after is also broken-- todo (in loose order of importance) #1428: still some missing some dlls (were in earlier pkges) #1971: r.in.bin: fix LFS support #1952: package 'more.exe' with msys (pager for g.list) #943: cairo rendering fixes #1936a: Move "Click here to show search module engine" to "Search module" tab, freeing up valuable screen real estate for the output text window. (rfc) #854: building addons on Mac (assume we can handle post-release in pkg'ing) now in progress in devbr6 - #1849: g.proj datum transforms broken for epsg and proj4 terms / g.proj needs -t flag (as a hack-around) for datum transforms / -- traceback error (fixed?) #1967: wxPy loc'n wiz: doesn't allow ellipsoid without datum best, Hamish ps- trac load seems to have gotten worse, often get a can't even connect to the server now. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi all, this just arrived: On Sat, May 11, 2013 at 10:12 PM, Angelos Tzotsos wrote: > Hi all, > > After the last round of e-mails about the base OS for OSGeoLive 7.0, this is > the first alpha based on Xubuntu LTS 12.04.2: > http://aiolos.survey.ntua.gr/gisvm/7.0/ > http://osprey.ucdavis.edu/downloads/osgeo/gisvm/gisvm/7.0alpha1/ > > I think it is a good time for projects to start updating their installers. ... I hope that we don't miss the train again to get 6.4.3 into the upcoming OSGeoLive release... On Thu, May 2, 2013 at 2:19 PM, Hamish wrote: > Markus N wrote: >> What's missing, > > here's my wish list of things to get done before 6.4.3-final- > all are either almost done, has-a-patch, or should-be-easy: ok, so let's just conclude it then...: > #1428: still some missing some dlls (were in earlier pkges) https://trac.osgeo.org/grass/ticket/1428 -> It changed from potentially illegal to "perhaps these will fail", so not critical for the release (meanwhile fixed: #1727, #1946, #1554) > > #1849: g.proj needs -t flag (as a hack-around) for datum transforms https://trac.osgeo.org/grass/ticket/1849 > #1952: package 'more.exe' with msys (pager for g.list) https://trac.osgeo.org/grass/ticket/1952 -> enhancement, so not critical for the release > #1936a: Move "Click here to show search module engine" to "Search module" > tab, freeing up valuable screen real estate for the output text > window. (rfc) > > #1936b: Reword "Protocol" button as "Log file" (strings + docs only) https://trac.osgeo.org/grass/ticket/1936 > #854: building addons on Mac (assume we can handle post-release in pkg'ing) https://trac.osgeo.org/grass/ticket/854 -> unclear state (to me) > I didn't make it past the first two pages of 6.x tickets, but 25 tickets > able to be closed in the past day is pretty good progress. :) Right. Time to release in order to think about 6.4.4 then (and 7 of course). > have a look > all grass 6 bugs: https://trac.osgeo.org/grass/report/16 > all wingrass bugs: https://trac.osgeo.org/grass/report/14 > all wxgui bugs:https://trac.osgeo.org/grass/report/15 Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
2013/5/2 Martin Landa : > 2013/5/2 Anna Kratochvílová : > > [...] > >> Sorry for delaying, there is a pretty high chance to make cartographic >> composer (PDF export) working [1]. Tomorrow it will be clear. > > winGRASS compilation launched manually. In two hours there should be > new build including the last fixes. build 573 is available. Quick test (raster + vector map) with 6.4.3svn: * raster map is still missing in preview * generating PS works* * generating PDF works* Martin * message "Generating ..." doesn't disappear when job is done -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Markus N wrote: > What's missing, here's my wish list of things to get done before 6.4.3-final- all are either almost done, has-a-patch, or should-be-easy: #1428: still some missing some dlls (were in earlier pkges) #1727a: (patch in ticket) script-within-script needs scripts/ in %PATH% #1727b: (now in devbr6 for testing) tcltk stripping C:\ from GISDBASE #1849: g.proj needs -t flag (as a hack-around) for datum transforms #1946: (patch in ticket) clean up .svn in demolocation packaging #1952: package 'more.exe' with msys (pager for g.list) #1554: either get ps2pdf wrapper working or hardcode the gswin32.exe command it calls to get PDF output from the carto composer on wingrass (work in progress) #1936a: Move "Click here to show search module engine" to "Search module" tab, freeing up valuable screen real estate for the output text window. (rfc) #1936b: Reword "Protocol" button as "Log file" (strings + docs only) #854: building addons on Mac (assume we can handle post-release in pkg'ing) I didn't make it past the first two pages of 6.x tickets, but 25 tickets able to be closed in the past day is pretty good progress. :) have a look all grass 6 bugs: https://trac.osgeo.org/grass/report/16 all wingrass bugs: https://trac.osgeo.org/grass/report/14 all wxgui bugs:https://trac.osgeo.org/grass/report/15 thanks, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
2013/5/2 Anna Kratochvílová : [...] > Sorry for delaying, there is a pretty high chance to make cartographic > composer (PDF export) working [1]. Tomorrow it will be clear. winGRASS compilation launched manually. In two hours there should be new build including the last fixes. Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, May 1, 2013 at 2:20 PM, Markus Neteler wrote: > Hi, > > since RC3 was published some days ago and since there are no more blockers: > > 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 > > ... we should get GRASS GIS 6.4.3 final out of the doors. > > What's missing, any objections? Remember that 6.4.4 can follow then. > Sorry for delaying, there is a pretty high chance to make cartographic composer (PDF export) working [1]. Tomorrow it will be clear. Anna [1] https://trac.osgeo.org/grass/ticket/1554#comment:43 > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2013/5/1 Markus Neteler : > ... we should get GRASS GIS 6.4.3 final out of the doors. +1 > What's missing, any objections? Remember that 6.4.4 can follow then. No objections. Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Yes, thanks for the reply Doug On Wed, May 1, 2013 at 8:39 AM, Markus Neteler wrote: > On Wed, May 1, 2013 at 2:32 PM, Newcomb, Doug > wrote: > > Will development of GRASS 7 be proceeding to a release in parallel to > 6.4.4? > > IMHO the two release branches are independent from each other. > Both will be maintained for the foreseeable future but not necessarily > be in sync with the release dates (there is no reason to force that). > > Does this answer the question? > > Markus > -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, May 1, 2013 at 2:32 PM, Newcomb, Doug wrote: > Will development of GRASS 7 be proceeding to a release in parallel to 6.4.4? IMHO the two release branches are independent from each other. Both will be maintained for the foreseeable future but not necessarily be in sync with the release dates (there is no reason to force that). Does this answer the question? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Will development of GRASS 7 be proceeding to a release in parallel to 6.4.4? Doug On Wed, May 1, 2013 at 8:20 AM, Markus Neteler wrote: > Hi, > > since RC3 was published some days ago and since there are no more blockers: > > > 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 > > ... we should get GRASS GIS 6.4.3 final out of the doors. > > What's missing, any objections? Remember that 6.4.4 can follow then. > > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, since RC3 was published some days ago and since there are no more blockers: 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 ... we should get GRASS GIS 6.4.3 final out of the doors. What's missing, any objections? Remember that 6.4.4 can follow then. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Sat, Apr 13, 2013 at 12:32 PM, Markus Neteler wrote: > On Fri, Apr 12, 2013 at 2:50 AM, Hamish wrote: >> Markus N wrote: >>> If there are no objections, I can try to prepare RC3 by >>> tomorrow. >> >> yes please. :) > > ... since Hamish currently backports more from dev6, I'll > postpone RC3 for some hours or whatever suitable. ... packaging now... Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hamish wrote: > kompare/kdiff3/meld were all a bit annoying to set up with > regex filters to avoid $Date$, OBJ.*, .svn/, dist.*, etc., > I should write down some notes in the wiki while it's still > fresh in my mind, but it's too late for today. --> https://trac.osgeo.org/grass/wiki/HowToBackport#Comparingbranches (also documented there how to use the easy-merge addon scripts) Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
[re. what to backport to 6.4.svn] Hamish wrote: > A number or nviz diffs exist too, maybe should be looked at > at some point by the authors. (seems to be Tcl 8.6 api updates, > +) There are changes in nviz too, but I think this is the one that caught my eye: (lib/form/form.c) https://trac.osgeo.org/grass/changeset/35625 --> replaced by --> https://trac.osgeo.org/grass/changeset/35718 Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Sat, Apr 13, 2013 at 2:33 PM, Hamish wrote: > Markus N wrote: >> ... since Hamish currently backports more from dev6, I'll >> postpone RC3 for some hours or whatever suitable. > > thanks, I'm done for now, but there's one outstanding difference > between relbr64 and devbr6 for r.watershed that MarkusM might > have a look at (see below). [snip] > > -->so I'm go for RC3 as soon as r.watershed gets looked at. Done in r55756-7. Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Markus N wrote:
> ... since Hamish currently backports more from dev6, I'll
> postpone RC3 for some hours or whatever suitable.
thanks, I'm done for now, but there's one outstanding difference
between relbr64 and devbr6 for r.watershed that MarkusM might
have a look at (see below). I mostly focused on display/ and
raster/ where most of my changes are. scripts/ and ps/ should
be ok. I tried to just focus on either bugs or simple changes
which were made long long ago so have had tons of testing
already.
Using kdiff3 I notice a few differences in the DB drivers, I
think some extra driver closings and debug experiments were
put into devbr6 for testing zombie dbf.exe errors in WinGrass.
It's probably still worth comparing the two builds on wingrass
to see if they actually help -- aka it will be good to know
what commit definitively fixes it as opposed to guessing that
it might be ok now.
A number or nviz diffs exist too, maybe should be looked at at
some point by the authors. (seems to be Tcl 8.6 api updates, +)
kompare/kdiff3/meld were all a bit annoying to set up with
regex filters to avoid $Date$, OBJ.*, .svn/, dist.*, etc.,
I should write down some notes in the wiki while it's still
fresh in my mind, but it's too late for today.
-->so I'm go for RC3 as soon as r.watershed gets looked at.
regards,
Hamish
---
https://trac.osgeo.org/grass/changeset/54765
https://trac.osgeo.org/grass/changeset/54766
a current diff on raster/r.watershed/ram/do_cum.c, the first
one just seems to be a speedup, the second changes behavior.
--- relbr_6_4/raster/r.watershed/ram/do_cum.c 2013-02-20 17:45:31.877625578
+1300
+++ grass65/raster/r.watershed/ram/do_cum.c 2013-04-12 17:52:36.990693417
+1200
@@ -26,8 +26,8 @@
aspect = asp[this_index];
seg_index_rc(alt_seg, this_index, &r, &c);
if (aspect > 0) {
- dr = r + asp_r[ABS(aspect)];
- dc = c + asp_c[ABS(aspect)];
+ dr = r + asp_r[aspect];
+ dc = c + asp_c[aspect];
}
else
dr = dc = -1;
@@ -149,9 +149,9 @@
seg_index_rc(alt_seg, this_index, &r, &c);
FLAG_SET(worked, r, c);
aspect = asp[this_index];
- if (aspect > 0) {
- dr = r + asp_r[aspect];
- dc = c + asp_c[aspect];
+ if (aspect) {
+ dr = r + asp_r[ABS(aspect)];
+ dc = c + asp_c[ABS(aspect)];
}
else
dr = dc = -1;
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Fri, Apr 12, 2013 at 2:50 AM, Hamish wrote: > Markus N wrote: >> If there are no objections, I can try to prepare RC3 by >> tomorrow. > > yes please. :) ... since Hamish currently backports more from dev6, I'll postpone RC3 for some hours or whatever suitable. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Markus N wrote: > If there are no objections, I can try to prepare RC3 by > tomorrow. yes please. :) thanks, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Sat, Mar 9, 2013 at 7:25 PM, Markus Neteler wrote: > we should get GRASS GIS 6.4.3RC3 out of the doors... If there are no objections, I can try to prepare RC3 by tomorrow. > Here the current state of the art: > > 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 > > Please help to check the remaining tickets. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Sat, Mar 9, 2013 at 7:25 PM, Markus Neteler wrote: > Hi, > > we should get GRASS GIS 6.4.3RC3 out of the doors... > > Here the current state of the art: > > 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 > > Please help to check the remaining tickets. Glad to see that they get continuously less. Power-Hint for Firefox users: if you want to open a set of tickets in one step in different browser tabs, enjoy this Addon: https://addons.mozilla.org/en-US/firefox/addon/multi-links/ To open multiple links, you simply right click and hold to drag a box around the links to desire to take action on. When you release the right mouse button, you will open those links. cheers Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, we should get GRASS GIS 6.4.3RC3 out of the doors... Here the current state of the art: 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 Please help to check the remaining tickets. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Wed, Dec 5, 2012 at 9:49 AM, Martin Landa wrote: > Hi, > > 2012/11/29 Markus Neteler : >> which important backports are lacking for >> the next release candidate? > > it's more then one month from the last RC. I would vote for RC2 at > this point. Martin OK, so let's do it! I'll prepare it now. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2012/11/29 Markus Neteler : > which important backports are lacking for > the next release candidate? it's more then one month from the last RC. I would vote for RC2 at this point. Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning; v.external 3D
On Sun, Dec 2, 2012 at 9:11 PM, Martin Landa wrote: > Hi, > > 2012/12/2 Benjamin Ducke : >> Would it be possible to implement the same >> behaviour in v.in.ogr, i.e. have it auto- >> matically read Z data from 3D sources, instead >> of having to set the "-z" flag manually? >> >> Or would that change the expected behaviour too >> much for a 6.4.x release? > > too much for 6.4.x release. Acceptable for GRASS 7. Martin +1 Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning; v.external 3D
Hi, 2012/12/2 Benjamin Ducke : > Would it be possible to implement the same > behaviour in v.in.ogr, i.e. have it auto- > matically read Z data from 3D sources, instead > of having to set the "-z" flag manually? > > Or would that change the expected behaviour too > much for a 6.4.x release? too much for 6.4.x release. Acceptable for GRASS 7. Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GRASS 6.4.3 release planning; v.external 3D
[..]
And the ability to use v.external with 3D data
sources.
Please try attached v.external64_3D.diff.
That looks good. I will try this (i.e. the
current SVN snapshot) with some 3D data and
report back.
From what I can tell, 3D vertices are read
correctly by v.external now, and the data's Z
extent is also set correctly. Great.
Would it be possible to implement the same
behaviour in v.in.ogr, i.e. have it auto-
matically read Z data from 3D sources, instead
of having to set the "-z" flag manually?
Or would that change the expected behaviour too
much for a 6.4.x release?
Cheers,
Ben
Cheers,
Ben
Markus
--
Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer
bendu...@fastmail.fm
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On 11/30/2012 02:36 PM, Markus Neteler wrote:
On Thu, Nov 29, 2012 at 10:16 PM, Benjamin Ducke wrote:
The "outdir=" option in r.walk.
Do you refer to this potentially missing backport?
https://trac.osgeo.org/grass/ticket/1154#comment:1
Yes, I suppose we need both "outdir=" in r.walk
and "indir=" in r.drain backported to 6.4.x.
And the ability to use v.external with 3D data
sources.
Please try attached v.external64_3D.diff.
That looks good. I will try this (i.e. the
current SVN snapshot) with some 3D data and
report back.
Cheers,
Ben
Markus
--
Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer
bendu...@fastmail.fm
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, 2012/11/30 Markus Neteler : >> And the ability to use v.external with 3D data >> sources. > > Please try attached v.external64_3D.diff. note related to `v.external`, should be fixed in r54116 (relbr64). Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
On Thu, Nov 29, 2012 at 10:16 PM, Benjamin Ducke wrote: > The "outdir=" option in r.walk. Do you refer to this potentially missing backport? https://trac.osgeo.org/grass/ticket/1154#comment:1 > And the ability to use v.external with 3D data > sources. Please try attached v.external64_3D.diff. Markus v.external64_3D.diff Description: Binary data ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
The "outdir=" option in r.walk.
And the ability to use v.external with 3D data
sources.
Best,
Ben
On 11/29/2012 09:16 PM, Markus Neteler wrote:
Hi,
which important backports are lacking for
the next release candidate?
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer
bendu...@fastmail.fm
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
Hi, which important backports are lacking for the next release candidate? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.4.3 release planning
s I hear about the problems, but I have >> MacOS10.6 at home where >> I can test right away, it gets more complicated in terms of logistics if it >> is MS Windows or MacOS10.8 >> And lot of the reported problems are just user error so I don't want to >> submit a bug report >> before confirming that there is a real problem. >> >> 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 >> hmit...@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 Nov 12, 2012, at 3:41 AM, Maris Nartiss wrote: >> >>> Sorry, Michael, but I also couldn't reproduce this issue on my AMD64 >>> Gentoo Linux system. Also code paths leading to crash site seemed to >>> be reasonable. Could it be a bug outside of GRASS (in ctypes?)? >>> >>> No help unless somebody donates a new Mac to Martin or some other >>> WXGUI person for GRASS on Mac testing, as it's not possible to >>> download a free MacOS image for running in a VM. >>> >>> >>> Maris. >>> >>> 2012/11/12 Michael Barton : >>>> >>>> On Nov 11, 2012, at 1:00 PM, grass-dev-requ...@lists.osgeo.org wrote: >>>> >>>> From: Helmut Kudrnovsky >>>> Subject: Re: [GRASS-dev] GRASS 6.4.3 release planning >>>> Date: November 10, 2012 4:22:01 PM MST >>>> To: >>>> >>>> >>>> we may slowly consider 6.4.3RC2 to be prepared. >>>> >>>> >>>> +1 for RC2. Martin >>>> >>>> >>>> maybe it's worth to have a look at: >>>> >>>> wingrass6.4.3svn: raster3d problems >>>> http://trac.osgeo.org/grass/ticket/1784 >>>> >>>> >>>> >>>> >>>> - >>>> best regards >>>> Helmut >>>> >>>> >>>> And volume display does not work at all for the most current 2 OS versions >>>> for Mac (versions after OS X 10.6). >>>> >>>> http://trac.osgeo.org/grass/ticket/1736 >>>> >>>> Michael >>>> >>>> C. Michael Barton >>>> Director, Center for Social Dynamics & Complexity >>>> Professor of Anthropology, School of Human Evolution & Social Change >>>> Arizona State University >>>> >>>> voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) >>>> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) >>>> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> ___ >>>> grass-dev mailing list >>>> grass-dev@lists.osgeo.org >>>> http://lists.osgeo.org/mailman/listinfo/grass-dev >>> ___ >>> grass-dev mailing list >>> grass-dev@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/grass-dev >> > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
