Re: [pcp] Heads up ... Debian stretch/sid unsuitable for PCP QA

[Ken McDonell <kenj@xxxxxxxxxxxxxxxx>]

On 09/05/16 23:33, Lukas Berk wrote:
> Hi,
>
> Ken McDonell <kenj@xxxxxxxxxxxxxxxx> writes:
> [...]
> > The way it has been since the Epoch:
> >
> > kenj@bozo:~$ ls eek
> > ls: cannot access eek: No such file or directory
> >
> > Debian stretch:
> >
> > kenj@vm07:~$ ls eek
> > ls: cannot access 'eek': No such file or directory
> >
> > Don't even think about how many QA tests the extra quotes break.  I
> > suspect this is not a Debian initiative, so in time we may see this
> > silliness percolate down to other distros.
> Is there an ls quoting-style we can specify to correct this?  I don't
> have a local sid install handy to test this, but something like `ls
> --quoting-sytle=literal` might do it (or -N aiui)?  Perhaps we can alias
> this in a common.* file?
>
> or maybe one of...
>    - âliteralâ
>    - âshellâ
>    - âshell-alwaysâ
>    - âcâ
>    - âc-maybeâ
>    - âescapeâ
>    - âlocaleâ
>    - âclocaleâ
>
> would work if not literal?
Thanks for the pointers Lukas.

Unfortunately none of the above work.

Debian has reverted the coreutils brain damage that lead to this problem 
in normal ls output (with special characters in the filename), see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810295 ... and I'd 
expect other distros to follow suit [hint], rather than expect people to 
retrofit $QUOTING_STYLE or --quoting-sytle= to their scripts to maintain 
the status quo.
However, they have not reverted the accompanying quoting in the error 
messages which is apparently always present (even if the filename 
contains no special characters) ... I've opened a Debian bug for this.