[GRASS-dev] [GRASS GIS] #2598: g.extension compilation fails
#2598: g.extension compilation fails --+- Reporter: ewcgrass | Owner: grass-dev@… Type: defect| Status: new Priority: normal| Milestone: Component: Default | Version: svn-releasebranch70 Keywords:|Platform: Linux Cpu: x86-64| --+- Running GRASS 7.0.1svn(64bit)-2015-02-21, Python 2.7.0, wxPython 2.8.12.0, Linux-2.6.35.14-106.fc14.x86_64-x86_64-with-fedora-14 running g.extension (from gui or from command line) gives: --snip-- g.extension extension=r.damflood svnurl=http://svn.osgeo.org/grass/grass- addons/grass7 Fetching r.damflood from GRASS-Addons SVN repository (be patient)... Compiling... mkdir: cannot create directory `/usr/local/grass7.0.1svn- x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown- linux-gnu': Permission denied make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux- gnu-21_02_2015/dist.x86_64-unknown-linux-gnu] Error 1 ERROR: Compilation failed, sorry. Please check above error messages. --snip-- where g.extension appears to be wanting to write temporary files while compiling (and installing?) to a directory with root privileges, instead of at $HOME/.grass7/addons which based on manual pages should be the default local directory if s flag is not set. I have had same problem with various GRASS-6 versions (where I simply stopped trying to install addons), except for GRASS-6.4.4svn-x86_64-02-11-2013, where g.extension works but with messages like: --snip-- /usr/local/grass6.4.4svn-x86_64-unknown-linux-gnu- 02_11_2013/include/Make/Grass.make:423: warning: overriding recipe for target `/home/rick/data/grassdata/ns-nad83-utm- 25m- 10m/PERMANENT/.tmp/localhost.localdomain/7565.0/r.flip/bin' --snip-- as an apparent work-around, which allowed addons to be installed into $HOME/.grass6/addons directory. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2598 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 7 addons
Hi, 2015-02-25 19:25 GMT+01:00 Brian Miles selimna...@gmail.com: I have some software tools that rely on GRASS addons. I'm starting to test my tools with GRASS 7, and I've found that one of the add-ons, r.findtheriver, which I wrote, installs fine under GRASS 7. However another, r.soils.texture, is not in the GRASS 7 addon repo; perhaps this addon is not compatible? right, first module is there [1], the second module I found only for GRASS 6 [2], so it must be ported to GRASS 7. I may have missed a message about this, but what was the process by which GRASS 6 addons were migrated to GRASS 7? Is there a list of addons that are incompatible with GRASS 7? Migration is up to a maintainer or a user how need this module. The list of modules for GRASS 6 [3], GRASS 7 [4]. Martin [1] http://svn.osgeo.org/grass/grass-addons/grass7/raster/r.findtheriver/ [2] http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.soils.texture/ [3] http://grass.osgeo.org/grass64/manuals/addons/ [4] http://grass.osgeo.org/grass70/manuals/addons/ -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2598: g.extension compilation fails
#2598: g.extension compilation fails --+- Reporter: ewcgrass | Owner: grass-dev@… Type: defect| Status: new Priority: normal| Milestone: 7.0.1 Component: Default | Version: svn-releasebranch70 Keywords:|Platform: Linux Cpu: x86-64| --+- Comment(by martinl): Replying to [ticket:2598 ewcgrass]: where g.extension appears to be wanting to write temporary files while compiling (and installing?) to a directory with root privileges, instead of at $HOME/.grass7/addons which based on manual pages should be the default local directory if s flag is not set. To clarify: compilation is always done in tmp dir. If -s flag is given than the modules is installed to $GISBASE, otherwise to $HOME.grass7/addons. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2598#comment:2 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.extension compilation fails
#2598: g.extension compilation fails --+- Reporter: ewcgrass | Owner: grass-dev@? Type: defect| Status: new Priority: normal| Milestone: Component: Default | Version: svn-releasebranch70 Keywords:|Platform: Linux Cpu: x86-64| --+- Running GRASS 7.0.1svn(64bit)-2015-02-21, Python 2.7.0, wxPython 2.8.12.0, Linux-2.6.35.14-106.fc14.x86_64-x86_64-with-fedora-14 running g.extension (from gui or from command line) gives: --snip-- g.extension extension=r.damflood svnurl=http://svn.osgeo.org/grass/grass- addons/grass7 Fetching r.damflood from GRASS-Addons SVN repository (be patient)... Compiling... mkdir: cannot create directory `/usr/local/grass7.0.1svn- x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown- linux-gnu': Permission denied make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux- gnu-21_02_2015/dist.x86_64-unknown-linux-gnu] Error 1 ERROR: Compilation failed, sorry. Please check above error messages. --snip-- where g.extension appears to be wanting to write temporary files while compiling (and installing?) to a directory with root privileges, instead of at $HOME/.grass7/addons which based on manual pages should be the default local directory if s flag is not set. I too encountered this today. I just changed the permissions of my grass 7 install tree in usr/lib/grass70, and it worked fine. I, too, didn't have any issue in grass6.4. However, I am having a different issue with g.extension, but only for addons I've written myself (and I made another e-mail thread about that). -- Isaac I Ullah, Ph.D. Arizona State University School of Human Evolution and Social Change PO Box 2402 Tempe, AZ 85287-2402 (480) 727-1054 office (650) 201-0479 cell iul...@asu.edu ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.extension error installing addons I've written, what do I change?
Hi, 2015-02-25 20:26 GMT+01:00 Isaac Ullah isaac.ul...@asu.edu: Fetching r.catchment from GRASS-Addons SVN repository (be patient)... Compiling... make: *** No rule to make target `/tmp/tmp3G3Iwq/r.catchment/scripts/r.catchment', needed by `script'. Stop. ERROR: Compilation failed, sorry. Please check above error messages. Python script must end with .py extension, fixed [1], now compiles [2]. Martin [1] http://trac.osgeo.org/grass/changeset/64747 [2] http://grass.osgeo.org/addons/grass7/logs/r.catchment.log -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Cannot install BOTH grass 6 AND grass7 stable from Ubuntu repo..
Hi, 2015-02-25 21:02 GMT+01:00 Sebastiaan Couwenberg sebas...@xs4all.nl: These Conflicts need to be removed from the GRASS upstream packages to allow co-installation of grass grass7. does it mean to remove Conflicts from rules file on Launchpad or? Martin -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Cannot install BOTH grass 6 AND grass7 stable
The cause is the recent addition of conflicts with the official Debian package for grass, see: http://bazaar.launchpad.net/~grass/grass/grass70_release_debian/revision/62 http://lists.osgeo.org/pipermail/grass-dev/2015-February/074161.html These Conflicts need to be removed from the GRASS upstream packages to allow co-installation of grass grass7. Hmm. Ok. I think I get it, but it seems still like a bit of an issue for those of us who need to maintain linux systems that both have the new grass7.0, and are backwards compatible with grass 6 (e.g., for some custom scripts to do modeling), and who don't know about (or want to deal with) the dailies of grass 7.1 upstream (which are not guaranteed to work). If it's not already the plan to make the changes necessary to have the new grass 7.0 alongside the official ubuntu grass6.4, then it probably ought to be. Apologies if this is already in the works! ~Isaac ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] v.to.rast question
How does v.to.rast resolve conflicts (determine the value to ascribe to the cell) when there is more than one polygon (or point) with different attributes that falls in the same cell? For polygons, does the program look at values near or on the centroid, the total area covered by the polygons or what to determine the value of that cell? Thank you, Gail ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Cannot install BOTH grass 6 AND grass7 stable from Ubuntu repo..
On 02/25/2015 08:36 PM, Isaac Ullah wrote: I have a feeling that the package manager believes there to be some conflict, although there should be none. Does anyone have an idea as to what may be causing this, and how it can be fixed? The cause is the recent addition of conflicts with the official Debian package for grass, see: http://bazaar.launchpad.net/~grass/grass/grass70_release_debian/revision/62 http://lists.osgeo.org/pipermail/grass-dev/2015-February/074161.html These Conflicts need to be removed from the GRASS upstream packages to allow co-installation of grass grass7. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2598: g.extension compilation fails
#2598: g.extension compilation fails
--+-
Reporter: ewcgrass | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.1
Component: Default | Version: svn-releasebranch70
Keywords:|Platform: Linux
Cpu: x86-64|
--+-
Changes (by martinl):
* milestone: = 7.0.1
Old description:
Running GRASS 7.0.1svn(64bit)-2015-02-21, Python 2.7.0, wxPython
2.8.12.0, Linux-2.6.35.14-106.fc14.x86_64-x86_64-with-fedora-14
running g.extension (from gui or from command line) gives:
--snip--
g.extension extension=r.damflood svnurl=http://svn.osgeo.org/grass/grass-
addons/grass7
Fetching r.damflood from GRASS-Addons SVN repository (be patient)...
Compiling...
mkdir: cannot create directory `/usr/local/grass7.0.1svn-
x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown-
linux-gnu': Permission denied
make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu] Error 1
ERROR: Compilation failed, sorry. Please check above error messages.
--snip--
where g.extension appears to be wanting to write temporary files while
compiling (and installing?) to a directory with root privileges, instead
of at $HOME/.grass7/addons which based on manual pages should be the
default local directory if s flag is not set.
I have had same problem with various GRASS-6 versions (where I simply
stopped trying to install addons), except for
GRASS-6.4.4svn-x86_64-02-11-2013, where g.extension works but with
messages like:
--snip--
/usr/local/grass6.4.4svn-x86_64-unknown-linux-gnu-
02_11_2013/include/Make/Grass.make:423: warning: overriding
recipe for target `/home/rick/data/grassdata/ns-nad83-utm-
25m-
10m/PERMANENT/.tmp/localhost.localdomain/7565.0/r.flip/bin'
--snip--
as an apparent work-around, which allowed addons to be installed into
$HOME/.grass6/addons directory.
New description:
Running GRASS 7.0.1svn(64bit)-2015-02-21, Python 2.7.0, wxPython 2.8.12.0,
Linux-2.6.35.14-106.fc14.x86_64-x86_64-with-fedora-14
running g.extension (from gui or from command line) gives:
{{{
--snip--
g.extension extension=r.damflood svnurl=http://svn.osgeo.org/grass/grass-
addons/grass7
Fetching r.damflood from GRASS-Addons SVN repository (be patient)...
Compiling...
mkdir: cannot create directory `/usr/local/grass7.0.1svn-
x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown-
linux-gnu': Permission denied
make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu] Error 1
ERROR: Compilation failed, sorry. Please check above error messages.
--snip--
}}}
where g.extension appears to be wanting to write temporary files while
compiling (and installing?) to a directory with root privileges, instead
of at $HOME/.grass7/addons which based on manual pages should be the
default local directory if s flag is not set.
I have had same problem with various GRASS-6 versions (where I simply
stopped trying to install addons), except for
GRASS-6.4.4svn-x86_64-02-11-2013, where g.extension works but with
messages like:
{{{
--snip--
/usr/local/grass6.4.4svn-x86_64-unknown-linux-gnu-
02_11_2013/include/Make/Grass.make:423: warning: overriding
recipe for target `/home/rick/data/grassdata/ns-nad83-utm-
25m-
10m/PERMANENT/.tmp/localhost.localdomain/7565.0/r.flip/bin'
--snip--
}}}
as an apparent work-around, which allowed addons to be installed into
$HOME/.grass6/addons directory.
--
--
Ticket URL: http://trac.osgeo.org/grass/ticket/2598#comment:1
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.extension error installing addons I've written, what do I change?
Ah! I just removed those extension because they were preventing it from running in previous version. Let me fix it on all my other scripts... Thanks! On Wed, Feb 25, 2015 at 1:04 PM, Martin Landa landa.mar...@gmail.com wrote: Hi, 2015-02-25 20:26 GMT+01:00 Isaac Ullah isaac.ul...@asu.edu: Fetching r.catchment from GRASS-Addons SVN repository (be patient)... Compiling... make: *** No rule to make target `/tmp/tmp3G3Iwq/r.catchment/scripts/r.catchment', needed by `script'. Stop. ERROR: Compilation failed, sorry. Please check above error messages. Python script must end with .py extension, fixed [1], now compiles [2]. Martin [1] http://trac.osgeo.org/grass/changeset/64747 [2] http://grass.osgeo.org/addons/grass7/logs/r.catchment.log -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa -- Isaac I Ullah, Ph.D. Arizona State University School of Human Evolution and Social Change PO Box 2402 Tempe, AZ 85287-2402 (480) 727-1054 office (650) 201-0479 cell iul...@asu.edu ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2598: g.extension compilation fails
#2598: g.extension compilation fails
--+-
Reporter: ewcgrass | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.1
Component: Default | Version: svn-releasebranch70
Keywords:|Platform: Linux
Cpu: x86-64|
--+-
Comment(by martinl):
Replying to [ticket:2598 ewcgrass]:
{{{
--snip--
g.extension extension=r.damflood svnurl=http://svn.osgeo.org/grass
/grass-addons/grass7
}}}
strange please try to run this module with `--v` flag. I cannot reproduce
this error.
--
Ticket URL: http://trac.osgeo.org/grass/ticket/2598#comment:3
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Cannot install BOTH grass 6 AND grass7 stable from Ubuntu repo..
On 02/25/2015 09:08 PM, Martin Landa wrote:
Hi,
2015-02-25 21:02 GMT+01:00 Sebastiaan Couwenberg sebas...@xs4all.nl:
These Conflicts need to be removed from the GRASS upstream packages to
allow co-installation of grass grass7.
does it mean to remove Conflicts from rules file on Launchpad or?
Yes, you need to remove the Conflicts from the GRASS packaging on
Launchpad to fix this issue.
While you're at it, there are some fixes you need in
grass7-core.links grass7-core.links.in:
- remove the symlink from grass70 to itself,
the symlink from grass to grass70 was a cause of conflicts between
the grass grass70 packages.
- remove the symlink from grass@vers...@.1.gz to grass.1.gz,
grass7-core.links is correct, but grass7-core.links.in is not.
The man pages in grass7-doc.install{,.in} is still a cause of conflict
between the grass grass7 packages. Instead of use Conflicts to prevent
co-installation with dependencies, using the alternatives system to
switch between version like openjdk-6 7 uses is probably better.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GRASS 7 addons
Hello, I have some software tools that rely on GRASS addons. I'm starting to test my tools with GRASS 7, and I've found that one of the add-ons, r.findtheriver, which I wrote, installs fine under GRASS 7. However another, r.soils.texture, is not in the GRASS 7 addon repo; perhaps this addon is not compatible? I may have missed a message about this, but what was the process by which GRASS 6 addons were migrated to GRASS 7? Is there a list of addons that are incompatible with GRASS 7? What's the process for getting a formerly incompatible addon into the GRASS 7 repo? (assuming myself or someone else fixes the compatibility issues) Thanks, Brian ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Cannot install BOTH grass 6 AND grass7 stable from Ubuntu repo..
Hi all, I maintain a small group of linux machines, all with Xubuntu 14.04 on them. I recently worked out a way (with help from Martin and Markus) to be able to have the previous devel version of GRASS 70 installable via the ppa repositories grass-devel and ubuntugis-unstable, which worked well and let me maintain current grass7 installs on all my machines, alongside grass6 stable. This has changed with the release of grass7 stable, which I'm trying to upgrade to on all the machines. What happens is that the ubuntu package manager will not let me have BOTH grass7 stable AND grass6 stable installed at the same time. I have a feeling that the package manager believes there to be some conflict, although there should be none. Does anyone have an idea as to what may be causing this, and how it can be fixed? I'm happy to help in any way that I can, but repo packaging is not something I know a huge amount about. Oh, and to add just an extra twist, I'm able to install the grass 7 daily package along side either grass7 or grass6. It seems just that the two stable releases cannot live together (at least according to the package manager)... Cheers, -- Isaac I Ullah, Ph.D. Arizona State University School of Human Evolution and Social Change PO Box 2402 Tempe, AZ 85287-2402 (480) 727-1054 office (650) 201-0479 cell iul...@asu.edu ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] g.extension error installing addons I've written, what do I change?
Hi all, I've been updating the addons I've written in GRASS6 to versions for GRASS7, and have been adding them to the GRASS7 addon svn, but it seems that I'm doing something wrong. The scripts all run fine from my own computer when I manually put them in my GRASS_ADDON_PATH, but when I, or others, try to install them from g.extension, we get the following error: Fetching r.catchment from GRASS-Addons SVN repository (be patient)... Compiling... make: *** No rule to make target `/tmp/tmp3G3Iwq/r.catchment/scripts/r.catchment', needed by `script'. Stop. ERROR: Compilation failed, sorry. Please check above error messages. Any other addons will install fine, including others that are also python scripts. This is happening with all three of the scrips I've converted so far (r.catchment, r.landscape.evol, and r.viewshed.cva). I've been using other python scripts in the addons svn as templates for the format of the makefile, html description, and the headers for my own scripts, but it seems like nothing I do is making this work properly. Here is a link to the svn repo for my r.catchment script, which sets off the above error: https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.catchment Here's a link to the r.basins script, which is not mine, and does NOT set off the above error: https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.basin Can anybody see what I am doing wrong here? Any help will be GREATLY appreciated!!! -- Isaac I Ullah, Ph.D. Arizona State University School of Human Evolution and Social Change PO Box 2402 Tempe, AZ 85287-2402 (480) 727-1054 office (650) 201-0479 cell iul...@asu.edu ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS] #2599: PyGRASS Raster execution error
#2599: PyGRASS Raster execution error +--- Reporter: aandre | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: Component: Python | Version: svn-releasebranch70 Keywords: raster |Platform: All Cpu: All | +--- Hello, creating my first ticket, i hope it's relevant and the way to do it. I get 2 errors while executing Python scripts. source:/branches/releasebranch_7_0/lib/python/pygrass/raster/__init__.py#L415 source:/branches/releasebranch_7_0/lib/python/pygrass/raster/__init__.py#L416 I attached a diff file. Regards, Adrien -- Ticket URL: https://trac.osgeo.org/grass/ticket/2599 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Cannot install BOTH grass 6 AND grass7 stable from Ubuntu repo..
Hi,
2015-02-25 21:18 GMT+01:00 Sebastiaan Couwenberg sebas...@xs4all.nl:
While you're at it, there are some fixes you need in
grass7-core.links grass7-core.links.in:
- remove the symlink from grass70 to itself,
the symlink from grass to grass70 was a cause of conflicts between
the grass grass70 packages.
- remove the symlink from grass@vers...@.1.gz to grass.1.gz,
grass7-core.links is correct, but grass7-core.links.in is not.
I fixed these issues and put to Launchpad the new packages as
`7.0.0-7`. Testing welcomed (the new package should be available in
30min).
The man pages in grass7-doc.install{,.in} is still a cause of conflict
between the grass grass7 packages. Instead of use Conflicts to prevent
co-installation with dependencies, using the alternatives system to
switch between version like openjdk-6 7 uses is probably better.
This issue is still open. Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Cannot install BOTH grass 6 AND grass7 stable from Ubuntu repo..
On 02/25/2015 09:19 PM, Isaac Ullah wrote: If it's not already the plan to make the changes necessary to have the new grass 7.0 alongside the official ubuntu grass6.4, then it probably ought to be. Apologies if this is already in the works! Apology accepted, because that's what the grass70 package name thread I linked to is about. The intention is to allow co-installation, but also preventing conflicts between the official Debian package and those from the GRASS PPA. The Conflicts change I proposed prevents some conflicts between the official Debian package and the GRASS PPA, but prevents co-installation as you have experienced. The /usr/bin/grass /usr/bin/x-grass symlinks in grass-core are not a problem anymore, but there is still any issue with the man pages as I wrote earlier in this thread. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] No overwrite option in grass 7 addon scripts?
Hi all, sorry for the spat of messages today, but as you can tell, I'm having trouble getting my addon scripts up to par for GRASS7 standard. I'm trying to figure these issues out on my own, but I can't seem to find any documentation that can help me do so. My current issue is that I'm noticing that my python scripts are lacking the automatically generated flag for --overwrite in the GUI. One can add --overwrite to the command line (and it works fine), but it's not there in the GUI. I'm trying to use the grass.overwrite() syntax for all internal grass module calls in the script, and this issue is making that difficult. I've updated my g.parser header code in the scripts to reflect what I believe is the latest syntax (based on other addon scripts in the svn). eg: #%option G_OPT_R_ELEV #% key: elev #% description: Input elevation map (DEM) #% required : yes #%END #%option G_OPT_R_INPUT #% key: output #% description: Output CVA raster #% required : yes #%END But with this I get no overwrite flag option in the GUI, even though other addon scripts that seem to be using this DO get overwrite flags added. If I do it the old way: #%option #% key: elev #% type: string #% gisprompt: old,cell,raster #% description: Input elevation map (DEM) #% required : yes #%END #%option #% key: output #% type: string #% gisprompt: old,cell,raster #% description: Output CVA raster #% required : yes #%END I also get no overwrite option in the module GUI. However, if I do this: #%option #% key: elev #% type: string #% gisprompt: new,cell,raster #% description: Input elevation map (DEM) #% required : yes #%END #%option #% key: output #% type: string #% gisprompt: new,cell,raster #% description: Output CVA raster #% required : yes #%END Then I DO get the overwrite option! However, when I do this, I then get the error that my input maps already exist (even though these are just input maps, and not output). So, I suppose I'm confused about how I'm supposed to do this now? I've looked through the many new pages of python code documentation on the wiki, etc, and can't find anything at all about this... Again, any help is greatly appreciated! -- Isaac I Ullah, Ph.D. Arizona State University School of Human Evolution and Social Change PO Box 2402 Tempe, AZ 85287-2402 (480) 727-1054 office (650) 201-0479 cell iul...@asu.edu ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2598: g.extension compilation fails
#2598: g.extension compilation fails
--+-
Reporter: ewcgrass | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.1
Component: Default | Version: svn-releasebranch70
Keywords:|Platform: Linux
Cpu: x86-64|
--+-
Comment(by ewcgrass):
Here is the output with the --verbose flag
{{{
g.extension --verbose extension=r.damflood
svnurl=http://svn.osgeo.org/grass/grass-addons/grass7
Fetching r.damflood from GRASS-Addons SVN repository (be patient)...
Ar.damflood/SWE.c
Ar.damflood/SWE.h
Ar.damflood/main.c
Ar.damflood/r.damflood.html
Ar.damflood/dam_failure.png
Ar.damflood/Makefile
Checked out revision 64750.
Compiling...
mkdir: cannot create directory `/usr/local/grass7.0.1svn-
x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown-
linux-gnu': Permission denied
make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu] Error 1
ERROR: Compilation failed, sorry. Please check above error messages.
mkdir -p /usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu
(Wed Feb 25 18:07:45 2015) Command finished (2 sec)
}}}
Again, g.extension wants to create temporary directories in
/usr/local/grass where it does not have permission to do so.
I ran g.extension repeatedly, each time manually creating (as root user)
the directories that are wanting to be created and causing permission
errors (i.e. /bin.x86_64-unknown-linux-gnu, /dist.x86_64-unknown-linux-
gnu, and within this latter one, /driver/db, /fonts, /include/grass,
/lib). As I was approaching of this, these were the messages being
received:
{{{
g.extension --verbose extension=r.damflood
svnurl=http://svn.osgeo.org/grass/grass-addons/grass7
Fetching r.damflood from GRASS-Addons SVN repository (be patient)...
Ar.damflood/SWE.c
Ar.damflood/SWE.h
Ar.damflood/main.c
Ar.damflood/r.damflood.html
Ar.damflood/dam_failure.png
Ar.damflood/Makefile
Checked out revision 64750.
mkdir -p /tmp/tmpmAdoGF/r.damflood/bin
mkdir -p /tmp/tmpmAdoGF/r.damflood/etc
mkdir -p /usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu/docs
Compiling...
mkdir: cannot create directory `/usr/local/grass7.0.1svn-
x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown-
linux-gnu/docs': Permission denied
make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu/docs] Error 1
ERROR: Compilation failed, sorry. Please check above error messages.
(Wed Feb 25 18:43:56 2015) Command finished (2 sec)
}}}
and
{{{
g.extension --verbose extension=r.damflood
svnurl=http://svn.osgeo.org/grass/grass-addons/grass7
Fetching r.damflood from GRASS-Addons SVN repository (be patient)...
Ar.damflood/SWE.c
Ar.damflood/SWE.h
Ar.damflood/main.c
Ar.damflood/r.damflood.html
Ar.damflood/dam_failure.png
Ar.damflood/Makefile
Checked out revision 64750.
mkdir -p /tmp/tmpEhkPVn/r.damflood/bin
mkdir -p /tmp/tmpEhkPVn/r.damflood/etc
mkdir -p /tmp/tmpEhkPVn/r.damflood/docs/html
mkdir -p /tmp/tmpEhkPVn/r.damflood/docs/man
mkdir -p /tmp/tmpEhkPVn/r.damflood/docs/man/man1
mkdir -p /usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu/tools
Compiling...
mkdir: cannot create directory `/usr/local/grass7.0.1svn-
x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown-
linux-gnu/tools': Permission denied
make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux-
gnu-21_02_2015/dist.x86_64-unknown-linux-gnu/tools] Error 1
ERROR: Compilation failed, sorry. Please check above error messages.
(Wed Feb 25 18:45:34 2015) Command finished (2 sec)
}}}
So as I'm creating the requested directories within /dist.x86_64-unknown-
linux-gnu, it's appearing as if g.extension is able to create the
directories and files it needs in /tmp.
Finally, after creating the last of the two directories causing permission
errors (i.e. /dist.x86_64-unknown-linux-gnu/docs and /dist.x86_64-unknown-
linux-gnu/tools), this is what I get as output:
{{{
g.extension --verbose extension=r.damflood
svnurl=http://svn.osgeo.org/grass/grass-addons/grass7
Fetching r.damflood from GRASS-Addons SVN repository (be patient)...
Ar.damflood/SWE.c
Ar.damflood/SWE.h
Ar.damflood/main.c
Compiling...
Ar.damflood/r.damflood.html
Ar.damflood/dam_failure.png
Ar.damflood/Makefile
Checked out revision 64750.
mkdir -p /tmp/tmpwy0eZb/r.damflood/bin
mkdir -p /tmp/tmpwy0eZb/r.damflood/etc
mkdir -p /tmp/tmpwy0eZb/r.damflood/docs/html
mkdir -p /tmp/tmpwy0eZb/r.damflood/docs/man
Re: [GRASS-dev] [GRASS GIS] #2599: PyGRASS Raster execution error
#2599: PyGRASS Raster execution error +--- Reporter: aandre | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: Component: Python | Version: svn-releasebranch70 Keywords: raster |Platform: All Cpu: All | +--- Comment(by wenzeslaus): Replying to [ticket:2599 aandre]: creating my first ticket, i hope it's relevant and the way to do it. This is definitively the way. Tickets with patch attached are greatly appreciated. There is few things you can improve. I get 2 errors while executing Python scripts. It would be good if you can post what are the steps to reproduce the error you got. In your case probably your Python code but not the whole thing, just minimal piece of code which produces the error (e.g. taken from interactive command line). Use data from [http://grass.osgeo.org/download /sample-data/ GRASS GIS NC sample dataset] to help others easily reproduce the problem you have. In ideal case, your code can be used to create a test case which would now expose the error and later serve as a failsafe that the error won't happen again. -- Ticket URL: https://trac.osgeo.org/grass/ticket/2599#comment:1 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] No overwrite option in grass 7 addon scripts?
On Wed, Feb 25, 2015 at 4:49 PM, Isaac Ullah isaac.ul...@asu.edu wrote: Hi all, sorry for the spat of messages today, but as you can tell, I'm having trouble getting my addon scripts up to par for GRASS7 standard. I'm trying to figure these issues out on my own, but I can't seem to find any documentation that can help me do so. My current issue is that I'm noticing that my python scripts are lacking the automatically generated flag for --overwrite in the GUI. One can add --overwrite to the command line (and it works fine), but it's not there in the GUI. I'm trying to use the grass.overwrite() syntax for all internal grass module calls in the script, and this issue is making that difficult. I've updated my g.parser header code in the scripts to reflect what I believe is the latest syntax (based on other addon scripts in the svn). eg: #%option G_OPT_R_ELEV #% key: elev #% description: Input elevation map (DEM) #% required : yes #%END #%option G_OPT_R_INPUT #% key: output #% description: Output CVA raster #% required : yes #%END But with this I get no overwrite flag option in the GUI, even though other addon scripts that seem to be using this DO get overwrite flags added. If I do it the old way: #%option #% key: elev #% type: string #% gisprompt: old,cell,raster #% description: Input elevation map (DEM) #% required : yes #%END #%option #% key: output #% type: string #% gisprompt: old,cell,raster #% description: Output CVA raster #% required : yes #%END I also get no overwrite option in the module GUI. However, if I do this: #%option #% key: elev #% type: string #% gisprompt: new,cell,raster #% description: Input elevation map (DEM) #% required : yes #%END #%option #% key: output #% type: string #% gisprompt: new,cell,raster #% description: Output CVA raster #% required : yes #%END Then I DO get the overwrite option! However, when I do this, I then get the error that my input maps already exist (even though these are just input maps, and not output). So, I suppose I'm confused about how I'm supposed to do this now? I've looked through the many new pages of python code documentation on the wiki, etc, and can't find anything at all about this... Again, any help is greatly appreciated! You should be using standardized option G_OPT_R_INPUT, the definition can be found here: http://grass.osgeo.org/programming7/parser__standard__options_8c_source.html The key here is to specify 'new' in gisprompt, but only for output map. 'new' means that a new map will be created and parser then knows that it should check whether there is already a map of such name and if yes, require overwrite. Based on 'new', the overwrite flag is created. Anna -- Isaac I Ullah, Ph.D. Arizona State University School of Human Evolution and Social Change PO Box 2402 Tempe, AZ 85287-2402 (480) 727-1054 office (650) 201-0479 cell iul...@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
Re: [GRASS-dev] winGRASS 64bit
Martin Landa wrote: I am hopefully close to winGRASS7 64bit build. Currently I am trying to solve this issue: OBJ.x86_64-pc-mingw32/ls_filter.o:ls_filter.c:(.text+0x3e9): undefined reference to `__imp_regexec' ... c:/MinGW64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld.exe: OBJ.x86_64-pc-mingw32/ls_filter.o: bad reloc address 0x0 in section `.data' collect2.exe: error: ld returned 1 exit status make[3]: *** [/osgeo4w/usr/src/grass700/dist.x86_64-pc-mingw32/lib/libgrass_gis.7.0.0.dll] Error 1 Any kind of hint will be highly appreciated, thanks in advance, Martin undefined reference to __imp_ usually means that it found the import library but not the corresponding DLL. Or maybe it's finding a 32-bit version? MSVCRT doesn't have the regex.h functions; MinGW uses a port of the regex functionality from GNU libc. -- Glynn Clements gl...@gclements.plus.com ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.extension compilation fails
On Wed, Feb 25, 2015 at 2:52 PM, Isaac Ullah isaac.ul...@asu.edu wrote: #2598: g.extension compilation fails --+- Reporter: ewcgrass | Owner: grass-dev@? Type: defect| Status: new Priority: normal| Milestone: Component: Default | Version: svn-releasebranch70 Keywords:|Platform: Linux Cpu: x86-64| --+- Running GRASS 7.0.1svn(64bit)-2015-02-21, Python 2.7.0, wxPython 2.8.12.0, Linux-2.6.35.14-106.fc14.x86_64-x86_64-with-fedora-14 running g.extension (from gui or from command line) gives: --snip-- g.extension extension=r.damflood svnurl=http://svn.osgeo.org/grass/grass- addons/grass7 Fetching r.damflood from GRASS-Addons SVN repository (be patient)... Compiling... mkdir: cannot create directory `/usr/local/grass7.0.1svn- x86_64-unknown-linux-gnu-21_02_2015/dist.x86_64-unknown- linux-gnu': Permission denied make: *** [/usr/local/grass7.0.1svn-x86_64-unknown-linux- gnu-21_02_2015/dist.x86_64-unknown-linux-gnu] Error 1 ERROR: Compilation failed, sorry. Please check above error messages. --snip-- where g.extension appears to be wanting to write temporary files while compiling (and installing?) to a directory with root privileges, instead of at $HOME/.grass7/addons which based on manual pages should be the default local directory if s flag is not set. I too encountered this today. I just changed the permissions of my grass 7 install tree in usr/lib/grass70, and it worked fine. I, too, didn't have any issue in grass6.4. However, I am having a different issue with g.extension, but only for addons I've written myself (and I made another e-mail thread about that). Please, write that directly to the ticket on Trac: http://trac.osgeo.org/grass/ticket/2598 Put there also how did you change the permissions. g.extension should install by default to .grass7 in your how directory (or equivalent) or if executed with sudo (or equivalent), it will put data into system directory (neither option should require change of permissions). Vaclav -- Isaac I Ullah, Ph.D. Arizona State University School of Human Evolution and Social Change PO Box 2402 Tempe, AZ 85287-2402 (480) 727-1054 office (650) 201-0479 cell iul...@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
Re: [GRASS-dev] GRASS 7 addons
cc’ing Gianluca Massei, the author of r.soils.texture … See my comments inline. Thanks, Brian On Feb 25, 2015, at 2:45 PM, Martin Landa landa.mar...@gmail.com wrote: Hi, 2015-02-25 19:25 GMT+01:00 Brian Miles selimna...@gmail.com: I have some software tools that rely on GRASS addons. I'm starting to test my tools with GRASS 7, and I've found that one of the add-ons, r.findtheriver, which I wrote, installs fine under GRASS 7. However another, r.soils.texture, is not in the GRASS 7 addon repo; perhaps this addon is not compatible? right, first module is there [1], the second module I found only for GRASS 6 [2], so it must be ported to GRASS 7. Interesting. I don’t recall putting r.findtheriver in the GRASS 7 addon’s repo when I contributed it to the GRASS 6 addons repo. I’m not sure how it made its way into the GRASS 7 repo. I may have missed a message about this, but what was the process by which GRASS 6 addons were migrated to GRASS 7? Is there a list of addons that are incompatible with GRASS 7? Migration is up to a maintainer or a user how need this module. The list of modules for GRASS 6 [3], GRASS 7 [4]. Gianluca, are you planning/able to port r.soils.texture to GRASS 7? Martin [1] http://svn.osgeo.org/grass/grass-addons/grass7/raster/r.findtheriver/ [2] http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.soils.texture/ [3] http://grass.osgeo.org/grass64/manuals/addons/ [4] http://grass.osgeo.org/grass70/manuals/addons/ -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] winGRASS 64bit
Hi, I am hopefully close to winGRASS7 64bit build. Currently I am trying to solve this issue: OBJ.x86_64-pc-mingw32/ls_filter.o:ls_filter.c:(.text+0x3e9): undefined reference to `__imp_regexec' ... c:/MinGW64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld.exe: OBJ.x86_64-pc-mingw32/ls_filter.o: bad reloc address 0x0 in section `.data' collect2.exe: error: ld returned 1 exit status make[3]: *** [/osgeo4w/usr/src/grass700/dist.x86_64-pc-mingw32/lib/libgrass_gis.7.0.0.dll] Error 1 Any kind of hint will be highly appreciated, thanks in advance, Martin -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Make it clearer that GRASS 7.0 is the version to go for now
On Wed, Feb 25, 2015 at 2:23 AM, Vaclav Petras wenzesl...@gmail.com wrote: The news page [1] contains link to GRASS GIS packages in OSGeo4W which is great if you already have OSGeo4W but you have to figure out how to download it. What about: winGRASS 7.0.0: standalone installer | OSGeo4W installer (description of GRASS GIS packages) ... the line would become very long then. For now I simplified it to winGRASS which points to http://grass.osgeo.org/download/software/ms-windows/ In case we should improve that page. Markus where OSGeo4W installer goes to [3] and description of GRASS GIS packages goes to [2]? [1] http://grass.osgeo.org/news/42/15/GRASS-GIS-7-0-0/ [2] http://trac.osgeo.org/osgeo4w/wiki/pkg-grass [3] http://trac.osgeo.org/osgeo4w/ ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
