Changed the title to better reflect the situation.

This can be rectified by overwriting TERM value before starting cros_sdk:

TERM=screen cros_sdk

The  https://chromium-review.googlesource.com/969413  which supposedly fixed this problem in fact did not fix it for chroot, the issue is still there.

When ncruses is emerged inside chroot, the -r99 version of the ebuild is used, not the -r6 modified by the above patch.

ping... any chance of fixing this soon, or maybe providing some insight wrt two different ebuilds for ncurses?

I think I tried `sudo emerge =sys-libs/ncurses-5.9-r6` at one point, don't remember if that's what fixed it or not.

Ideally it would auto-update to r6.  Not sure how to make that happen.

a plain emerge prob won't do it, but build_packages should.  the bots are picking it up fine.

current samus-paladin & samus-release show in their build_image stage:
[binary  N     ] sys-libs/ncurses-5.9-r6:0/5::portage-stable to /mnt/host/source/src/build/images/samus/R68-10633.0.0/rootfs/ USE="minimal static-libs -ada -cxx -debug -doc -gpm -profile -tinfo -trace -unicode" ABI_X86="(64) -32 (-x32)" 0 KiB
[binary  N     ] sys-libs/ncurses-5.9-r99:5::portage-stable to /mnt/host/source/src/build/images/samus/R68-10633.0.0/rootfs/ USE="static-libs -ada -cxx -gpm -tinfo -unicode" ABI_X86="(64) -32 (-x32)" 0 KiB

Vadim needs to emerge it for his chroot... is there a step similar to build_packages that will do it?

why can't you run build_packages?

the chroot versions are irrelevant here

It actually looks that xterm-256color is now handled fine inside chroot, it's screen.xterm-256color which causes problems.

But FWIW I ran 'bulid_packages --board=bob' and did not see ncurses emerged at all, at least it does not show up in /build/bob/tmp/portage/logs.

screen.xterm-256color is what TERM is set to when entering chroot from a screen session on Rodete of Ubuntu 16.04, it messes up many functions inside chroot.


this patch is trying to add another string to the list https://chromium-review.googlesource.com/#/c/chromiumos/overlays/portage-stable/+/1064481 

I still don't understand though how to emerge this for chroot environment, there is another ebuild in the same directory (ncurses-5.9-r99.ebuild) which takes over when 'sudo emerge ncurses' is run.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/cc80592cfeef01af301ebc7e293d18e64777cbcd

commit cc80592cfeef01af301ebc7e293d18e64777cbcd
Author: Vadim Bendebury <vbendeb@chromium.org>
Date: Wed Jul 18 04:53:25 2018

sys-libs/ncurses: add screen.xterm-256colors

TERM is set to screen.xterm-256colors when in Rodete, let's make sure
this terminal type is recognized inside chroot.

BUG=chromium:810893
TEST=none

Change-Id: I70f152294584a658008b00e7618de2a680301014
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1064481
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[rename] https://crrev.com/cc80592cfeef01af301ebc7e293d18e64777cbcd/sys-libs/ncurses/ncurses-5.9-r7.ebuild