<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git, branch 2.8_M1</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=2.8_M1</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=2.8_M1'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2019-06-10T16:47:35+00:00</updated>
<entry>
<title>build-appliance-image: Update to master head revision</title>
<updated>2019-06-10T16:47:35+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-06-10T16:47:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9910a3631ce953b8dd8f3d57d6e122c7fd8cb462'/>
<id>urn:sha1:9910a3631ce953b8dd8f3d57d6e122c7fd8cb462</id>
<content type='text'>
(From OE-Core rev: 86266dfcd70b8e3435d267538c3e6e4d69be829e)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>recipetool: add python3 support</title>
<updated>2019-06-10T16:38:10+00:00</updated>
<author>
<name>Maciej Pijanowski</name>
<email>maciej.pijanowski@3mdeb.com</email>
</author>
<published>2019-06-08T19:13:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bb59bcd016bdd815809ac10df45d61c364c46df0'/>
<id>urn:sha1:bb59bcd016bdd815809ac10df45d61c364c46df0</id>
<content type='text'>
Add support for generating python3 recipes using the recipetool / devtool.
Drop python2 support at the same time.

Tested with:

oe-selftest -r recipetool.RecipetoolTest

[YOCTO #13264]

(From OE-Core rev: d8b2f58974482b3b1ccc65c5f93104d0d7ba87bc)

Signed-off-by: Maciej Pijanowski &lt;maciej.pijanowski@3mdeb.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: QB_FSINFO to support fstype wic images</title>
<updated>2019-06-10T16:38:10+00:00</updated>
<author>
<name>Adrian Freihofer</name>
<email>adrian.freihofer@siemens.com</email>
</author>
<published>2019-06-09T12:03:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0e4c79a7c4dae93fb1b12e8c0a59e8252e3f4b71'/>
<id>urn:sha1:0e4c79a7c4dae93fb1b12e8c0a59e8252e3f4b71</id>
<content type='text'>
wic images are handled as vmtype images. Starting qemu with "-kernel"
parameter and an image of type wic is not supported. Especially for
"-machine virt" the combination of wic with -kernel parameter would
be beneficial.

The new parameter QB_FSINFO allows to pass image type specific flags to
runqemu. QB_FSINFO is a space separated list of parameters. Parameters are
structured according to the following pattern: image-type:flag.

For now two parameters are supported:
- wic:no-kernel-in-fs
  The wic image is treated as rootfs only image. A -kernel option is
  passed to qemu.
- wic:kernel-in-fs
  The wic image is treated as VM image including a bootloader and a
  kernel. This is still the default behavior.

Example:
QB_DEFAULT_FSTYPE = "wic"
QB_FSINFO = "wic:no-kernel-in-fs"
QB_KERNEL_ROOT = "/dev/vda1"
QB_SYSTEM_NAME = "qemu-system-aarch64"
QB_MACHINE = "-machine virt"
...

[YOCTO #13336]

(From OE-Core rev: 2aa79a67affd22dfa37e4c2945c6ab0c86321f98)

Signed-off-by: Adrian Freihofer &lt;adrian.freihofer@siemens.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: cooker: Add compability handling for multiconfig: prefix migration</title>
<updated>2019-06-10T13:46:38+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-06-10T13:19:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=79ef0eab3555dc9e9994e899aa00a70ed8573c3c'/>
<id>urn:sha1:79ef0eab3555dc9e9994e899aa00a70ed8573c3c</id>
<content type='text'>
This allows "multiconfig:" targets to continue to work by internally
mapping them to the new "mc:" naming, allowing older builds to work
as before.

(Bitbake rev: c4d90890547af642e99cc541af3415df3559563e)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: multiconfig: Switch from 'multiconfig' -&gt; 'mc'</title>
<updated>2019-06-10T13:46:38+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-06-07T12:35:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1f68b0bd98ab0d9aeb7e5dae560d9d505ffac7c3'/>
<id>urn:sha1:1f68b0bd98ab0d9aeb7e5dae560d9d505ffac7c3</id>
<content type='text'>
After real world use its clear the "multiconfig:" prefix to multiconfig tasks,
whilst clear, is also clumbersome. Switch to use the short version instead.

mcdepends will continue to work with "multiconfig:" for now as well. The commandline
will only accept mc: going forward.

[YOCTO #11168]

(Bitbake rev: 821daf093b76504067a8b77dfa4b181af6ec92b4)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>multiconfig: Adapt to bitbake switch 'multiconfig' -&gt; 'mc'</title>
<updated>2019-06-10T13:46:38+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-06-07T12:45:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=32df42cff5370bb0bda51f0f637357c18ee3b1eb'/>
<id>urn:sha1:32df42cff5370bb0bda51f0f637357c18ee3b1eb</id>
<content type='text'>
(From OE-Core rev: 8a6f7c1e455156966f467008645fef14db679ccf)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oeqa: Add reproducible build selftest</title>
<updated>2019-06-10T13:46:38+00:00</updated>
<author>
<name>Joshua Watt</name>
<email>jpewhacker@gmail.com</email>
</author>
<published>2019-06-06T20:33:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e5217b6c1024f216226443cb8246db9fc090f113'/>
<id>urn:sha1:e5217b6c1024f216226443cb8246db9fc090f113</id>
<content type='text'>
Adds an initial test for reproducible builds to the OE selftest. This
initial test builds core-image-minimal using sstate, then does a clean
build without sstate in another build directory, and finally does a
binary comparison of the resulting package files between the two builds.

The test is currently always skipped since it doesn't pass yet, but it
can easily be enabled locally

(From OE-Core rev: 2e591bdf93ec9e59b900562263dfe8e72b163baa)

Signed-off-by: Joshua Watt &lt;JPEWHacker@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: Fix Thud Bitbake release metadata</title>
<updated>2019-06-10T08:44:46+00:00</updated>
<author>
<name>David Reyna</name>
<email>David.Reyna@windriver.com</email>
</author>
<published>2019-06-10T00:48:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=17dfe628d175c2af3d3adabd7e1f1f6f1eefec13'/>
<id>urn:sha1:17dfe628d175c2af3d3adabd7e1f1f6f1eefec13</id>
<content type='text'>
Fix the Bitbake version ID for Thud (1.40).

[YOCTO #13356]

(Bitbake rev: 7d0ab11a0d1a2510515d7ebab66b922fbfc411c3)

Signed-off-by: David Reyna &lt;David.Reyna@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>base.bbclass: Add OE_EXTRA_IMPORTS</title>
<updated>2019-06-08T15:01:41+00:00</updated>
<author>
<name>Chris Laplante</name>
<email>chris.laplante@agilent.com</email>
</author>
<published>2019-06-07T18:57:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=070218c1c5d1055353dc7008569ef0ae058c806b'/>
<id>urn:sha1:070218c1c5d1055353dc7008569ef0ae058c806b</id>
<content type='text'>
OE_IMPORTS is not intended to be touched by users, but there are cases
in which layers might want to make additional Python modules available
to Python functions. For example, Python modules defined in the layer
themselves (under meta-layer/lib).

(From OE-Core rev: 00fa8391365863fa7805ad61b2d1a8425b9ea040)

Signed-off-by: Chris Laplante &lt;chris.laplante@agilent.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>testimage: consider QB_DEFAULT_FSTYPE</title>
<updated>2019-06-08T15:01:41+00:00</updated>
<author>
<name>Adrian Freihofer</name>
<email>adrian.freihofer@siemens.com</email>
</author>
<published>2019-06-08T07:59:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=13aa3bea40a177d34b50745427257bc6b513f084'/>
<id>urn:sha1:13aa3bea40a177d34b50745427257bc6b513f084</id>
<content type='text'>
testimage.bbclass starts qemu with the first image type found in
the IMAGE_FSTYPES list. It's weird: this ['wic', 'tar'] works but
this ['tar'. 'wic'] does not. If QB_DEFAULT_FSTYPE is defined,
this fstype is booted.

(From OE-Core rev: aedb6bf9b6ccf37f69372642bc4c5dbbca92d0d9)

Signed-off-by: Adrian Freihofer &lt;adrian.freihofer@siemens.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
