Hi!
Thus asking are Windows CRLF necessary in the new mysql-test/main/mysql-interactive.result test?
The .result files are compared verbatim against the test output to check for test passing or failing. So you can easily check this by removing the CR bytes and run the main.mysql-interactive to see if it still pases.
Firstly, I cannot use 'patch' to remove Windows line endings. I can't even use it to modify that file due to git attributes or patch itself mangling on them (e.g. https://salsa.debian.org/otto/mariadb-server/-/jobs/7569516). I didn't manage to fully debug which step exactly cleans them away and from what file. Secondly, I won'd have a Windows machine to test on if the test still works. On my Linux machine the test will surely pass if I remove those endings. My question was here for upstream if you know if that test was intentionally introduced with Windows line endings or if it just happened?
While importing 11.4.6 into Debian I ran into issues with git and quilt failing to convert text files properly between Unix and Windows line endings.
What issues? Why do you need to convert text files, why not simply keep the files as they are, regardless of CRLF or any other special byte sequences?
I need to patch this file in the Debian packaging. I could alternatively also just disable this new test, so it is not a showstopper.