Sam Sirlin wrote: > FYI, in case there was any doubt, this annoying bug is also present in > a recent 6.0-STABLE (Sat Jan 14) on amd 64. > > CONFIG_SHELL=/bin/sh is a fix. > > Shouldn't the port be marked broken or reverted to a working copy in that case?