Creating chroot with cros_sdk for release-R77-12371.B fails

87 views
Skip to first unread message

Moritz Graf

unread,
Jan 19, 2022, 12:07:09 PM1/19/22
to Chromium OS Discussion
Hey there,
i am trying to create the chroot for release-R77-12371.B with cros_sdk, but it fails with following error:

Retrying emerge of chromeos-base/devserver-0.0.3-r419.
Started chromeos-base/devserver-0.0.3-r419 (logged in /tmp/devserver-0.0.3-r419-3CR8US)
=== Start output for job devserver-0.0.3-r419 (0m0.6s) ===
devserver-0.0.3-r419: >>> Emerging (1 of 1) chromeos-base/devserver-0.0.3-r419::chromiumos
devserver-0.0.3-r419:  * Running stacked hooks for pre_pkg_setup
devserver-0.0.3-r419:  *    sysroot_build_bin_dir ...                                       [ ok ]ver-0.0.3-r419:
devserver-0.0.3-r419:  * Running stacked hooks for post_pkg_setup
devserver-0.0.3-r419:  *    python_eclass_hack ...                                          [ ok ]ver-0.0.3-r419:
devserver-0.0.3-r419:  * Running stacked hooks for pre_src_unpack
devserver-0.0.3-r419:  *    python_multilib_setup ...                                       [ ok ]ver-0.0.3-r419:
devserver-0.0.3-r419: >>> Unpacking source...
devserver-0.0.3-r419:  * ACCESS DENIED:  open_wr:      /mnt/host/source/src/platform/dev/.git/index.lock
devserver-0.0.3-r419:  * Using local source dir(s): /mnt/host/source/src/platform/dev
devserver-0.0.3-r419:  * path: /mnt/host/source/src/platform/dev
devserver-0.0.3-r419:  * destdir: /var/tmp/portage/chromeos-base/devserver-0.0.3-r419/work/devserver-0.0.3
devserver-0.0.3-r419: >>> Source unpacked in /var/tmp/portage/chromeos-base/devserver-0.0.3-r419/work
devserver-0.0.3-r419:  * Running stacked hooks for post_src_unpack
devserver-0.0.3-r419:  *    asan_init ...                                                   [ ok ]ver-0.0.3-r419:
devserver-0.0.3-r419:  * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
devserver-0.0.3-r419:  * LOG FILE: "/var/log/sandbox/sandbox-13006.log"
devserver-0.0.3-r419:  *
devserver-0.0.3-r419: VERSION 1.0
devserver-0.0.3-r419: FORMAT: F - Function called
devserver-0.0.3-r419: FORMAT: S - Access Status
devserver-0.0.3-r419: FORMAT: P - Path as passed to function
devserver-0.0.3-r419: FORMAT: A - Absolute Path (not canonical)
devserver-0.0.3-r419: FORMAT: R - Canonical Path
devserver-0.0.3-r419: FORMAT: C - Command Line
devserver-0.0.3-r419:
devserver-0.0.3-r419: F: open_wr
devserver-0.0.3-r419: S: deny
devserver-0.0.3-r419: P: /mnt/host/source/src/platform/dev/.git/index.lock
devserver-0.0.3-r419: A: /mnt/host/source/src/platform/dev/.git/index.lock
devserver-0.0.3-r419: R: /mnt/host/source/.repo/projects/src/platform/dev.git/index.lock
devserver-0.0.3-r419: C: git status --porcelain
devserver-0.0.3-r419:  * --------------------------------------------------------------------------------
devserver-0.0.3-r419: >>> Failed to emerge chromeos-base/devserver-0.0.3-r419, Log file:
devserver-0.0.3-r419: >>>  '/var/log/portage/chromeos-base:devserver-0.0.3-r419:20220119-141355.log'
=== Complete: job devserver-0.0.3-r419 (0m0.6s) ===
Failed chromeos-base/devserver-0.0.3-r419 (in 0m0.6s). Your build has failed.
Pending 8/8, Building 0/0, Retrying 2, [Time 15:13:55 | Elapsed 0m30.9s | Load 1.23 0.91 1.05]

I am getting the same error for following packages:
chromeos-base/vboot_reference-1.0-r1671
chromeos-base/verity-0.0.1-r114
 sys-apps/rootdev-0.0.1-r34
 chromeos-base/update_payload-0.0.1-r185
 dev-util/crosutils-0.0.1-r2276

I can't find any information about how to resolve this.

I followed exactly these guidelines but always ends up with the same error:

I would be happy if someone can explain me this error and help me to resolve it, so that i can successfull create a chroot for release-R77-12371.B

Mike Frysinger

unread,
Jan 19, 2022, 12:17:01 PM1/19/22
to morit...@merkle.de, Chromium OS Discussion
i vaguely recall us fixing this bug in newer versions, but we don't backport to release branches because those are not long lived.  fairly certain anything you build with R77 will have known security vulnerabilities and you should not do that.  so switch to ToT instead.
-mike

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss

Moritz Graf

unread,
Jan 20, 2022, 1:21:24 AM1/20/22
to Chromium OS Discussion, Mike Frysinger, Chromium OS Discussion, Moritz Graf

Okay, alright. Thanks for the fast response.
Sry, but what do you mean with ToT?

Sameeruddin Shaik

unread,
Jan 20, 2022, 1:47:36 AM1/20/22
to morit...@merkle.de, Chromium OS Discussion, Mike Frysinger
It's tip of tree

--sameer

---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

Moritz Graf

unread,
Jan 20, 2022, 2:04:18 AM1/20/22
to Chromium OS Discussion, sameerudd...@gmail.com, Chromium OS Discussion, Mike Frysinger, Moritz Graf
Alright, thank you guys.

Heiko Stübner

unread,
Feb 11, 2023, 3:04:13 PM2/11/23
to ChromiumOS Discussion, Mike Frysinger, Chromium OS Discussion, morit...@merkle.de
As this is the prime search result for this error and I spend a while looking for the solution on my own, the relevant fix is

For the next person stumbling over this ;-) .

As I want to play with low-level firmware on one of my old veyron devices, the top of tree isn't an option here.

Heiko

Mike Frysinger schrieb am Mittwoch, 19. Januar 2022 um 18:17:01 UTC+1:
Reply all
Reply to author
Forward
0 new messages