linux/poky.git/bitbake/lib/bb/fetch2/bzr.py, branch pyro-enea

bitbake: fetch2: don't use deprecated bb.data APIs

2017-03-01T11:16:07+00:00

Cleanup some more usage of bb.data APIs in the fetchers. (Bitbake rev: 9752fd1c10b8fcc819822fa6eabc2c1050fcc03b) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

bitbake: fetch2: Rename "setup_revisons" to "setup_revisions"

2017-02-19T14:28:47+00:00

For spelling's sake, rename Python routine "setup_revisons" to "setup_revisions." (Bitbake rev: 4df59b027c02ef39d72476251ccd3fd62fc20bf6) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

bitbake: fetch2: preserve current working directory

2016-08-20T15:08:59+00:00

Fix the methods in all fetchers so they don't change the current working directory of the calling process, which could lead to "changed cwd" warnings from bitbake. (Bitbake rev: 6aa78bf3bd1f75728209e2d01faef31cb8887333) Signed-off-by: Matt Madison Signed-off-by: Richard Purdie

bitbake: fetch: Fix use of tar's --exclude option for tar >= 1.29

2016-08-10T09:46:34+00:00

Starting from tar 1.29 the --exclude option won't work anymore if is not used before the path. There are some fetch modules that copy the ptest using tar and --exclude option. This fixes these for bitbake. [YOCTO #9763] (Bitbake rev: cc71d5d9da71ea5f21d02f3b2fbf119bd2d794f0) Signed-off-by: Mariano Lopez Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: fetch2: Correct a few calls to latest_revision()

2013-11-25T13:02:27+00:00

In 6a48474de9505a3700863f31839a7c53c5e18a8d the url parameter to a number of functions was removed. However, not all calls to latest_revision() were fixed... (Bitbake rev: 7c94ca56b2fd85a989089f58b3dcce3172a778f2) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

bitbake: fetch2: Stop passing around the pointless url parameter

2013-11-22T12:03:02+00:00

There is no good reason to keep passing around the url parameter when its contained within urldata (ud). This is left around due to legacy reasons, some functions take it, some don't and its time to cleanup. This is fetcher internal API, there are a tiny number of external users of the internal API (buildhistory and distrodata) which can be fixed up after this change. (Bitbake rev: 6a48474de9505a3700863f31839a7c53c5e18a8d) Signed-off-by: Richard Purdie

bitbake: fetch2/git: Clean up sortable_revision

2013-05-22T11:10:12+00:00

Now we no longer try and provide increasing values from the fetcher, we can simplify the function structure for the sortable_revision pieces and move the AUTOINC handling directly into the function which needs it, simplifying the code. (Bitbake rev: fb068bee47bb1a06f02447daf16c2b2a79c03288) 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/bzr.py: Use "protocol" parameter to get the protocol

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

(Bitbake rev: 630876b40ed181312e84f902c4cfb97361afbe81) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie

bitbake/fetch2: Fix the problems introduced by the git fetcher AUTOREV fix

2011-04-20T01:13:26+00:00

The ordering constrains on the urldata_init functions are not straight forward. To avoid further problems, create a helper function to setup the source revisions which the init functions can all at the appropriate point. Signed-off-by: Richard Purdie