You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: /Stage[main]/Npm::Globals/Npm::Global[grunt-cli]/Exec[npm_global_grunt-cli]/returns: change from notrun to 0 failed: /usr/bin/npm install -g grunt-cli returned 1 instead of one of [0]
This error continues to occur after multiple tries at vagrant provision. Even if the command is run manually, it fails. It seems to be complaining about some /usr/local/bin/grunt existing before the install, and it says it doesn't want to delete that so it fails here. Since this is high up the dependency tree, it seems to be the cause of everything not working (like the wikidata not working and the webpage not being served).
The odd thing is that this isn't even in code from this repo - it's part of the actual npm module for puppet. Also, this is exactly the same as it is on drmf2016 and still this problem only occurs on drmf2017. EDIT: Apparently it does occur on drmf2016 as well but it didn't when the vagrant machine was originally provisioned (so the wikidata stuff generated fine).
@physikerwelt have you encountered something like this before?
The text was updated successfully, but these errors were encountered:
After looking at this further, it doesn't seem to be causing problems - it's only causing issues with mathoid apparently. It's still an issue, so I'll leave the issue open, but it doesn't seem to be a big deal.
This error continues to occur after multiple tries at vagrant provision. Even if the command is run manually, it fails. It seems to be complaining about some
/usr/local/bin/grunt
existing before the install, and it says it doesn't want to delete that so it fails here. Since this is high up the dependency tree, it seems to be the cause of everything not working (like the wikidata not working and the webpage not being served).The odd thing is that this isn't even in code from this repo - it's part of the actual npm module for puppet. Also, this is exactly the same as it is on drmf2016
and still this problem only occurs on drmf2017.EDIT: Apparently it does occur on drmf2016 as well but it didn't when the vagrant machine was originally provisioned (so the wikidata stuff generated fine).@physikerwelt have you encountered something like this before?
The text was updated successfully, but these errors were encountered: