I gave this a test with Ubuntu 14.04, 16.04, 18.04, 20.04, LTS releases,
and Debian 10 and Debian 11, in lxd.
Ubuntus before 20.04 all showed the described behaviour.
Ubuntu 20.04 LTS worked the same as both Debian releases.
The versions of dash in each release make this make some sense:
$ for
** Changed in: dash (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1516300
Title:
dash command variable assignments remain in the she
This might represent a behaviour that's still unwanted in our dash
packages, especially if Debian's dash packages differ. So I'm setting it
back to 'new' in the hopes that someone from Foundations can give it a
look and decide if this deserves an SRU.
It certainly surprises me.
Thanks
** Changed
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1516300
Title:
dash command variable assignments remain in
4 matches
Mail list logo