[bitbake-devel] [PATCH 0/9] Always use the url specified in the recipe as a base for the git shallow tarball naming
Urs Fässler
urs.fassler at bbv.ch
Mon Jul 23 15:42:50 UTC 2018
The existing behavior was to use the url where the repository was cloned from.
It happened that the tarball was not found when a mirror rewrite rule was
active.
We now use the url specified in the recipe to name the shallow tarball. It fixes
that the tarball is not found under certain conditions. In addition, the naming
is independent of network/server failure and the mapping of the name is easier
to understand.
Urs Fässler (9):
fetch2/git: add tests to verify naming of download directories
fetch2/git: add tests to capture existing behavior wrt. naming of git
shallow tarball
fetch2/git: only use relevant checks for shallow tarball unpack
tests/data: extract LogRecord into own file
fetch2/git: throw error when no up to date sources were found during
unpack
fetch2: declare urldata_init in base class
fetch2: provide original url in addition to the mirrored url to
FetchData.__init__ and FetchMethod.urldata_init
fetch2/git: move generation of git source name into own method
fetch2/git: name the shallow tarball according to the url specified in
the recipe rather than the mirrored url
lib/bb/fetch2/__init__.py | 17 +++--
lib/bb/fetch2/bzr.py | 2 +-
lib/bb/fetch2/clearcase.py | 2 +-
lib/bb/fetch2/cvs.py | 2 +-
lib/bb/fetch2/git.py | 56 +++++++++------
lib/bb/fetch2/gitannex.py | 4 +-
lib/bb/fetch2/hg.py | 2 +-
lib/bb/fetch2/local.py | 2 +-
lib/bb/fetch2/npm.py | 2 +-
lib/bb/fetch2/osc.py | 2 +-
lib/bb/fetch2/perforce.py | 2 +-
lib/bb/fetch2/repo.py | 2 +-
lib/bb/fetch2/s3.py | 2 +-
lib/bb/fetch2/sftp.py | 2 +-
lib/bb/fetch2/ssh.py | 2 +-
lib/bb/fetch2/svn.py | 2 +-
lib/bb/fetch2/wget.py | 2 +-
lib/bb/tests/data.py | 25 +------
lib/bb/tests/fetch.py | 142 +++++++++++++++++++++++++++++++++++++
lib/bb/tests/logrecord.py | 51 +++++++++++++
20 files changed, 258 insertions(+), 65 deletions(-)
create mode 100644 lib/bb/tests/logrecord.py
--
2.18.0
More information about the bitbake-devel
mailing list