Get list of addons via g.extension with -tl flag, which means operate on toolboxes instead of single modules (experimental) doesn't work

[tmszi]

Describe the bug Get list of addons g.extension -tl, with -t flag which means operate on toolboxes instead of single modules (experimental) doesn't work.

To Reproduce Steps to reproduce the behavior:

1. Get list of addons g.extension -tl with -t flag
2. See error

GRASS nc_basic_spm_grass7/PERMANENT:~ > g.extension -tl
List of available extensions (toolboxes):
ERROR: Download file from
       <https://grass.osgeo.org/addons/grass8/toolboxes.xml>, failed. File
       is not on the server or check your internet connection.

Expected behavior Get list of addon g.extension -tl, with -t flag should be work without error message.

System description:

• GRASS GIS version main, releasebranch_7_8, releasebranch_8_0

Additional context toolboxes.xml file doesn't exists (for G7/G8) on our osgeo server. Much more info about addons toolboxes is here. Seems this file isn't generated by any script, and before we merged this PR I saw this file in this url (for G7). I found a similar file here, but I don't think that match the one which existed on the server or is actual. Do @neteler have more info about it, please?

[veroandreo]

What would be the difference/advantage of using -t or not, do you know? Afaik, if one runs only g.extension i.sentinel, all modules within i.sentinel will be installed anyway, right?

[tmszi]

What would be the difference/advantage of using -t or not, do you know? Afaik, if one runs only g.extension i.sentinel, all modules within i.sentinel will be installed anyway, right?

I reformulated the issue title and text.

If I understand it correctly, it is used to create groups = toolbox (with toolbox code) that include only specified addons, for easy installation/organization same as described here.

The toolbox installation should look like this g.extension -t extension=TOOLBOX_CODE.

[neteler]

Since there is no PR yet, may we bump this to the milestone 8.0.1? Let's go and release 8.0.0.

[wenzeslaus]

-t is marked as experimental, so marking this as 8.2.0 is fine.

[sraul1]

Has this had resolution yet? I'm running 8.2 and still am experiencing it. Otherwise, is there a workaround?