Closed mid-kid closed 2 years ago
I guess the fix would be to disable auto-CRLF in our CI script, as well as re-generating all affected tarballs.
Regenerating tarballs after this long is kinda evil since most packaging scripts rely on it staying the same for verification. And failing tests is super minor. But if you want a list, it's just 0.5.1 and 0.5.2.
Also why not fix the gitattributes?
Because it appears to work fine on Windows installs despite using CRLF, if I am to believe our CI.
As for regenerating the tarballs, you're right.
I think e35585960c5b814a00e216fdc6f7fa1503134250 and 830df360ae7dd5f045d177c5bc57746a9a6d337e resolved this too. Edit: Nope, the reported problems still occur with rgbds-0.6.0-rc2.tar.gz.
Steps to reproduce:
Errors appear, like:
How to fix in repo:
Though it probably should be fixed in gitattributes.