Package: dash
Version: 0.5.12-9
Followup-For: Bug #1007263
X-Debbugs-Cc: rra@debian.org

This topic came up in Policy bug #1074014. It sounds like there is a plan
to document the transition in the release notes, but, going forward, the mechanism to change the shell underlying /bin/sh sounds like it changed
as part of the current work and users should now do a local diversion of /bin/sh and create a new symlink.

I think it would be a good idea to add user-facing documentation explaining
how to do that, and I wasn't able to find any in dash (or bash, which is
the most likely but not the only target shell). It probably should be in
more than just NEWS.Debian, as well, since this will continue to be
something some users need to do going forward, such as to handle local #!/bin/sh scripts that have bashisms.

Maybe the README.Debian file of this package would be an appropriate place?


-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental') Architecture: amd64 (x86_64)

Kernel: Linux 6.10.3-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dash depends on:
ii debianutils 5.20
ii libc6 2.39-6

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: true

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)