New issue
Advanced search Search tips

Issue 923431 link

Starred by 2 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

chromeos-bsp-sarien-private: cros-workon ebuild against itself randomly breaks

Project Member Reported by tbegin@chromium.org, Jan 18 (4 days ago)

Issue description

Failing Builder:
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?id=3373284

fatal: reference is not a tree: 0a4f6bff3006e942278d8f1f57b58727cf6d3fb4
ERROR: chromeos-base/chromeos-config-bsp-sarien-0.0.1-r7::sarien failed (unpack phase):

Related to https://bugs.chromium.org/p/chromium/issues/detail?id=854633
 

Comment 1 by tbegin@chromium.org, Jan 18 (4 days ago)

Cc: cros-proj-wilco@google.com nathan.d...@intel.com

Comment 2 by vapier@chromium.org, Jan 18 (4 days ago)

Labels: OS-Chrome
Summary: chromeos-bsp-sarien-private: cros-workon ebuild against itself randomly breaks (was: Build failure - Sarien)
ebuilds must not be workon relative to themselves.  that is known to be broken and at this point, is unsupported.  you'll need to convert the bsp ebuild away from being cros-workon.

Comment 3 by tbegin@chromium.org, Jan 18 (4 days ago)

Sounds good, thanks for taking a look at it. Does this mean that any ebuild using cros-workon and a local files directory should be changed to remove cros-workon?
Project Member

Comment 5 by bugdroid1@chromium.org, Jan 19 (3 days ago)

Comment 6 by vapier@chromium.org, Jan 19 (3 days ago)

> Does this mean that any ebuild using cros-workon and a local files directory should be changed to remove cros-workon

the issue isn't that the ebuild has a files/ dir, it's that the ebuild points to the same repo as where that ebuild lives

Sign in to add a comment