| Summary: | Can't build update-rc.d if BB_NO_NETWORK=1 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Gary Thomas <gary> |
| Component: | meta-yocto | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | poky.bs.watcher, poky.watcher, sgw |
| Version: | unspecified | ||
| Target Milestone: | 1.1 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Gary Thomas
2011-06-06 11:42:34 UTC
More data: $ ls -l /work/misc/Poky/sources/git*update-rc* -rw-rw-r-- 1 gthomas gthomas 8386 May 24 07:59 /work/misc/Poky/sources/git2_github.com.philb.update-rc.d.git.tar.gz If I disable BB_NO_NETWORK, the build succeeds but the tarball is unchanged, so there is no reason it can't be built with BB_NO_NETWORK=1 This is actually kind of by design in the fetcher. The trouble is that recipe says "tag=<somename>" and that is not a revision. bitbake is being careful and using the remote repository to translate <somename> into a revision. A local repository might not be up to date. Its certainly a corner case but I can see people reporting a bug if we didn't do this too so I'm not sure we can win :( So how can I ship something to my customers to build that may have no network connectivity? To date, I've been able to cache/stage all the relevant source files and provide those, but this seems to break that :-( |