6383 2014-05-29 13:07:30 +0000 detect invalid sstate mirrors 2017-06-13 11:04:32 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 1.7 x86 Multiple RESOLVED WONTFIX Medium enhancement Future 1 alexandru.damian richard.purdie bluelightning poky.bs.watcher poky.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 43645 0 alexandru.damian 2014-05-29 13:07:30 +0000 Bitbake should explicitly warn if sstate mirrors are set up, but they are unusable. e.g. - if no packages matched a mirror entry, a warning should be provided to the user to check the mirror settings 43651 1 richard.purdie 2014-05-29 14:43:11 +0000 How do you tell the difference between a broken mirror entry and an entry which simply has no compatible sstate? 43686 2 alexandru.damian 2014-05-30 10:08:05 +0000 I define a sstate mirror that has NO compatible sstate caches as broken, and let the user know about it. The purpose of sstate mirrors is to accelerate build. If it doesn't accelerate the build, the purpose is not accomplished, and the software should be proactive and let the user know that something that is expected is not happening. 45803 3 richard.purdie 2014-09-24 14:38:42 +0000 In practise this doesn't work. I often make some change, trigger a full rebuild and the fact there is no overlap with any of my configured mirrors is no surprise to me. The question therefore remains, how do we figure out when they are unusable? :/. 74056 4 richard.purdie 2017-06-13 11:04:32 +0000 There is no solution to solve this problem, closing as unable to fix it.