-
-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] g.extension fails to install #5139
Comments
If we look at the CI logs of grass-addons (and even locally), every single addons (maybe with some exceptions) show this, but doesn't make the build fail. |
It is failing in my case. Last time I installed addons was on 9th February and worked ok then.Now I cannot even reinstall the existing ones, failing on same issue. |
I have now deleted my local .grass8 folder and /usr/local/grass85, and then rebuilt GRASS using the latest (938b9ad) main. The problem persists. |
It seems to be searching for the documentation as md files, which for addons do not exist yet. And in dev, it changed during the past week or so. |
I runs for me locally, we tried to address it at least in a temporary way before the transition is complete. Try to use |
Thank you @petrasovaa , but it does not change things for me:
|
Any chance you could test #5141 ? |
Broken after Markdown docs transition. Markdown needs it special addons path just like the others, otherwise it goes to the system directory (and fails without permissions). See #5139.
It works fine. Thank you! |
Describe the bug
g.extension fails to install an extension. It reports an error seemingly attempting to read a non-existing file.
To reproduce
Note that "r.area.md" is not present in "/usr/local/grass85/docs/mkdocs/source" nor in the local .grass8 folder.
Expected behavior
Addon installs correctly in local (user space) directory for addons.
System description
Additional context
I have other 3 addons installed with a previous GRASS installation. These are correctly installed locally in .grass8:
The text was updated successfully, but these errors were encountered: