Hi, On Wed, 14 Aug 2024, at 09:52, Helmut Grohne wrote: >> This update to dash moves /bin/sh to /usr/bin/sh, but your system has a >> local
> As Thorsten pointed out, using an old dash to configure bash as the > shell results in a diversion owned by bash and it is possible to keep > this diversion. Such a diversion is not called local. How about dropping > the word "local"? Sure. >> diversion of /bin/sh. Since there is no new diversion of the new location > > I am wondering whether "new location" may confuse users into believing > that /bin/sh would now be unavailable. In my wording, I tried to > emphasize that the change in location is only a detail of how dpkg looks > at it. I don’t think this needs to be emphasised, but in any case the old wording was a bit too technical. I’ll try to think of a better one to capture this meaning. >> /usr/bin/sh, this local diversion will no longer work, making dash the >> default shell. >> . >> To prevent this message from appearing again, remove the local diversion of >> /bin/sh. > > This is factually wrong. With the proposed implementation, the message > will only be displayed when upgrading from an aliased dash to a moved > dash. In later upgrades, it will not be displayed. Also dpkg-reconfigure > will not display it. I don't think there is a way to see it twice. You’re right, this message will only be displayed once. >> To continue using the alternative default shell of your choice, create >> another >> diversion for /usr/bin/sh. > > Thanks for trying to improve the wording, but I don't think this quite > cuts it yet. -- Cheers, Andrej
