This is new, but it is identical to 1.8.8 which has been ~arch for ages, except for adding a fix to a bash call which breaks with the shellshock fixes. The current stable version is broken and needs to be removed.
With cfg-update 1.8.7 I'm getting: > * invalid key... try again: bash: readkey: command not found repeatedly, like over and over... 1.8.9 or newer is needed to fix this bug I believe. https://github.com/rich0/cfg-update/commit/b87b46465a291be8f4508826a5610d68decb4a9a#diff-e3d611238f15ce823a8ad932c7172765 ^ The comment says it all: > After security-updates to bash it's no longer possible to store > functions in envirinment. This patch replaces use of bash to read a > single key from tty with the perl-module Term::ReadKey --- (In reply to Richard Freeman from comment #0) > This is new, but it is identical to 1.8.8 which has been ~arch for ages, > except for adding a fix to a bash call which breaks with the shellshock > fixes. The current stable version is broken and needs to be removed. Makes sense / Yes, I agree. This is probably related to the fixes for shellshock. In the meantime I'm adding: <app-portage/cfg-update-1.8.9 to my /etc/portage/package.mask
(In reply to Sarah White from comment #1) > With cfg-update 1.8.7 I'm getting: > > > * invalid key... try again: bash: readkey: command not found > > repeatedly, like over and over... > > 1.8.9 or newer is needed to fix this bug I believe. ((...snip...)) Tested in the past couple hours: Confirmed working. The 1.8.9 version fixes this issue, and appears to be just as stable as the older versions which used the older shellshock-vulnerable routine.
Marked x86 as stable - current stable was broken anyway and I did get a test report.
ppc stable. Closing.
