On 4/6/19 10:40 PM, Frank Scheiner wrote:
Ok, looks like there's a "local" keyword used outside of a function in a
partman startup(?) file:
```
Apr 6 20:22:36 partman: No matching physical volumes found
Apr 6 20:22:36 partman: Reading all physical volumes. This may take
a while...
Apr 6 20:22:36 main-menu[209]: (process:4259):
/lib/partman/init.d/26zfs-devices: local: line 19: not in a function
Apr 6 20:22:36 main-menu[209]: INFO: Menu item 'partman-base' succeeded
but requested to be left unconfigured.
```
But that file ([1]) is 5 years old, so maybe the way the shell -
actually `busybox` - handles (or ignored) a "local" keyword outside of a
function has changed?
The installer team just uploaded busybox 1.30 last month [1] which introduced
at least one serious bug [2]. Might be that busybox 1.30 broke more stuff.
Adrian
[1] https://packages.qa.debian.org/b/busybox/news/20190301T211946Z.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925979