| Summary: | devtool sdk-install unable to add component | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Rebecca Chang <rebecca.swee.fun.chang> |
| Component: | autobuilder | Assignee: | Joshua Lock <joshuagloe> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | infras.ab.watcher, Infras.watcher, joshuagloe, pidge |
| Version: | 2.4 | ||
| Target Milestone: | 2.5 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Rebecca Chang
2017-11-16 00:35:40 UTC
I downloaded the 2.4.1 eSDK[1] from the Autobuilder and confirmed this bug. I then took a look at and realised that the SSTATE_MIRRORS isn't pointing to the per-release sstate mirror, i.e.: http://sstate.yoctoproject.org/2.4.1 but instead is pointing to the top-level sstate mirror folder: http://sstate.yoctoproject.org/ I believe the value of SSTATE_MIRRORS is inherited from the setting in auto.conf at the time of building, therefore the bug is in the autobuilder code that sets that value. 1. https://autobuilder.yocto.io/pub/releases/yocto-2.4.1/toolchain/x86_64/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.4.1.sh I've implemented a fix for this in CreateAutoConf and tested it on the yocto.io cluster with a synthetic 2.4.2 release. Having downloaded the generated eSDK I can confirm that I'm no longer able to reproduce the issue. |