Hi,Such as?
I am facing ^M (\r) character in the .build output file using sbuild
on my system (Sid).
For instance:
$ file timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build: ASCII text, with
very long lines (307), with CRLF, CR, LF line terminators
It seems to me that there are some tools not using the conventional
unix EOL (\n only) in formating their output.
So I was curious if there are:There is a difference between printing something on stdout and actually
1. a policy on this (and more generally source file and/or output encoding),
2. a way to search using Debian Code Search for possible culprits,I doubt that.
just to get an idea.
I am facing ^M (\r) character in the .build output file using sbuild
on my system (Sid).
For instance:
$ file timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build: ASCII text, with
very long lines (307), with CRLF, CR, LF line terminators
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 33:48:49 |
Calls: | 6,707 |
Files: | 12,239 |
Messages: | 5,353,263 |