On Fri, Jun 21, 2024 at 09:43:52 -0700, Mike Castle wrote: > On Fri, Jun 21, 2024 at 4:57 AM Greg Wooledge <g...@wooledge.org> wrote: > > That's why I find it frustrating when someone claims that this bug is > > so severe that Debian has to *change their policy* without even describing > > how this bug is affecting them in real life. > > I did not feel like the OP was saying the bug was that bad and the > policy needed to change, but as a starting point to ask why it is > still the policy after 27 years.
Are you unaware that it *changed*? Here's a quote from <https://wiki.debian.org/Shell> which was the first place I could find it: In all releases up to and including DebianLenny, Bash was the default non-interactive shell. Beginning with DebianSqueeze, Debian uses Dash (the Debian Almquist shell) as the target of the /bin/sh symlink. Debian made a *conscious choice* to switch /bin/sh from bash to dash. The OP of this thread is requesting that Debian should reverse this and change *back* to bash, because of one bug, which affects a very small number of scripts. Furthermore: From DebianSqueeze to DebianBullseye, it was possible to select Bash as the target of the /bin/sh symlink by running dpkg-reconfigure dash. However, as of DebianBookworm, this is no longer supported. So, the OP is not only asking for a reversion of the policy decision that was made, but for a reinvestment of the time and resources that would be required to support this new-but-really-old policy. The resources to support /bin/sh -> bash have already been discontinued.
