<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts, branch yocto-3.4.4</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-3.4.4</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-3.4.4'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2022-04-22T15:12:17+00:00</updated>
<entry>
<title>scripts/runqemu: Fix memory limits for qemux86-64</title>
<updated>2022-04-22T15:12:17+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-03-14T13:35:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4337b18725aa0ef96e7b1962c95ca54b48e8bc28'/>
<id>urn:sha1:4337b18725aa0ef96e7b1962c95ca54b48e8bc28</id>
<content type='text'>
When setting memory to 4GB, qemu is only running with 2GB for x86_64.
Avoid this by removing the mem= option to the kernel and letting the
qemu configuration handle it for x86 in a similar way to mips.

(From OE-Core rev: ad7a8bf827a24f195df55a5d49e3ace949b6e23e)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 2fd53417eba354c31c058c4bb066bb882e098add)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oe-pkgdata-util: Adapt to the new variable override syntax</title>
<updated>2022-04-09T07:27:04+00:00</updated>
<author>
<name>Peter Kjellerstedt</name>
<email>peter.kjellerstedt@axis.com</email>
</author>
<published>2022-03-10T21:23:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e37119c3583cc9da95624f4fcd969234285a8ad3'/>
<id>urn:sha1:e37119c3583cc9da95624f4fcd969234285a8ad3</id>
<content type='text'>
(From OE-Core rev: 8d44f3d72af8791ef526eea12710f7b8b6c3d750)

Signed-off-by: Peter Kjellerstedt &lt;peter.kjellerstedt@axis.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 2bf6a0ca9fdf639418646700b20b65c9960efdbe)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>wic: Use custom kernel path if provided</title>
<updated>2022-03-15T16:38:29+00:00</updated>
<author>
<name>Bill Pittman</name>
<email>bill.pittman@ni.com</email>
</author>
<published>2022-02-15T16:54:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1ce1e56da132b65858ced6bc0fbd182acca8c2a9'/>
<id>urn:sha1:1ce1e56da132b65858ced6bc0fbd182acca8c2a9</id>
<content type='text'>
If the custom kernel path is provided in options, then
use that path instead of the default path.

(From OE-Core rev: bced1ddc2358350a5df5b397be7a3ab7d64b08f6)

Signed-off-by: Bill Pittman &lt;bill.pittman@ni.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 1068102216a894c467f71f6046fdb37d5577545c)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>devtool: explicitly set main or master branches in upgrades when available</title>
<updated>2022-03-10T16:39:50+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2022-02-21T09:28:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a164989b59f90c452931d9fc03225ec59c2f525a'/>
<id>urn:sha1:a164989b59f90c452931d9fc03225ec59c2f525a</id>
<content type='text'>
In particular this resolves devtool's inability to pick a branch
when the same tagged commit is avaiable in main and in a release maintenance
branch.

Thanks to Peter Kjellerstedt for the suggestion.

(From OE-Core rev: e2f27f05018a7f7882166b1b82ffd4b443ca9dc0)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit bcb21ee2760a2c76039412a56c6cda43fbf96fd0)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>devtool: deploy-target: Remove stripped binaries in pseudo context</title>
<updated>2022-02-24T11:12:39+00:00</updated>
<author>
<name>Florian Amstutz</name>
<email>florian.amstutz@scs.ch</email>
</author>
<published>2022-02-02T10:15:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=96515b53440e52e765dec1caf52c55fec6a50634'/>
<id>urn:sha1:96515b53440e52e765dec1caf52c55fec6a50634</id>
<content type='text'>
deploy-target may fail the second time with "pseudo abort" because
devtool-deploy-target-stripped is deleted outside of pseudo's fakeroot
context.

(From OE-Core rev: 23b0efb5428343b395a3abf76c84b21b08bbc33c)

Signed-off-by: Florian Amstutz &lt;florian.amstutz@scs.ch&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 2338a33b690b0bbe279cde3f73764911b239cb50)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/runqemu-ifdown: Don't treat the last iptables command as special</title>
<updated>2022-02-24T11:12:39+00:00</updated>
<author>
<name>Daniel Müller</name>
<email>muellerd@fb.com</email>
</author>
<published>2022-02-02T17:18:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=36815db55943984e49733e0029dde8994d489ef1'/>
<id>urn:sha1:36815db55943984e49733e0029dde8994d489ef1</id>
<content type='text'>
The runqemu-ifup script performs a bunch of setup steps that
runqemu-ifdown attempts to undo later on. While a bunch of said setup
operations are considered fatal should they fail, the iptables based NAT
setup notably is not.
The tear down procedure in runqemu-ifdown, however, has the iptables
based tear down as the last operation, with the status of it determining
the overall status of the script. Hence, if this step fails, the script
is considered a failure overall. That is arguably inconsistent: If the
NAT setup did not succeed, the tear down cannot succeed either.
To ensure similarity of the two paths, let's not treat the last iptables
tear down operation any special and allow it to fail the runqemu-ifdown
script, but just ignore failures.

