Closed vosykapavel closed 5 years ago
That's a really weird set of warnings, starting with
/usr/sbin/locale-gen: line 177: 1606 Floating point exception
More interesting though are all the warnings about '\r not found', like
/vagrant/inc/install-packages.sh: line 6: $'\r': command not found
This looks like a Unix->DOS/Windows line ending conversion problem. Looks as if whatever Git client you used performed line ending conversion, and the bash shell does not like DOS line endings at all.
That leads to package installation failure when executing the install.sh script, and following that lots of errors due to missing packages that did not get installed.
Unfortunately I do not have access to any windows machines for testing right now, the one I still had died on christmas ...
Got my windows test machine repaired today. The problem is indeed in the line endings only.
I installed Git with the "Checkout as-is, commit as-is" setting for line endings, and ran a full "vagarnt up" test run with that.
This are the symptoms of the CR to CRLF conversion done by git on Windows.
Maybe a ".gitattributes" with these entries helps:
Thank you for your help. The answer is probably correct. But sorry I can't test it and I don't need maposmatic now.
But I think we can close this as solved. Thank both of you.
(And I shame for my late answer)
I was thinking about my own private instace of maposmatic. So I tried "vagrant up", but than I get lot of "command not found" and finally "No such file or directoryd /etc/ImageMagick-6/policy.xml".
If you see any easy mistake, please help me. If it is more complicated, you can delete this issue. Thanks.