I can confirm (using Ubuntu 16.04 latest) LICENSE file has Windows line endings (which is OK if it was checked-out on Windows) both frameworks/locale/ja_JP/metadata.properties and frameworks/tests/basicTests/spark/views/SortTests.mxml files has invalid contents (encoding)
I would suggest to create .gitattributes (similar to .gitignore) in case line endings might be an issue not sure why UTF-8 files were damaged, there are OK after git clone On Tue, Nov 14, 2017 at 2:50 PM, Alex Harui <aha...@adobe.com.invalid> wrote: > > > On 11/13/17, 11:34 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > >Hi, > > > >> The binaries are not created by first creating the source package, > >> unpacking it and compiling it. You were a Flex SDK RM at least once, > >>did > >> you not understand what you were signing? > > > >Every time I made the release I made it from the source on my local > >machine on a clean tagged branch. I understood 100% what I was signing > >(for instance see [1][2]) and write most of the scripts to do help make > >builds [3][4] and contributed a lot to the wiki on the instructions on > >how the build the SDK. [4] I was a Flex SDK RM 1/2 dozen times probably > >more and more than a dozen releases in this project. So I have no idea > >why you would say “did you not understand what you were signing?” and IMO > >that was uncalled for. > > Because it sounded like you didn't understand how the build scripts worked. > > > >> I'm not sure there is a workaround to convert those files back > >> to UTF8 or not. > > > >Even if you did find a way it would likely change the md5s and make the > >signatures invalid as converting to UTF8 modifies the file by adding a > >byte order mark at the front of the file. > > A workaround of converting the files back to UTF8 before compiling would > have nothing to do with md5s and sigs. > > -Alex > > -- WBR Maxim aka solomax
