Using the eSDK installer from 2.4 release and following the guide on SDK manual, I have tried to use sdk-install subcommand but the operation failed unexpectedly. eSDK installer used in this example: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/toolchain/x86_64/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.4.sh When running ‘devtool sdk-install’ ----- snip ----- $ devtool sdk-install mesa NOTE: Starting bitbake server... Loading cache: 100% |##############################################################################################################| Time: 0:00:00 Loaded 1275 entries from dependency cache. NOTE: Installing mesa... Loading cache: 100% |##############################################################################################################| Time: 0:00:00 Loaded 1275 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Initialising tasks: 100% |#########################################################################################################| Time: 0:00:02 Checking sstate mirror object availability: 100% |#################################################################################| Time: 0:00:02 NOTE: Executing SetScene Tasks NOTE: Tasks Summary: Attempted 205 tasks of which 205 didn't need to be rerun and all succeeded. ERROR: Failed to install mesa – unavailable ----- snip -----
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.