Bug 1578 - SSTATE_MIRROR needs a trailing '/' character to work
Summary: SSTATE_MIRROR needs a trailing '/' character to work
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard: Final patch out for review on bitbake...
Depends on:
Blocks:
 
Reported: 2011-10-03 13:25 UTC by Matthew McClintock
Modified: 2011-11-24 14:16 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew McClintock 2011-10-03 13:25:10 UTC 
If I set 

SSTATE_MIRROR = "http://linux.freescale.net/yocto/sstate-cache"

the sstate mirror will not be used, however if I simply change this too:


SSTATE_MIRROR = "http://linux.freescale.net/yocto/sstate-cache/"

it works again.
Comment 1 Richard Purdie 2011-11-04 10:22:03 UTC 
I'm a bit confused by this report - there is not a SSTATE_MIRROR variable and SSTATE_MIRRORS doesn't use that syntax? Do you mean:

file://.* http://linux.freescale.net/yocto/sstate-cache

doesn't work but:

file://.* http://linux.freescale.net/yocto/sstate-cache/

does? That is a natural part of the mirror mapping code unfortunately...
Comment 2 Matthew McClintock 2011-11-04 12:06:01 UTC 
(In reply to comment #1)
> I'm a bit confused by this report - there is not a SSTATE_MIRROR variable and
> SSTATE_MIRRORS doesn't use that syntax? Do you mean:
> 
> file://.* http://linux.freescale.net/yocto/sstate-cache
> 
> doesn't work but:
> 
> file://.* http://linux.freescale.net/yocto/sstate-cache/
> 
> does? That is a natural part of the mirror mapping code unfortunately...

Correct. 

But its extremely non-obvious when you miss this. As we are just looking for cached stuff and not finding the cache is not a fatal result. Therefore it's easy to just assume something else is broken with the caching system.

Maybe we can add a QA on this variable to check the a trailing '/'? Or maybe it's better to leave it alone. Not sure what the best approach is...