Five files have CRLF formatting issues

I am using git-buildpackage to package Electrum for Debian. This creates branches in Git to hold the pristine tarball, the the upstream source, and the Debian specific directory. As part of the build process the system moves back and forth between these branches. Apparently, it really doesn’t like certain CRLF <-> LF issues in text files. I believe that what is happening is that these fields are being auto-substituted by Git push and pull, which is then causing the verification stage to fail because the files have changed unexpectedly. There are five specific text files that give it hard time:

electrum/gui/kivy/data/fonts/tron/License.txt electrum/gui/kivy/data/fonts/tron/Readme.txt electrum/gui/qml/fonts/PTMono.LICENSE electrum/ripemd.py electrum/wordlist/portuguese.txt

I don’t consider myself an expert on this subject, but I think that the attached five files are formatted in a way that would make Git happier. (I had to add .txt to the end of PTMono.LICENSE and ripemd.py to make GitHub happy. The original file name should be restored.)

License.txt portuguese.txt Readme.txt PTMono.LICENSE.txt ripemd.py.txt

[SomberNight]

For future reference, files with CRLF line endings can be listed like this (from https://stackoverflow.com/a/73969):

$ find . -not -type d -exec file "{}" ";" | grep CRLF
./electrum/wordlist/portuguese.txt: ASCII text, with CRLF line terminators
./electrum/gui/qml/fonts/PTMono.LICENSE: Unicode text, UTF-8 (with BOM) text, with CRLF line terminators
./electrum/gui/kivy/data/fonts/tron/License.txt: ASCII text, with CRLF, LF line terminators
./electrum/gui/kivy/data/fonts/tron/Readme.txt: ASCII text, with CRLF, LF line terminators
./electrum/ripemd.py: Python script, ASCII text executable, with CRLF line terminators

[SomberNight]

Thanks for the PR. I was looking into how to avoid this reoccurring in the future. See https://github.com/spesmilo/electrum/pull/8029