Seems like chrome started depending on bluez without actually listing it in the ebuild, as of this:

https://codereview.chromium.org/2166143002

(i.e., a long time ago)

We don't really need Chrome (and we are purposely disabling USE=bluetooth in the testbed-ap profile), so maybe we need to go whole-hog and move panther and stumpy testbed-ap to the embedded profile, just like we do for whirlwind.

This would have other ramifications, but so far, I think we're dealing with those ramifications for whirlwind.

~/trunk/src/private-overlays/overlay-stumpy-private $ git diff
diff --git a/profiles/testbed-ap/parent b/profiles/testbed-ap/parent
index 00222c6..54d59b5 100644
--- a/profiles/testbed-ap/parent
+++ b/profiles/testbed-ap/parent
@@ -1,2 +1,3 @@
 ../base
+chromiumos:features/embedded
 chromeos:features/testbed-ap

then setup the board:
 ./setup_board --board=stumpy --profile=testbed-ap --force

Failed with:

ERROR   :  build_image_util.sh:104:check_blacklist(), called: die 'Blacklisted packages found: dev-lang/python.' 
ERROR   : 
ERROR   : Error was:
ERROR   :   Blacklisted packages found: dev-lang/python.

Since whirlwind doesn't hit this issue, is that like due "../base" needing to be replaced with "chromiumos:default/linux/arm/10.0/chromeos" (or rather the equivalent for amd64)?

Sorry - a bit too terse in comment #3: build_image failed with the given error. Here my normal "build everything" command line:

for B in panther stumpy ; do nice ./build_packages --board=$B --withautotest; if [ $? -ne 0 ] ; then echo "===== FAILED : $(date) : ./build_packages --board=$B =====" >> FAILED.out; else nice ./build_image test --board=$B --noenable_rootfs_verification; if [ $? -ne 0 ] ; then echo "===== FAILED : $(date) : ./build_image test --board=$B =====" >> FAILED.out; fi; fi; done

Hrm..I suspect I need to drop the "--withautotest" so it doesn't automagically pull in python. Will try that.

vapier provided the right magic. \o/

~/trunk/src/overlays/overlay-stumpy $ cat scripts/board_specific_setup.sh 
#!/bin/bash
# Copyright 2018 The Chromium OS Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.

if portageq-${FLAGS_board} envvar USE | grep -E '(^| )wifi_testbed_ap( |$)'; then
    #  crbug.com/809792  : python is needed on testbed-ap profiles.
    skip_blacklist_check=1
fi


flashing to USB and testing next.

This boots on stumpy but it seems to still have chrome and the UI login. :(

Three things I want to do related to this:
1) test this build anyway on real stump "-router" in the lab

2) figure out how to remove chrome from the build.  Will have to look at fizz-accelerator build.

3) post CLs, cherry-pick those to release-R65-10323.B, retest with official build


4) move testbed-ap stuff to public overlay (or first clone it there since that's were "chromium:features/embedded" lives)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/07fb6f3d6bd6ff287fd0f26232b50ef128fc03bc

commit 07fb6f3d6bd6ff287fd0f26232b50ef128fc03bc
Author: Grant Grundler <grundler@chromium.org>
Date: Fri Mar 02 03:13:35 2018

chromeos-init: start frecon if also embedded

When USE=cros_embedded,  not all upstart scripts are installed.

If USE=frecon is set, we need boot-splash.conf installed to
start frecon. Thus boot-splash.conf needs to be installed
when both flags are specified.

BUG= chromium:809792 
TEST=./setup_board --board=stumpy --profile=testbed-ap --force
	./build_packages --board=stumpy
	./build_image test --board=stumpy --noenable_rootfs_verification

	cros flash stumpy.lab
	# verify monitor shows a console

Change-Id: If9a831409c7f76110714d7fe29c3b2bc10d49455
Reviewed-on: https://chromium-review.googlesource.com/938641
Commit-Ready: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/07fb6f3d6bd6ff287fd0f26232b50ef128fc03bc/chromeos-base/chromeos-init/chromeos-init-9999.ebuild

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-stumpy-private/+/038d66e65c0707d3dfcf17ff75d3f00f46ba8ba7

commit 038d66e65c0707d3dfcf17ff75d3f00f46ba8ba7
Author: Grant Grundler <grundler@chromium.org>
Date: Sat Mar 03 06:22:29 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-stumpy-private/+/0c4f53309ff48a64e31ea3f3a0fb41fc2405e406

commit 0c4f53309ff48a64e31ea3f3a0fb41fc2405e406
Author: Grant Grundler <grundler@chromium.org>
Date: Tue Mar 06 22:21:02 2018

the follow CL allows one to build on top of R65 branch, the last version to officially support stumpy:
   https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/927228

However, wifi_matfunc tests failed entirely to connect the DUT with the stumpy. I didn't pursue debugging this since stumpy machines are unsupported HW and we have to replace all stumpy devices in any case.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/31f5f56c0194d8025ced5dd8283a0023be8d75ac

commit 31f5f56c0194d8025ced5dd8283a0023be8d75ac
Author: Grant Grundler <grundler@chromium.org>
Date: Fri May 11 06:18:06 2018

init: start frecon even if no assets

In "embedded" configurations, we don't have any chrome assets
and that makes frecon very unhappy (exits) once it finds out
the "*.png" doesn't exist.

This change also allows board specific overlays to overide the
"ASSETLESS_ARG" parameters to frecon.

BUG= chromium:809792 
TEST=./build_packages --board=kefka
     ./build_image test --board=kefka --noenable_rootfs_verification
     cros flash kefka.lab
     # verify console works in dev mode.

ORIG_TEST=./setup_board --board=stumpy --profile=testbed-ap --force
     ./build_packages --board=stumpy
     ./build_image test --board=stumpy --noenable_rootfs_verification
     cros flash stumpy.lab
     # verify monitor shows a console

Change-Id: Id9bf0563bc3564ee12ef6f354cf5fb78c4181d52
Reviewed-on: https://chromium-review.googlesource.com/939501
Commit-Ready: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Brian Norris <briannorris@chromium.org>

[modify] https://crrev.com/31f5f56c0194d8025ced5dd8283a0023be8d75ac/init/upstart/boot-splash.conf