<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/lib/bb/fetch2, branch 3.2_M2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=3.2_M2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=3.2_M2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2020-07-12T10:53:00+00:00</updated>
<entry>
<title>bitbake: fetch2: Change git fetcher not to destroy old references</title>
<updated>2020-07-12T10:53:00+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2020-07-08T11:07:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=61931d14df3be5273a38008ae2dff2a60a7d9b02'/>
<id>urn:sha1:61931d14df3be5273a38008ae2dff2a60a7d9b02</id>
<content type='text'>
It looks like we're about to see a lot of changes in branch names in repos. If
we have the prune option here, those old names are lost, the changes propagate
to our source mirrors and our old releases break.

We have the force option so any replaced references should be replaced, its only
orphaned branches which will now be preserved.

I believe this behaviour will cause us fewer problems given the changes that
look likely to happen.

(Bitbake rev: 820ab886e79eea516560c0c008e4cf059c6e11a3)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: perforce: add local path handling SRC_URI options</title>
<updated>2020-06-25T09:24:02+00:00</updated>
<author>
<name>Alexandru N. Onea</name>
<email>onea.alex@gmail.com</email>
</author>
<published>2020-06-23T09:00:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b7006f50c7b4b98ed15a1d8c15aeeb88719a9d8a'/>
<id>urn:sha1:b7006f50c7b4b98ed15a1d8c15aeeb88719a9d8a</id>
<content type='text'>
This patch implements three new SRC_URI options for the perforce
fetcher, namely:

* module
* remotepath

The options are intended to provide the user more control over the
downloaded file paths by allowing the user to specify how much of the remote
path should be preserved locally.

The changes in this patch are backwards compatible, i.e. if none of the
introduced options is specified, the default (old) behavior is enforced.

(Bitbake rev: aab228822d2f221c01337dd57d7582c51ce9a505)

Signed-off-by: Alexandru N. Onea &lt;onea.alex@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: perforce: add basic progress handler for perforce</title>
<updated>2020-06-25T09:24:02+00:00</updated>
<author>
<name>Alexandru N. Onea</name>
<email>onea.alex@gmail.com</email>
</author>
<published>2020-06-23T09:00:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=cb1fbec4d95e9cbb36ec84c605981444eeb81dd4'/>
<id>urn:sha1:cb1fbec4d95e9cbb36ec84c605981444eeb81dd4</id>
<content type='text'>
This patch adds a basic implementation of a progress handler for the
perforce fetcher, based on the number of files to be downloaded and the
output behavior of the p4 print command used in the fetcher
implementation.

(Bitbake rev: f0582292bf79b0988048683dfd086aa3b9787344)

Signed-off-by: Alexandru N. Onea &lt;onea.alex@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: fetch2/gitsm: Make need_update() process submodules</title>
<updated>2020-06-15T13:55:25+00:00</updated>
<author>
<name>Paul Barker</name>
<email>pbarker@konsulko.com</email>
</author>
<published>2020-06-12T19:15:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=816a12758bfcb5409accbf636ec58d9fa917cdb6'/>
<id>urn:sha1:816a12758bfcb5409accbf636ec58d9fa917cdb6</id>
<content type='text'>
If the bitbake.srcrev nugget is not present for the commit we're
interested in we should not just bail out and say that an update is
needed. Instead we can recursively walk through the submodules and check
for the presence of the required commits.

(Bitbake rev: cfc78316309556bec487ef0a5a9205e41f1be86f)

Signed-off-by: Paul Barker &lt;pbarker@konsulko.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: fetch2/gitsm: Mark srcrev as fetched once all submodules are processed</title>
<updated>2020-06-15T13:55:25+00:00</updated>
<author>
<name>Paul Barker</name>
<email>pbarker@konsulko.com</email>
</author>
<published>2020-06-12T19:15:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5c3d2ccf54ddd216e18d807c50331017ed77fe63'/>
<id>urn:sha1:5c3d2ccf54ddd216e18d807c50331017ed77fe63</id>
<content type='text'>
This prevents multiple bitbake.srcrev entries being created when a
repository has more than one submodule. It also ensures that the
bitbake.srcrev entry is not added unless all submodules are correctly
fetched.

(Bitbake rev: 860ff1193fe53f04696d41635a720c2d1f29fa7f)

