On Wed, 21 Aug 2019 11:47:57 +0000 Dmitry Bogatov <kact...@debian.org> wrote: > > [2019-08-12 19:31] Dmitry Bogatov <kact...@debian.org> > > [2019-03-13 17:17] Dmitry Bogatov <kact...@debian.org> > > > Package: bash > > > Version: 5.0-2 > > > Severity: wishlist > > > > > > Dear Maintainer, > > > > > > To contribute to efford of of making bash non-essential, I propose > > > following patch, that should resolve issue with login #620898 (in CC). > > > > > > Please, consider applying. > > > [...] > > > > Dear maintainer, hereby I inform you about my intention to make NMU > > upload with this patch into DELAYED/15 in week or so. > > Please be informed that I uploaded proposed change into DELAYED/15. You > are still welcome to provide feedback and, if necessary, cancel upload. > -- > Note, that I send and fetch email in batch, once in a few days. > Please, mention in body of your reply when you add or remove recepients. > >
Hi Dmitry, It is my belief that the change would be a severe regression when applied to deconfigure and I request that you cancel/update your NMU to avoid breaking system configuration during upgrades. (Note: I am not commenting on the entire change - only the deconfigure part). The issue is this: * deconfiguration of a package is normal during upgrades and commonly happens due to Breaks relations. * As bash is essential, it is required to function even when deconfigured (i.e. just unpacked), so the system will not be affected severely by this during the upgrade. * The proposed changes wipes local system configuration of who had the bash shell as default shell and cannot undo it on (re)configure. I would interpret this as loss of local system configuration (which is generally an RC bug). Thanks, ~Niels
