veyron_rialto: emerge: there are no binary packages to satisfy "chromeos-base/memd" |
|||
Issue descriptionThis error happens consistently when we submit https://crrev.com/c/1145740: veyron_rialto: emerge: there are no binary packages to satisfy "chromeos-base/memd" For instance, see https://luci-milo.appspot.com/buildbot/chromeos/veyron_rialto-paladin/8252 In the BuildPackages phase, I see this reference to memd: [ebuild R ] virtual/target-chromium-os-1-r102::chromiumos to /build/veyron_rialto/ USE="bluetooth cellular compupdates containers cras crash_reporting cros_disks debugd memd* mist network_time pam postscript power_management profile readahead shill syslog system_locales tpm trim_supported usbguard vpn watchdog -biod -bootchart -bootimage -buffet -cr50_onboard -cros_ec -cros_embedded -cups -dptf -eclog -fonts -fuzzer -gobi -hammerd -ime -intel_lpe -kvm_host -ml_service -modemfwd -mtd -nfc -peerd (-scanner) -systemd -touchview -tpm2 -wimax" INPUT_DEVICES="evdev" 0 KiB [ebuild R ] virtual/target-os-1.5-r1::chromeos to /build/veyron_rialto/ 0 KiB Not sure what the * means but it is suspicious. I have looked at the veyron_rialto private overlay and find no references to memd so I don't understand what's special about it. Can I get some help with this? Also, I am wondering if it would be OK to temporarily disable memd with a USE flag in overlay-variant-veyron-rialto-private/profiles/base/make.defaults, unless the fix for this is obvious.
,
Aug 7
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/overlay-variant-veyron-rialto-private/+/f29c96c3fc80b31271a95fb078aaf380f74d4759 commit f29c96c3fc80b31271a95fb078aaf380f74d4759 Author: Luigi Semenzato <semenzato@chromium.org> Date: Tue Aug 07 08:50:45 2018
,
Aug 15
,
Nov 14
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vapier@chromium.org
, Aug 6