On 2021-10-13 19:37 -0300, David Bremner wrote: > Sean Whitton <spwhit...@spwhitton.name> writes:
> > The which(1) program must not print any deprecation warnings. > > I remain to be convinced on this point. If I understand the issue > correctly the problem is with autopkgtests failing because they were not > expecting output on stderr. It's not just that. Builds fail too. tensorflow now FTBFS in unstable because of this change, and the way bazel deals (or fails to deal) with it. I gave details further up the thread. > I understand that people find the message annoying, and perhaps not that > useful, but I don't think that rises the level justifying overriding a > maintainer. I think causing build failures is enough reason to say this. I don't suppose that mine is the only one. Yes those builds are buggy and should not do this, and we should make efforts to find out why bazel (or possibly the build scripts it is operating on) is/are so crappy, but for now I agree that reverting this is the right thing to do. We have time to do this transition properly and quietly in the background, without causing random breakage. A message about a binary moving from one package to another does not need to be printed on every usage of that binary. Indeed it is actively unhelpful to do so. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature
