[GRASS-dev] [GRASS GIS] #1950: wingrass: replace rxvt with conhost.exe

GRASS GIS trac at osgeo.org
Thu May 2 03:39:54 PDT 2013

#1950: wingrass: replace rxvt with conhost.exe
  Reporter:  hamish       |       Owner:  grass-dev@…              
      Type:  task         |      Status:  closed                   
  Priority:  major        |   Milestone:  6.4.3                    
 Component:  Packaging    |     Version:  svn-develbranch6         
Resolution:  fixed        |    Keywords:  wingrass                 
  Platform:  MSWindows 7  |         Cpu:  All                      
Changes (by hamish):

  * status:  new => closed
  * resolution:  => fixed


 Replying to [comment:8 hamish]:
 > > I don't care about keeping rxvt. I have no problem with replacing
 > > it if it's for the best. What I care about is last minute untested
 > > [in 6.x] changes in the release branch,

 Replying to [comment:9 mmetz]:
 > It was you how broke translation for 16 languages in the last minute.

 consider 2/400 modules with possibly untranslated descriptions. consider
 also one of the main startup methods of grass about to be released with
 next to ''zero'' field testing.
 Which one is worth losing more sleep over?

 (and again, I mean byte-for-byte in-place implementation in grass on a
 widespread section of end-user systems; time is the only tool we have
 against the subtle unforeseen bugs, it is unhumble of us to assume that we
 can know those).

 > I do not expect to be GRASS 6.4.3rc4 to be released in the next minute.

 maybe not ever. straight to -final! :)

 > > and keeping the development team a nice community to participate in.
 > ?
 > IMHO, what counts is releasing a stable version.

 We all agree on that. The best one we can. I'm trying to throw emphasis on
 the word "stable", by which I mean well tested and problems known +

 > Soon. You prevent this. This is, i.e you are, not nice.

 I do not apologize for filing blocker bugs for license violations or
 things like cmd.exe totally and completely failing to launch. We could not
 launch like that, but they are nearly fixed now so let's keep moving

 If I apologize for anything it's to Martin for sending an email the other
 day about using EPSG codes, which came out harsher than I meant it to for
 something still in early development.

 But for reporting new bugs? No way.

 > Please keep the development team a nice community and do not post
 provoking posts.

 What pissed me off is this: I asked to please wait for a bit before
 committing. You ignored and committed immediately anyway. So yeah,
 That is no way for us to do business.

 > Why did you not "just wait a bit" before breaking translations?

 no one asked for a strings-freeze AFAIK, if there was I missed it.

 > > by the way, you overwrote some local changes to the msys.bat script in
 > > commits. (i.e. our "%PART1%" test to see that paths with spaces were
 > > quoted, see original commit to svn + #905, #629)
 > These are not local changes. The part you refer to is not even in

 the missing piece between the two antithetical sentences above are the
 patches I wrote and submitted to the msys bug system on sourceforge. for
 us as long as nothing changes and the quoting stays fixed it doesn't

 > My .2c:
 > downgrade the osgeo4w python and wxpython versions

 what's the bug? news to me. ticket #?

 > upgrade msys and mingw

 what's missing/broken in the current one? ticket #?

 > fix grass-addons

 where/what? OSX?

 anyway this one is done, let's move on.


Ticket URL: <https://trac.osgeo.org/grass/ticket/1950#comment:10>
GRASS GIS <http://grass.osgeo.org>

More information about the grass-dev mailing list