diff options
author | Tony Ambardar <itugrok@yahoo.com> | 2018-03-02 19:32:24 -0800 |
---|---|---|
committer | Jo-Philipp Wich <jo@mein.io> | 2018-09-24 18:58:00 +0200 |
commit | 4097ab6a975902b170dd7f7ac6c8025e5f32ef8d (patch) | |
tree | ce94d3b301e61110bf965178c718d88645fa7868 /tools | |
parent | d3b43f49acb38cbe364da8735c9617427edd3d81 (diff) | |
download | upstream-4097ab6a975902b170dd7f7ac6c8025e5f32ef8d.tar.gz upstream-4097ab6a975902b170dd7f7ac6c8025e5f32ef8d.tar.bz2 upstream-4097ab6a975902b170dd7f7ac6c8025e5f32ef8d.zip |
base-files: fix postinstall uci-defaults removal
Commit 7f694582 introduced a bug where default_postinst() often fails to
remove a uci-defaults script after application, leaving it to run again
after a reboot.
(Note: commit 7f694582 also introduced FS#1021, now fixed by 73c745f6)
The subtle problem arises from the shell logical chain:
[ -f "$i" ] && . "$i" && rm -f "$i"
Most uci-defaults scripts contain a terminal 'exit 0' statement which,
when sourced, results in the logic chain exiting before executing 'rm -f'.
This was observed while testing upgrades of 'luci-app-sqm'.
The solution is to wrap the shell sourcing in a subshell relative to the
command 'rm -f':
( [ -f "$i" ] && . "$i" ) && rm -f "$i"
Revert to using 'grep' to prefilter the list of entries from the control
file, which yields the full path of uci-defaults scripts. This allows
keeping the existence check, directory change and script sourcing inside
the subshell, with the script removal correctly outside.
This approach avoids adding a second subshell only around the "." (source)
command. The change also preserves the fix FS#1021, since the full path is
used to source the script, which is POSIX-portable irrespective of PATH
variable or reference to the CWD.
Run Tested on: LEDE 17.01.4 running ar71xx, while tracing installation of
package luci-app-sqm with its associated /etc/uci-defaults/luci-sqm file.
Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions