Git linking issue in vagrant installation

[apwerk]

Hi folks, first of all thanks so much for open-sourcing your code, really appreciate it.

I'm having a spot of bother getting an instance set up using vagrant on EC2. Seems to be an issue following a git link. I followed the instructions provided and hit this snag on running vagrant up --provider=aws I have included the console log from the start of the actual mediacloud installation; find below.

default: Installing Media Cloud...
    default: Pulling submodules...
    default: Cloning into 'doc/api_2_0_spec/github-markdown-toc'...
    default: Submodule path 'doc/api_2_0_spec/github-markdown-toc': checked out 'a8a01a6913e00ecadcee0a88f6d487994dbfe3f6'
    default: Cloning into 'lib/MediaWords/Util/Mail/Message/Templates/email-templates'...
    default: Submodule path 'lib/MediaWords/Util/Mail/Message/Templates/email-templates': checked out 'c495f1fd31c3d9f468d77443e75c89208c276eae'
    default: fatal: Not a git repository: ../../../../../.git/modules/mediacloud/mediawords/languages/ca/snowball_stemmer
    default: Unable to find current revision in submodule path 'mediacloud/mediawords/languages/ca/snowball_stemmer'
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Are you aware of this issue/ have you encountered a similar one before? I'd be very grateful if someone could provide some guidance here.

Many thanks

[pypt]

Hey @apwerk!

Dunno, can't replicate your issue. Could you try refetching the modules:

git submodule update --init --recursive

or just re-cloning the repository?

Also, are you using Windows by any chance?