[GRASS-dev] addon mismatch

hi,

in https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector there is

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/v.in.gbif.log

but the manual can't be find here:

https://grass.osgeo.org/grass70/manuals/addons/

and the pre-built addon can't be found by g.extension in a winGRASS7.0.svn
session.

any idea?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

hi,

in https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector there is

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/v.in.gbif.log

but the manual can’t be find here:

https://grass.osgeo.org/grass70/manuals/addons/

and the pre-built addon can’t be found by g.extension in a winGRASS7.0.svn
session.

any idea?

I don’t have a clear idea how the system works but this addon is not even mentioned in

https://grass.osgeo.org/addons/grass7/logs/summary.html

I think it is because it is missing in this Makefile:

https://trac.osgeo.org/grass/browser/grass-addons/grass7/Makefile

I’m not sure if there is a documentation for this. We probably miss, how the create an addon.

On Thu, Sep 10, 2015 at 10:15 AM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

hi,

in https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector there is

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/v.in.gbif.log

but the manual can’t be find here:

https://grass.osgeo.org/grass70/manuals/addons/

and the pre-built addon can’t be found by g.extension in a winGRASS7.0.svn
session.

any idea?

I don’t have a clear idea how the system works but this addon is not even mentioned in

https://grass.osgeo.org/addons/grass7/logs/summary.html

I think it is because it is missing in this Makefile:

https://trac.osgeo.org/grass/browser/grass-addons/grass7/Makefile

I’m sorry, I meant this Makefile:

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

I’m not sure if there is a documentation for this. We probably miss, how the create an addon.

On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

...

but the manual can't be find here:

https://grass.osgeo.org/grass70/manuals/addons/

...

I think it is because it is missing in this Makefile:

...

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

yes, that's the reason (likewise for others).

I'm not sure if there is a documentation for this. We probably miss, how the
create an addon.

I have started a section here:
https://trac.osgeo.org/grass/wiki/Submitting#GRASSGISAddons

Markus

Markus Neteler wrote

On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras &lt;

wenzeslaus@

&gt; wrote:

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

...

but the manual can't be find here:

https://grass.osgeo.org/grass70/manuals/addons/

...

I think it is because it is missing in this Makefile:

...

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

yes, that's the reason (likewise for others).

oh, yes I remember darkly ;-), I'll add it.

thanks

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525p5223536.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Markus Neteler wrote

On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras &lt;

wenzeslaus@

&gt; wrote:

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

...

but the manual can't be find here:

https://grass.osgeo.org/grass70/manuals/addons/

...

I think it is because it is missing in this Makefile:

...

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

yes, that's the reason (likewise for others).

I'm not sure if there is a documentation for this. We probably miss, how
the
create an addon.

I have started a section here:
https://trac.osgeo.org/grass/wiki/Submitting#GRASSGISAddons

Markus
_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

http://lists.osgeo.org/mailman/listinfo/grass-dev

but in

https://grass.osgeo.org/addons/grass7/logs/summary.html

there is

vector/v.in.gns SUCCESS log

but v.in.gns isn't activated in

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile#L25

any idea?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525p5223541.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Thu, Sep 10, 2015 at 4:38 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

but in

https://grass.osgeo.org/addons/grass7/logs/summary.html

there is

vector/v.in.gns SUCCESS log

Yes, this is built on Martin L's Windows server AFAIK.

but v.in.gns isn't activated in

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile#L25

any idea?

Guess he just loops over *all* modules on his Windows machine while
the manual magic runs on the Linux server which respects the
Makefiles.

HTH,
Markus

Markus Neteler wrote

On Thu, Sep 10, 2015 at 4:38 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

but in

https://grass.osgeo.org/addons/grass7/logs/summary.html

there is

vector/v.in.gns SUCCESS log

Yes, this is built on Martin L's Windows server AFAIK.

but v.in.gns isn't activated in

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile#L25

any idea?

Guess he just loops over *all* modules on his Windows machine while
the manual magic runs on the Linux server which respects the
Makefiles.

HTH,
Markus
_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

http://lists.osgeo.org/mailman/listinfo/grass-dev

see https://grass.osgeo.org/grass70/manuals/addons/

v.in.gns is there , although not in the make file

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525p5223548.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On 10-09-15 16:29, Markus Neteler wrote:

On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

...

but the manual can't be find here:

https://grass.osgeo.org/grass70/manuals/addons/

...

I think it is because it is missing in this Makefile:

...

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

yes, that's the reason (likewise for others).

I'm not sure if there is a documentation for this. We probably miss, how the
create an addon.

I have started a section here:
https://trac.osgeo.org/grass/wiki/Submitting#GRASSGISAddons

A related / similar issue, I have added an add-on https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.biodiversity and added it to the parent Make file. I can't recall having done anything else then just uploading an add-on in the past, but it is not available through g.extension, nor does it show up in the online manual pages. From the links mentioned above, I am not clear what else I should do, or whether I did something wrong during upload?

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

On Fri, Sep 11, 2015 at 12:48 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:

A related / similar issue, I have added an add-on
https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.biodiversity
and added it to the parent Make file. I can't recall having done anything
else then just uploading an add-on in the past, but it is not available
through g.extension,

Yes it is!

GRASS 7.1.svn (eu_laea):~ > g.extension r.biodiversity
Fetching <r.biodiversity> from GRASS GIS Addons repository (be patient)...
Compiling...
Installing...
Updating addons metadata file...
WARNING: No addons metadata available. Addons metadata file not updated.
Installation of <r.biodiversity> successfully finished
GRASS 7.1.svn (eu_laea):~ >

Markus

PS: no idea what "WARNING: No addons metadata available. Addons
metadata file not updated." means

On 11-09-15 18:56, Markus Neteler wrote:

On Fri, Sep 11, 2015 at 12:48 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:

A related / similar issue, I have added an add-on
https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.biodiversity
and added it to the parent Make file. I can't recall having done anything
else then just uploading an add-on in the past, but it is not available
through g.extension,

Yes it is!

GRASS 7.1.svn (eu_laea):~ > g.extension r.biodiversity
Fetching <r.biodiversity> from GRASS GIS Addons repository (be patient)...
Compiling...
Installing...
Updating addons metadata file...
WARNING: No addons metadata available. Addons metadata file not updated.
Installation of <r.biodiversity> successfully finished
GRASS 7.1.svn (eu_laea):~ >

You are right :slight_smile: on the command line it worked. I had only checked using the g.extension GUI, where the extension is not shown

Markus

PS: no idea what "WARNING: No addons metadata available. Addons
metadata file not updated." means

No clue either, but maybe the reason it doesn't show in the g.extension GUI?

On Fri, Sep 11, 2015 at 1:13 PM, Paulo van Breugel <p.vanbreugel@gmail.com>
wrote:

PS: no idea what "WARNING: No addons metadata available. Addons
metadata file not updated." means

No clue either, but maybe the reason it doesn't show in the g.extension
GUI?

Well, I did pretty heavy changes in trunk's g.extension but I was not
getting this warning. It means that it can't find a particular XML on the
server. Does this happen for other addons or just r.biodiversity?

It seems not, I just tried to (re) install two others (r.bioclim and r.mess) and I did not get such warning

···

On Fri, Sep 11, 2015 at 1:13 PM, Paulo van Breugel <p.vanbreugel@gmail.com> wrote:

PS: no idea what “WARNING: No addons metadata available. Addons
metadata file not updated.” means

No clue either, but maybe the reason it doesn’t show in the g.extension GUI?

Well, I did pretty heavy changes in trunk’s g.extension but I was not getting this warning. It means that it can’t find a particular XML on the server. Does this happen for other addons or just r.biodiversity?

On Fri, Sep 11, 2015 at 1:37 PM, Paulo van Breugel <p.vanbreugel@gmail.com>
wrote:

On 11-09-15 19:31, Vaclav Petras wrote:

On Fri, Sep 11, 2015 at 1:13 PM, Paulo van Breugel <
<p.vanbreugel@gmail.com>p.vanbreugel@gmail.com> wrote:

PS: no idea what "WARNING: No addons metadata available. Addons
metadata file not updated." means

No clue either, but maybe the reason it doesn't show in the g.extension
GUI?

Well, I did pretty heavy changes in trunk's g.extension but I was not
getting this warning. It means that it can't find a particular XML on the
server. Does this happen for other addons or just r.biodiversity?

It seems not, I just tried to (re) install two others (r.bioclim and
r.mess) and I did not get such warning

I don't know if the server-side XMLs are generated for 71 or just 70 but
probably they are. Then I can also see that the addons page [1] data in the
bottom is some completely old one (Út srp 18 means Tuesday, August 18).
Since it is happening just for the new addon, it might be just because of
some delay in generating all server side things; I always have the feeling
that there is some delay, although it should be just 24 max.

[1] https://grass.osgeo.org/grass70/manuals/addons/

Just to add the note that those are add-ons that are already in the svn for some time, while r.biodiversity was just added. Not sure that makes a difference? Perhaps the XML file concerned is not renewed / updated?

···

On 11-09-15 19:37, Paulo van Breugel wrote:

On 11-09-15 19:31, Vaclav Petras wrote:

On Fri, Sep 11, 2015 at 1:13 PM, Paulo van Breugel <p.vanbreugel@gmail.com> wrote:

PS: no idea what “WARNING: No addons metadata available. Addons
metadata file not updated.” means

No clue either, but maybe the reason it doesn’t show in the g.extension GUI?

Well, I did pretty heavy changes in trunk’s g.extension but I was not getting this warning. It means that it can’t find a particular XML on the server. Does this happen for other addons or just r.biodiversity?

It seems not, I just tried to (re) install two others (r.bioclim and r.mess) and I did not get such warning

Does this happen for other addons or just r.biodiversity?

for newer addons recently added to svn

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525p5223869.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Yes, that is it. When using the address, things work as expected, the addon appears in the list and no error message. Would it be possible to make this work for v71 as well?

···

On 11-09-15 19:44, Vaclav Petras wrote:

On Fri, Sep 11, 2015 at 1:37 PM, Paulo van Breugel <p.vanbreugel@gmail.com> wrote:

On 11-09-15 19:31, Vaclav Petras wrote:

On Fri, Sep 11, 2015 at 1:13 PM, Paulo van Breugel <p.vanbreugel@gmail.com> wrote:

PS: no idea what “WARNING: No addons metadata available. Addons
metadata file not updated.” means

No clue either, but maybe the reason it doesn’t show in the g.extension GUI?

Well, I did pretty heavy changes in trunk’s g.extension but I was not getting this warning. It means that it can’t find a particular XML on the server. Does this happen for other addons or just r.biodiversity?

It seems not, I just tried to (re) install two others (r.bioclim and r.mess) and I did not get such warning

I don’t know if the server-side XMLs are generated for 71 or just 70 but probably they are.

https://svn.osgeo.org/grass/grass-addons/grass7/

Then I can also see that the addons page [1] data in the bottom is some completely old one (Út srp 18 means Tuesday, August 18). Since it is happening just for the new addon, it might be just because of some delay in generating all server side things; I always have the feeling that there is some delay, although it should be just 24 max.

[1] https://grass.osgeo.org/grass70/manuals/addons/

On Sep 11, 2015 11:17 PM, “Paulo van Breugel” <p.vanbreugel@gmail.com> wrote:

On 11-09-15 19:44, Vaclav Petras wrote:

I don’t know if the server-side XMLs are generated for 71 or just 70 but probably they are.

Yes, that is it. When using the https://svn.osgeo.org/grass/grass-addons/grass7/ address, things work as expected, the addon appears in the list and no error message. Would it be possible to make this work for v71 as well?

If someone tells me where, I can simply add a link on the server.

Markus

Hi,

2015-09-12 7:39 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

If someone tells me where, I can simply add a link on the server.

I don't know why, but addons logs were last time generated on 18/8.
Now I launched jobs manually and I didn't find any problem [1]. Also
r.biodiversity has metadata up-to-date now.

$ g.extension r.biodiversity
Fetching <r.biodiversity> from GRASS GIS Addons repository (be patient)...
Compiling...
Installing...
Updating addons metadata file...
Installation of <r.biodiversity> successfully finished

I will investigate why cronjobs are not launched automatically after svn commit.

Martin

[1] https://grass.osgeo.org/addons/grass7/logs/summary.html

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

On 12-09-15 13:44, Martin Landa wrote:

Hi,

2015-09-12 7:39 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

If someone tells me where, I can simply add a link on the server.

I don't know why, but addons logs were last time generated on 18/8.
Now I launched jobs manually and I didn't find any problem [1]. Also
r.biodiversity has metadata up-to-date now.

$ g.extension r.biodiversity
Fetching <r.biodiversity> from GRASS GIS Addons repository (be patient)...
Compiling...
Installing...
Updating addons metadata file...
Installation of <r.biodiversity> successfully finished

I will investigate why cronjobs are not launched automatically after svn commit.

Thanks for checking and follow up!

Martin

[1] https://grass.osgeo.org/addons/grass7/logs/summary.html