Background: we have seen a NAT related setup problem on the ifup path
(which didn't cause script failure), but then saw an issue bubbled up
when this operation was meant to be undone on the ifdown path.

(From OE-Core rev: 2832f0277e29811cfb32fb9962fc2983afb34c8f)

Signed-off-by: Daniel Müller &lt;muellerd@fb.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 0ebcfb034bcad81efef5f746f0aa0b69772901a0)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>recipetool: Fix circular reference in SRC_URI</title>
<updated>2022-02-24T11:12:39+00:00</updated>
<author>
<name>Saul Wold</name>
<email>Saul.Wold@windriver.com</email>
</author>
<published>2022-02-03T19:43:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3636ca3ff839eea46cb7c4d978b3e33e64d28149'/>
<id>urn:sha1:3636ca3ff839eea46cb7c4d978b3e33e64d28149</id>
<content type='text'>
When creating a new recipe.bb file for a binary, don't use BP which
includes the version information, instead use BPN which is just the
name base Package Name.

Since PB is not specified, it takes the default:
PV = "1.0+git${SRCPV}"

But SRCPV is defined in terms of the SRC_URI, which leads to infinite
recursion (traceback below). Here are the pertinent variables which
cause the recursion:

SRC_URI = "git://github.com/lvc/abi-dumper;protocol=https;subdir=${BP}"
BP = "${BPN}-${PV}"
PV = "1.0+git${SRCPV}"
SRCPV = "${@bb.fetch2.get_srcrev(d)}"

def get_srcrev(d, method_name='sortable_revision'):
    # ... trimmed
    scms = []
    fetcher = Fetch(d.getVar('SRC_URI').split(), d)
    # ... trimmed

[YOCTO #14040]

(From OE-Core rev: 1deb4e4b13fa37a480bddd5ab930fcdfe0475761)

Signed-off-by: Saul Wold &lt;saul.wold@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 3b8d43fc53ee13d39abc3b2a1f706a97fcf752aa)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-check-layer: add debug output for the layers that were found</title>
<updated>2022-02-09T23:15:15+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross@burtonini.com</email>
</author>
<published>2022-01-24T16:25:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7d52358534cf4fe03724f0b0d42f152cfe13944e'/>
<id>urn:sha1:7d52358534cf4fe03724f0b0d42f152cfe13944e</id>
<content type='text'>
When debugging weird yocto-check-layer output it is useful to know
what the tool found when looking for layers.

(From OE-Core rev: 6ff05fe05a23d4355c3a33a03350dea025133689)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 711e2d4d7baf36f8497741c14268d7f72d0db016)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/buildhistory-diff: drop use of distutils</title>
<updated>2022-01-12T22:03:31+00:00</updated>
<author>
<name>Tim Orling</name>
<email>timothy.t.orling@intel.com</email>
</author>
<published>2021-10-30T15:35:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2fbc7f5af18ab16ddabd7022fc4abc357d15589b'/>
<id>urn:sha1:2fbc7f5af18ab16ddabd7022fc4abc357d15589b</id>
<content type='text'>
The use of distutils.version.LooseVersion to check for GitPython &gt; 0.3.1
is not really needed anymore since any supported distribution has at least
1.0.0 (centos-7 via epel7, debian-9, ubuntu-16.04)

If we want to reinstate this check, alternatives would be to require
python3-packaging on all hosts and use packaging.version.Version or
use an imported LooseVersion in bb.version.

[YOCTO #14610]

(From OE-Core rev: 298222353584776afc1dfe17abc5916b4ada40de)

Signed-off-by: Tim Orling &lt;timothy.t.orling@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit bc90dcae9f53ddc246942f4d9b8ae8943e3b9754)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts: Update to use exec_module() instead of load_module()</title>
<updated>2022-01-12T22:03:31+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-01-04T23:06:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=849234d3ddb36650c0e07bd4e6fdbe3af7acc10e'/>
<id>urn:sha1:849234d3ddb36650c0e07bd4e6fdbe3af7acc10e</id>
<content type='text'>
This is deprecated in python 3.12 and Fedora 35 is throwing warnings so
move to the new functions.

(From OE-Core rev: 6b9c12fab3b1319b6b0e59ed596d4a586a678ef2)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
(cherry picked from commit 655cd3f614d736416eab0d708b7c49674bf5c977)
Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
