| Summary: | Fetcher failure: regulatory.bin; Checksum mismatch! | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | BogdanP <bogdan.potocnik> | ||||
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | Undecided | CC: | bluelightning, poky.bs.watcher, poky.watcher | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Other | ||||||
| OS: | arm | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | Don't know | |||||
| Attachments: |
|
||||||
The crda recipe is in meta-networking, which is not maintained by the Yocto Project. However, I am familiar with this problem - crda upstream has unfortunately decided to rearrange their website. OpenEmbedded is doing a couple of things to address it: 1) There is a patch to update crda to the latest version with fixed SRC_URI: http://patchwork.openembedded.org/patch/87751/ 2) Looking into creating a proper source mirror - here is the start of the thread: http://lists.openembedded.org/pipermail/openembedded-devel/2015-February/100071.html As a workaround you can download each file yourself, put it in your downloads directory and touch a file with the same name and .done appended to its name. |
Created attachment 2396 [details] Error log file ERROR: Fetcher failure for URL: 'wireless.kernel.org/.../2013.01.11-regulatory.bin;name=bin'. Checksum mismatch! File: '/home/bogdanp/ti-glsdk_dra7xx-evm_6_10_00_02/yocto-layers/downloads/2013.01.11-regulatory.bin' has md5 checksum ccc19c171457a1dba798d21eaa7f1fb5 when e0c8a5ca63fb8bf803213f9a0c90b50b was expected File: '/home/bogdanp/ti-glsdk_dra7xx-evm_6_10_00_02/yocto-layers/downloads/2013.01.11-regulatory.bin' has sha256 checksum 4bfbe086ade4cc6d635788eedbafc3c6355444c3a4a4367b64744273669c9fb6 when b1ee0b20c123c612dfdb6851ab42c01666f66fb583e0e590942f19bb54cf84be was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[bin.md5sum] = "ccc19c171457a1dba798d21eaa7f1fb5" SRC_URI[bin.sha256sum] = "4bfbe086ade4cc6d635788eedbafc3c6355444c3a4a4367b64744273669c9fb6" Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified.