Because of a bunch of PCP changes made while I was away, _half_ of my QA
machines had regressed to the point where I was unable to build or
install PCP packages. That sucks big time, but is not the point of this
email.
I've spent a week trying (and not yet succeeding) to recover.
One of the changes was to upgrade a couple of my machines from an older
Debian release (there were just too many package prereqs that where not
available ... this is a another gripe I have, but not the point of this
email either) ... so I upgraded to stretch/sid as I already had good
coverage of the other current Debian releases.
Yes I know stretch/sid is not yet released, but what moron would think
this change is a good idea?
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.
But, wait there is more ... valgrind does not work at all in Debian stretch.
The QA report is going to be pretty sad when I send it in a day or so.
|