linux/poky.git/bitbake/lib/bb/fetch2, branch 1.3_M3

bitbake: fetch2/local: Add search paths to the debug log to improve log usefullness

2012-08-02T22:04:27+00:00

(Bitbake rev: 2054c7d99933c1523d4b5c7f65d37c69b8472e47) Signed-off-by: Richard Purdie

bitbake: fetch2/local.py: Provide better debug output when fetch of a local file fails

2012-08-02T22:04:27+00:00

When a fetch failure occurs for a local file, this patch ensures we print the locations searched making it easier for the user to debug the problem. (Bitbake rev: a461adbc5f09b41c771a7603370f6f2d1299ae8e) Signed-off-by: Richard Purdie

bitbake: fetch2: print checksums when they are different then expected

2012-08-02T16:05:06+00:00

* in form which can be copied into a recipe without modification * like oe-classic did since: http://git.openembedded.org/openembedded/commit/?id=68abc465559a68e9201c9525be3c4acc6297eaed * it shows them in right form when they are missing completely, but in more verbose form when different * it needs to print that only when checksums were requested, e.g. fetching from sstate mirror sets both md5mismatch and sha256mismatch, but your checksums shouldn't be shown (Bitbake rev: 9eb34fc866775fd8310759a0111f232a9dc98981) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: fetch2: handle broken symlinks in local mirror handling

2012-08-02T16:05:06+00:00

If a file:// mirror is being used, the fetcher will create a symlink to the local file. However, if the local file gets removed, that link will be dead, and os.path.exists() returns False in that case, so it tries and fails to recreate the link. Now we unlink such a dead link if it exists. (Bitbake rev: 229ed3857e826e3e215e843cb51f729c1e13ed37) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

bitbake: fetch2/init.py: Add NoChecksumError exception

2012-08-02T16:05:05+00:00

Without the new exception, when the system is configured to use premirrors, but not allow network access (via BB_NO_NETWORK), when a recipe was lacking a checksum the wrong error message(s) were being generated. Instead of complaining about trying to perform network access, if the system was able to find the item in the premirror, it should inform the user of the lack of checksums, and the two SRC_URI fields they should use to update their recipe. (Bitbake rev: cb10e9c03a3f96d94e27e18330009616dde5e2b3) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

bitbake: fetch/local: Allow preservation of path components in relative file:// urls

2012-07-26T13:55:22+00:00

This enhances the fetcher to allow preservation of the path component in urls like: file://xxx/yyy/somefile.patch. (Bitbake rev: e49a656a499355a5c6e7eb00bf5b8f1795e8dddb) Signed-off-by: Richard Purdie

bitbake: bitbake wget fetcher: add parameter: downloadfilename

2012-07-24T09:35:33+00:00

this allows wget fetcher to store the downloaded file in a specified custom filename in ${DL_DIR} Exmaple: SRC_URI = "https://edc.intel.com/Download.aspx?id=6190;downloadfilename=LIN_IEMGD_1_14_GOLD_2443.tgz" This fixes bug: [YOCTO #2570] (Bitbake rev: ceb5871007f221c4d86a7bee421d4dd8d9100aaf) Signed-off-by: Nitin A Kamble Signed-off-by: Richard Purdie

bitbake: Change bzr fetcher to use branch instead of co. Fixes: bzr: ERROR: No pull location known or specified.

2012-07-24T09:35:33+00:00

This problem occurs when fetching a different revision of the same source. Which mean every time you update a bzr package. Using branch sets the pull location, and are the preferred way of cloning/branching a repository in bzr. (Bitbake rev: 877a04d0b3cea9d5dbdf3c54fe0feb54cb997dda) Signed-off-by: Martin Ertsaas Signed-off-by: Richard Purdie

bitbake: fetch2/svn.py: Use protocol parameter to get the protocol

2012-07-18T11:43:50+00:00

* it was send in v1 of proto -> protocol changes but then wasn't in V2 http://patchwork.openembedded.org/patch/31617/ where warning about proto= was moved to shared __init__ (Bitbake rev: b2017f493ab730d804ae44ec5a168d464626d046) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: fetch2/init.py: Warn user if SRC_URI is using "proto" and not "protocol"

2012-07-11T14:55:26+00:00

As well, if "proto" is used, get the associated value as "protocol" (Bitbake rev: 53e6b630f0463d2d07cdaa9c9eb36794dc9b6b69) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie