On Sat, Mar 18, 2023 at 08:45:37PM +0100, Patrice Duroux wrote: > Hi, > > 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. Such as? That file(1) output, as often happens with file(1) output, is not very useful or trustworthy by itself.
> So I was curious if there are: > 1. a policy on this (and more generally source file and/or output encoding), There is a difference between printing something on stdout and actually writing files. Printing should of course be in the user locale while files are different, especially non-text ones. > 2. a way to search using Debian Code Search for possible culprits, > just to get an idea. I doubt that.