emerging dev-lang spidermonkey fails |
||||
Issue descriptionChrome Version: <69.0.3464.0> Chrome OS Version: <10799.0.2018_06_19_1616> Chrome OS Platform: <GOOGLE-EVE> Network info: <N/A, N/A, N/A> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Cr-Internals Steps To Reproduce: (1) Run cros_portage_upgrade on dev-lang/spidermonkey-1.8.5-r6 (2) Run emerge on dev-lang/spidermonkey Expected Result: Package compiles successfully and emerges Actual Result: It fails in the prepare phase
,
Jul 10
,
Jul 10
,
Jul 11
We have resolved the Autoconf issue. Steps to resolve: 1. Upgrade sys-devel/autoconf on host machine to include 2.13 (using cros_portage_upgrade and emerge) Emerging spidermonkey still results in compilation errors, however.
,
Jul 13
The bug has been resolved by the following commits: 1. https://chromium-review.googlesource.com/c/chromiumos/overlays/portage-stable/+/1136802 2. https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1136805 3. https://chromium-review.googlesource.com/c/chromiumos/overlays/portage-stable/+/1136831
,
Jul 21
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/aa33cbaaadcc8bfae1d794304f8a4a2ce00bcccb commit aa33cbaaadcc8bfae1d794304f8a4a2ce00bcccb Author: Victor Reyes <vmreyes@google.com> Date: Sat Jul 21 01:34:04 2018 autotools: updated eclass to upstream BUG=chromium:862390 TEST=emerge-eve =dev-lang/spidermonkey-1.8.5-r6 Change-Id: Ib7154f5dc0309c9169802c2a6f6a28be4af8b64d Signed-off-by: Victor Reyes <vmreyes@google.com> Reviewed-on: https://chromium-review.googlesource.com/1136802 Commit-Ready: Victor Reyes Espinoza <vmreyes@google.com> Tested-by: Victor Reyes Espinoza <vmreyes@google.com> Tested-by: Salud Lemus <saludlemus@google.com> Reviewed-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/aa33cbaaadcc8bfae1d794304f8a4a2ce00bcccb/eclass/autotools.eclass
,
Jul 30
Bump. Spidermonkey remains an issue. It is a requirement for polkit, which is a runtime requirement for fwupd.
,
Jul 30
mmm polkit doesn't belong on CrOS. if fwupd needs it, you'll need to fix fwupd.
,
Jan 7
,
Jan 7
@vapier: Fwupd has a client/daemon architecture. The daemon runs as root, client runs as a regular user. Policykit is used to define what the client is able to do. For example; upgrade FW, downgrade FW. How should this be done without policy kit in ChromeOS? |
||||
►
Sign in to add a comment |
||||
Comment 1 by bleung@chromium.org
, Jul 10