linux/poky.git/bitbake/lib/bb/fetch2/__init__.py, branch 5.3_M2Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=5.3_M22025-05-28T11:37:02+00:00bitbake: fetch2: Ensure a valid symlink in `PREMIRRORS` case when using shallow cloning2025-05-28T11:37:02+00:00Stefan Kochstefan-koch@siemens.com2025-05-27T09:59:02+00:00urn:sha1:f5ae37fbd86c1328ebd81166573fbad3028abe5b
- Since `ud.path` contains in that case the `PREMIRRORS` prefix path,
this change ensures that a correct symlink is set up.
(Bitbake rev: 37ed18e45aa17406162efc5ee3ddb2d6b33d07b9)
Signed-off-by: Stefan Koch <stefan-koch@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2: Move the `ensure_symlink()` function into the `FetchMethod` class2025-05-28T11:37:02+00:00Stefan Kochstefan-koch@siemens.com2025-05-27T09:59:01+00:00urn:sha1:0e9ce41a1cc0e1158f84d5c5c08cf23b5c161155
(Bitbake rev: d934763f91b9bda85f273a44f12a04a3ca19fc28)
Signed-off-by: Stefan Koch <stefan-koch@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2: add support for .debs containing uncompressed data tarballs2025-05-28T11:37:02+00:00Isaac Trueisaac.true@emlix.com2025-05-26T13:57:33+00:00urn:sha1:a3bdd2144c39772c1217c30bc09fbc55fb967c6c
Some .deb files contain uncompressed data tarballs which do not have an
additional file extension after `.tar`. Add support for such cases while
preserving the existing behaviour.
(Bitbake rev: e3834deb427ceb1d1ae9a96c1e0dec990d7f3805)
Signed-off-by: Isaac True <isaac.true@emlix.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake: fetch: Fix BB_FETCH_PREMIRRORONLY for git mirror tarballs2025-04-10T10:07:38+00:00Julian Hallerjulian.haller@philips.com2025-04-04T12:10:44+00:00urn:sha1:f3948d6ee319d9a20ff2ac2800ea957d43979996
When invoking the original git fetcher after downloading a mirror
tarball, BB_FETCH_PREMIRRORONLY is ignored. This leads to git fetch
commands targeting the upstream source being executed silently. Ensure
setting BB_NO_NETWORK before invoking the original fetcher. While this
was only observed for git, setting this in general for all fetcher
types makes sense at this location.
(Bitbake rev: 1b1321f2b60c0a66159e3f20c6befcb0b3ccc4c7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch: Drop multiple branch/revision support for single git urls2025-03-20T13:50:40+00:00Richard Purdierichard.purdie@linuxfoundation.org2025-03-18T22:17:17+00:00urn:sha1:bdd2b0fee18c43597efc3493b9ac9ace9ccf7959
We used to use this for bare clones where a single git url could handle multiple
revisions (which implied multiple branches).
We don't use this any more and I doubt we'd want to go back to it. If we
remove it, we can simplfy the looping in the code which seems desireable.
This patch does change the warning for missing branch parameters to a
error. The message has hinted about that for long enough.
Some test cases are removed since they are no longer needed.
(Bitbake rev: 2515fbd10824005fa7f34e87706000c079920366)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch/git: Rework tag parameter handling2025-03-19T11:46:30+00:00Richard Purdierichard.purdie@linuxfoundation.org2025-03-18T11:04:21+00:00urn:sha1:18a533bfe6d4d5020c0252f9aecf6fc4abda672e
Currently bitbake disallows tag parameters along with revision parameters.
This isn't great since quite often, we'd like to verify that a given revision
does match some tag. At the same time we don't want to or need to access
the network to verify this, which normally a tag would require.
Rework the code so that tag and revisions can both be specified together.
Verify that any tag specified matches the revision in use at unpack time.
This means we can start requiring people to put tags in git SRC_URIs
when revisions are used, making review a little easier that it isn't
some random revision.
The test that is dropped looks like a different test but the comment
is a copy and paste error. The SRCREV/rev mismatch test remains, this
removes the rev and tag set test.
(Bitbake rev: d591d7633fe8d739ec00395920e44910b0b77e27)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2: Partial revert decodeurl() to not use the URI class2025-03-07T15:38:15+00:00Stefan Herbrechtsmeierstefan.herbrechtsmeier@weidmueller.com2025-03-07T09:43:20+00:00urn:sha1:bae86fe618075f28b708d2c89d247937a75226fc
This partial reverts commit a5d569c94700f04b8193c6bccae5af619931b00f
which changes decodeurl() to use the URI class to parse the URL instead
of doing it itself. While reusing code is generally a good idea, using
urllib.parse.urlparse() (which the URI class does) to parse the regular
expression "URLs" that are used in PREMIRRORS and MIRRORS does not work.
A regular expression URL containing https?://... would be silently
ignored, while a URL using a negative lookahead such as
git://(?!internal\.git\.server).*/.* would result in a cryptic error:
Exception: re.error: missing ), unterminated subpattern at position 0
The problem is that urllib.parse.urlparse() treats the ? as the start of
URL parameters and thus stops parsing whatever part of the URL it was
parsing. Restore the old function and use it in the PREMIRRORS and
MIRRORS code.
(Bitbake rev: f8a7712754e6d0199a0d227fca288307b935368d)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2: Fix BB_FETCH_PREMIRRORONLY network disabling2025-02-25T12:49:52+00:00Richard Purdierichard.purdie@linuxfoundation.org2025-02-20T16:57:28+00:00urn:sha1:ba91179519f2673ef803872baf2064281af37028
When using BB_FETCH_PREMIRRORONLY we write to the datastore to disable the network.
This change needs to be undo when handling later urls, so operate on a copy of the
datastore to allow this.
Reported by Julian Haller <julian.haller@philips.com>
(Bitbake rev: 67a5ede8ae92ed7dcad29fd0dcfd62c6640b10b2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2: local: use path variable2025-02-11T21:18:39+00:00Stefan Herbrechtsmeierstefan.herbrechtsmeier@weidmueller.com2025-02-07T12:46:55+00:00urn:sha1:f17c51c6959f740b279814624b40c65d69827637
Use the path variable from the fetch data instead of decoding the path
manually from the plain unexpanded url.
(Bitbake rev: ad3a29fa6ea53741d4e1786de35f8e7fc4292e7a)
Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2: remove unnecessary expand function calls2025-02-11T21:18:39+00:00Stefan Herbrechtsmeierstefan.herbrechtsmeier@weidmueller.com2025-02-07T12:46:54+00:00urn:sha1:3e543e8eaa18cecd9e360eecd3925b18e7a9058e
The fetch data class already expands the type, host, path, user, pswd
and parm variables. The fetcher classes already expand the localfile
variable. The getVar function expands the returned string per default.
Remove unnecessary expand function calls to simplify the code.
(Bitbake rev: 1b1eb037b861fbf20491ac17e519e9eaf232b858)
Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>