Lakitu builders broken due to circular dependency introduced by util-linux |
|||||
Issue descriptionlakitu-paladin and lakitu-release have both been failing at the BuildPackages stage, due to the following error: 14:09:56: INFO: RunCommand: /b/cbuild/internal_master/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpZKlDw7' -- /mnt/host/source/chromite/bin/cros_extract_deps --board lakitu '--format=deps' virtual/target-os virtual/target-os-dev virtual/target-os-test virtual/target-os-factory virtual/target-os-factory-shim chromeos-base/autotest-all --output-path /tmp/tmp5ilxjT in /b/cbuild/internal_master 14:10:09: ERROR: return code: 1; command: /b/cbuild/internal_master/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpZKlDw7' -- /mnt/host/source/chromite/bin/cros_extract_deps --board lakitu '--format=deps' virtual/target-os virtual/target-os-dev virtual/target-os-test virtual/target-os-factory virtual/target-os-factory-shim chromeos-base/autotest-all --output-path /tmp/tmp5ilxjT * Error: circular dependencies: (sys-apps/util-linux-2.27.1:0/0::portage-stable, ebuild scheduled for merge to '/build/lakitu/') depends on (sys-apps/systemd-225-r7:0/2::lakitu-private, ebuild scheduled for merge to '/build/lakitu/') (buildtime) (sys-apps/util-linux-2.27.1:0/0::portage-stable, ebuild scheduled for merge to '/build/lakitu/') (buildtime_slot_op) It might be possible to break this cycle by applying any of the following changes: - sys-apps/util-linux-2.27.1 (Change USE: +build) - sys-apps/util-linux-2.27.1 (Change USE: -systemd) Note that this change can be reverted, once the package has been installed. Full log: https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-paladin/builds/2696/steps/BuildPackages/logs/stdio This seems to related to CL:325680. We are planning a critical release today. Can we roll that CL back?
,
Apr 1 2016
we can disable USE=systemd for now in util-linux. it does three things: (1) makes `lslogins` query journald ... we don't run this program, and even that tiny bit of output we can live w/out (2) adds a --journald option to `logger` to write to journald instead of syslog ... we don't use that option anywhere, and we can just rely on the syslog->journald bridge (3) adds socket activation support to `uuidd` ... pretty sure we don't launch uuidd on our systems, so who cares :)
,
Apr 1 2016
+Aditya, author of https://chrome-internal-review.googlesource.com/#/c/253356/, which is to fix this in lakitu's overlay.
,
Apr 1 2016
,
Apr 1 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/overlay-lakitu-private/+/f24e8ed6e43abf3f2f62ed7aa48de6a921017a36 commit f24e8ed6e43abf3f2f62ed7aa48de6a921017a36 Author: Mike Frysinger <vapier@chromium.org> Date: Fri Apr 01 21:56:43 2016
,
Apr 2 2016
,
Apr 27 2016
,
Aug 12 2016
Closing. please reopen if its not fixed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by wonderfly@chromium.org
, Apr 1 2016