Signed-off-by: Paul Barker &lt;pbarker@konsulko.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: fetch2: Add the ability to list expanded URL data</title>
<updated>2020-06-04T12:28:16+00:00</updated>
<author>
<name>Paul Barker</name>
<email>pbarker@konsulko.com</email>
</author>
<published>2020-06-03T19:31:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1251765fff1c12d943091a2981b347e721b93e4e'/>
<id>urn:sha1:1251765fff1c12d943091a2981b347e721b93e4e</id>
<content type='text'>
Some fetchers may download additional sources along with those
explicitly listed in SRC_URI. These "implicit URLs" will be needed by
the archiver to ensure that all sources can be archived.

We can't just return a list of URL strings since each URL may need its
own SRCREV data so we return a list of FetchData objects.

Each fetcher can override the implicit_urldata() function to provide the
additional FetchData objects. For now this is just needed in the gitsm
fetcher to walk git submodules recursively.

(Bitbake rev: 1350f241b7d991bd191ce9e44f6662e4376c6e24)

Signed-off-by: Paul Barker &lt;pbarker@konsulko.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: git.py: Use the correct branch to check if the repository has LFS objects.</title>
<updated>2020-06-04T12:28:16+00:00</updated>
<author>
<name>Mauro Queirós</name>
<email>maurofrqueiros@gmail.com</email>
</author>
<published>2020-05-29T10:06:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d64809679436e9338555ef4e75ea6def93fc09c3'/>
<id>urn:sha1:d64809679436e9338555ef4e75ea6def93fc09c3</id>
<content type='text'>
Function "contains_lfs" was only looking at the master branch when searching for LFS
content. LFS may be configured in specific branches only, so we need to use the
correct branch.

(Bitbake rev: 4fa67c2af830035a1ddedc14592ee25a15ebff22)

Signed-off-by: Mauro Queiros &lt;maurofrqueiros@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: git.py: LFS bitbake note should not be printed if need_lfs is not set.</title>
<updated>2020-06-04T12:28:16+00:00</updated>
<author>
<name>Mauro Queirós</name>
<email>maurofrqueiros@gmail.com</email>
</author>
<published>2020-05-29T10:06:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3f8b8f8bcafa6d37b89c9e193be1326332366dab'/>
<id>urn:sha1:3f8b8f8bcafa6d37b89c9e193be1326332366dab</id>
<content type='text'>
The message "Repository %s has LFS content but it is not being fetched" was
being printed, even when Git-LFS was available and "lfs=1" was set. In those
situations, we want to fetch LFS content, so that message would not make sense.

(Bitbake rev: 45028dfda5a29a34ab408cb3f11d72ae17963340)

Signed-off-by: Mauro Queiros &lt;maurofrqueiros@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: git.py: skip smudging if lfs=0 is set</title>
<updated>2020-06-04T12:28:16+00:00</updated>
<author>
<name>Mauro Queirós</name>
<email>maurofrqueiros@gmail.com</email>
</author>
<published>2020-05-29T10:06:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8051b79733842aed8f9e839669760be478afe569'/>
<id>urn:sha1:8051b79733842aed8f9e839669760be478afe569</id>
<content type='text'>
Git-LFS objects were being fetched even when lfs=0 was not set.
This patch disables LFS smudging when lfs=0. That way, only the LFS pointers
are downloaded during checkout.

(Bitbake rev: 646d86df7de774255246a3d7051c308e43eb257d)

Signed-off-by: Mauro Queiros &lt;maurofrqueiros@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: fetch2/cvs: Fix CVS fetcher clean method</title>
<updated>2020-05-27T09:46:33+00:00</updated>
<author>
<name>Vyacheslav Yurkov</name>
<email>Vyacheslav.Yurkov@bruker.com</email>
</author>
<published>2020-05-05T10:18:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=30eb63a414ed026cd90329069669b52251988620'/>
<id>urn:sha1:30eb63a414ed026cd90329069669b52251988620</id>
<content type='text'>
Clean method assumes that download directory should be determined from
CVSDIR variable, but this is handled differently in download method.
Now we set download directory for the whole class in urldata_init

(Bitbake rev: 6d7ad9b06b82612f0dd17ffccea7ab98f9077198)

Signed-off-by: Vyacheslav Yurkov &lt;Vyacheslav.Yurkov@bruker.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
