Issue metadata
Sign in to add a comment
|
Unsatisfied sys-boot/chromeos-mrc dependency |
||||||||||||||||||||
Issue descriptionFrom https://groups.google.com/a/chromium.org/d/topic/chromium-os-dev/S6A0-Qovows/discussion: --- System: Debian Sid/unstable Kernel: 4.12 CPU: x86_64 './build_packages --board=samus' produces this error: emerge: there are no ebuilds to satisfy "sys-boot/chromeos-mrc" for /build/samus/. (dependency required by "sys-boot/coreboot-0.0.1-r2275::chromiumos[intel_mrc]" [ebuild]) (dependency required by "sys-boot/chromeos-bootimage-0.0.3-r7::chromiumos" [ebuild]) (dependency required by "virtual/chromeos-firmware-1-r2::chromiumos[bootimage]" [ebuild]) (dependency required by "virtual/target-chromium-os-1-r76::chromiumos" [ebuild]) (dependency required by "virtual/target-os-1-r3::chromiumos" [ebuild]) (dependency required by "virtual/target-os" [argument]) ERROR : emerge detected broken ebuilds. See error message above. --- It looks to me like https://chromium-review.googlesource.com/543918 added +intel_mrc to IUSE in sys-boot/coreboot/coreboot-9999.ebuild, making it have sys-boot/chromeos-mrc in DEPEND by default for x86 and amd64. sys-boot/chromeos-mrc lives in chromeos-partner-overlay, so this seems like it breaks builds based on checkouts of the publicly-available source code. Do we not have a builder that tests this?
,
Oct 4 2017
,
Aug 8
Is there any progress on this bug? It is still affecting current public builds on samus.
,
Aug 8
Simon, do you know the answer to Mike's question in #1?
,
Aug 16
Re #4, yes I think Mike is likely correct. The firmware ebuilds rely on things that are private, so moving the USE flags over to private seems like a good idea.
,
Aug 16
(BTW I am back from 2 weeks away) |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by vapier@chromium.org
, Oct 3 2017