Bug 6383

Summary:	detect invalid sstate mirrors
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Alexandru Damian <alexandru.damian>
Component:	bitbake	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	bluelightning, poky.bs.watcher, poky.watcher
Version:	1.7
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Alexandru Damian 2014-05-29 13:07:30 UTC

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

Comment 1 Richard Purdie 2014-05-29 14:43:11 UTC

How do you tell the difference between a broken mirror entry and an entry which simply has no compatible sstate?

Comment 2 Alexandru Damian 2014-05-30 10:08:05 UTC

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.

Comment 3 Richard Purdie 2014-09-24 14:38:42 UTC

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? :/.

Comment 4 Richard Purdie 2017-06-13 11:04:32 UTC

There is no solution to solve this problem, closing as unable to fix it.