[GRASS-dev] [GRASS GIS] #2865: Error when installing r.modis add-on and warning when starting grass

GRASS GIS trac at osgeo.org
Wed Jan 20 17:19:55 PST 2016


#2865: Error when installing r.modis add-on and warning when starting grass
-------------------------+-------------------------
  Reporter:  veroandreo  |      Owner:  grass-dev@…
      Type:  defect      |     Status:  new
  Priority:  normal      |  Milestone:  7.0.3
 Component:  Addons      |    Version:  svn-trunk
Resolution:              |   Keywords:  r.modis
       CPU:  x86-64      |   Platform:  Linux
-------------------------+-------------------------

Comment (by veroandreo):

 Replying to [comment:4 martinl]:
 > Replying to [comment:3 veroandreo]:
 >
 > > I was exchanging emails with Luca regarding this issue, and he said he
 tried to fix the problem reported but (quoting him, hope he doesn't mind)
 "it seems bigger than expected. There is no bug in r.modis but the problem
 is in lib/python/script/task.py because it doesn't find r.modis (but the
 problem is there also with r.green)."
 >
 > here you speak about
 >
 >  {{{
 >  GRASS 7.1.svn (latlong_wgs84):~ > r.modis: Unable to fetch interface
 >  description for command 'r.modis'.
 >
 >  Details: [Errno 2] No such file or directory
 >  WARNING: Some addons failed when loading. Please consider to update
 your
 >  addons by running 'g.extension.all -f'.
 >  }}}

 yes

 > I guess. It's harmless error which you can ignore. Yes of course it
 should be fixed. GUI is just trying to parse all addons and it's expecting
 that addon name is same with command (which is not true in the case of
 r.modis or r.green).
 >

 I understand, yes. As they are "groups" of addons, it should try to find
 all r.modis.* or r.green.* and not only r.modis/r.green.

 > The real problem is compilation error which I was not able to reproduce.
 Martin

 I'm using r67612 now, tested again and the same error when installing. Is
 there anything I can do so you have more information to reproduce this
 error yourself? Or any other information I could report and that's
 relevant for this issue?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2865#comment:5>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list