[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#994275: Draft resolution for reverting changes in debianutils


On Wed, 13 Oct 2021, David Bremner wrote:
> >    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. I don't think people are really entitled to
> expect which(1) to never print to stderr. Even when debian-policy
> recommended 'which' it apparently recommended redirecting stderr.
> I also don't see failures of autopkgtests as directly impacting users in
> the same way a failure to build or a failure to install does.

There have been other reports of failures due to the message on stderr,
autopkgtest is not the only one (wookey mentionned a build failure).

In any case, a message saying that which is deprecated when in fact
`which` will stay around (but maintained in another packages) is not

> 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 it does.

  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog <hertzog@debian.org>
  ⢿⡄⠘⠷⠚⠋    The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄⠀⠀⠀⠀   Debian Long Term Support: https://deb.li/LTS

Reply to: