linux/poky.git/bitbake/lib/bb/fetch2, branch 1.3.2

bitbake: ssh.py: add example SRC_URI

2013-03-03T17:02:22+00:00

(Bitbake rev: 5aa75f8090c04a9ab479e4dca77fcbb9b41cf463) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: ssh.py: throw ParameterError when someone tries ssh://foo; protocol=git

2013-03-03T17:02:22+00:00

* taken from SFTP fetcher: http://patchwork.openembedded.org/patch/43027/ (Bitbake rev: 6437b324a15e2730a12968beb58c2087aa712f46) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: ssh: fix fetcher

2013-03-03T17:02:22+00:00

* set localpath in urldata_init otherwise localpath and basename were None, when fetcher was trying to define .lock and .done paths basepath = d.expand("${DL_DIR}/%s" % os.path.basename(self.localpath or self.basename)) * remove "host" from localpath .done and .lock files are always using just basename, so if someone has 2 recipes with: SRC_URI = "ssh://foo/file.txt" SRC_URI = "ssh://bar/file.txt" then there will be only one file.txt.done in downloads anyway (and only first file.txt from first server will be returned on do_fetch (Bitbake rev: 5ac3ab3b565f70cd90cfbe121ddd2d899bfc0214) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: fetch2/wget: Fix for mixed-up wget commands

2012-12-07T17:25:54+00:00

wget commands for check and resume were mixed-up, leading to the following issues: 1. long running "NOTE: Preparing runqueue" reason: objects were downloaded, not spidered on the mirror 2. Failing network test in Build Appliance, because wget 1.14 (in use in BA) will fail if a file already exists. During the network connectivity test, index.php file was actually downloaded, not spidered (checked for existence on yoctoproject.org website), leading to wget failure. (Bitbake rev: 6f960055f55c5559562e8cc89961508fc27bf3eb) Signed-off-by: Cristian Iorga Signed-off-by: Richard Purdie

bitbake: fetch2: raise an exception if user specifies protocol=git with http://

2012-10-03T16:30:17+00:00

It is a common mistake to use http:// and protocol=git when attempting to fetch from a git repository using the http protocol; if this is detected then throw an error explaining that you need to use git:// with protocol=http instead. (Bitbake rev: 5bc4930c1638db16bcd5f9c8cfc4081f9ffc192b) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: fetch2: add "-d" option to cpio

2012-09-27T15:45:27+00:00

Add "-d" option to cpio since it is useful: -d --make-directories Create leading directories where needed. [YOCTO #3137] (Bitbake rev: a78f9ded7896432b107f34c0bb608b389fdb676a) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: fetch2/git: Don't use deprecated API

2012-09-25T14:55:57+00:00

(Bitbake rev: 8e650b3307b60cfe8e7439ea6891c3a85f785af9) Signed-off-by: Richard Purdie

bitbake: fetch2/git: Add missing mkdir

2012-09-24T11:13:52+00:00

bitbake-selftest is failing due to directories not being created. This adds in an appropriate mkdir so the tests can complete. Presumably in general OE use, something else is ensuring the parent directory is created. (Bitbake rev: 1270a07713e2a6c6e6fadcc61b785aebc99ae17b) Signed-off-by: Richard Purdie

bitbake: fetch2: improve error output for checksum failures

2012-09-24T11:13:52+00:00

* Don't print the full exception in the initial warning - if we later succeed in fetching the file from a mirror, we won't usually need the details (which are in the fetch log if they are needed); otherwise the full error will be printed when the fetch operation fails. Also adjust the conditional block so that we don't print another warning just mentioning we're going to try mirrors. * Call logger.error() so that with knotty the full log is not printed * Provide an explanation around the lines we print for easily updating the checksums in the recipe. We don't want users to be just blindly updating the recipe in case of a transient failure or deliberately altered remote file. (Bitbake rev: 2793413106c925b06783beb7413aa87cbcf246c3) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: fetch2: make fetch failure errors more readable

2012-09-24T11:13:52+00:00

Most of the time we don't need to see the fetch command; the fetch log includes the command as a debug message in any case, so omit it. Also adjust the way command output is printed (we don't need stderr/stdout labelled, and print "no output" instead of "output:\nNone" when there is no output. (Bitbake rev: a75505a52e4da918222100221f79e8a658f90446) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie