Hi Ross,
在 2017年12月18日 21:02, Burton, Ross 写道:
Does it really need coreutils stat, or is busybox's stat sufficient?
It uses "--format" option with stat, but busybox.stat doesn't support
this option that would cause an error:
# stat --format="%04D" /
stat: unrecognized option '--format=%04D'
Use distro_features_check so that we can have a uniform controller.
Signed-off-by: Robert Yang
---
meta/recipes-core/systemd/systemd-serialgetty.bb | 10 --
meta/recipes-core/systemd/systemd_234.bb | 13 +
meta/recipes-core/udev/eudev_3.2.2.bb| 9 +++-
Use distro_features_check so that we can have a uniform controller.
Signed-off-by: Robert Yang
---
meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb
b/meta/recipes-core/sysvi
The following changes since commit 978472c58629d1448399207873bbead96b27102e:
image.bbclass: Add additional bb.debug to help track 12304 (2017-12-18
18:02:12 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/systemd
http://cgit.openembe
On 12/19/2017 10:33 PM, Bruce Ashfield wrote:
On Tue, Dec 19, 2017 at 12:23 AM, ChenQi wrote:
On 12/19/2017 12:45 PM, Bruce Ashfield wrote:
On Mon, Dec 18, 2017 at 11:03 AM, Ross Burton
wrote:
Hi,
Another batch of patches from the list which have passed autobuilder
testing and
review.
Ross
Ping Ross
//Hongxu
On 2017年12月06日 10:46, Hongxu Jia wrote:
OE uses qemumips to simulate a Malta board by default.
As upstream qemu introduced:
https://git.qemu.org/?p=qemu.git;a=commit;h=94c2b6aff43cdfcfdfb552773a6b6b973a72ef0b
The Malta board can support up to 2GiB of RAM which should
be abl
Hi Saul,
On 12/20/2017 04:11 AM, Saul Wold wrote:
We have seen more failures, but have not been able to directly reproduce
it maybe svaing the rootfs and it contains some content that is tripping
s/svaing/saving/.
up the e2fsprogs mkfs.ext4 populate_rootfs() function
Signed-off-by: Saul Wo
I forgot to mention, my contrib branch with these and a few additional
WIPs can be found here:
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=clsulliv/image-creation
Thanks,
Cal
On 12/19/2017 02:58 PM, California Sullivan wrote:
First, note that this is based on top of Haris'
== Series Details ==
Series: EFI boot partition improvements
Revision: 1
URL : https://patchwork.openembedded.org/series/10262/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the
We can't guarantee vmlinuz anymore. Use KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan
---
meta/classes/systemd-boot-cfg.bbclass | 6 +-
meta/classes/systemd-boot.bbclass | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/meta/classes/systemd-boot-cfg.bb
With the postprocess command and installation into /boot/ in place, we
can use wic to create an EFI-compatible image without it having any
knowledge of the kernel or bootloader.
Signed-off-by: California Sullivan
---
scripts/lib/wic/canned-wks/efi-bootdisk.wks.in | 6 ++
1 file changed, 6 in
We can't guarantee the kernel will be named vmlinuz anymore. Use
KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan
---
meta/classes/syslinux.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/syslinux.bbclass b/meta/classes/syslinux.bbclass
ind
This class is useful on its own and can be used to create configuration
recipes.
Signed-off-by: California Sullivan
---
...stemd-boot.bbclass => systemd-boot-cfg.bbclass} | 57 --
meta/classes/systemd-boot.bbclass | 70 +-
2 files changed, 1 i
This way we could theoretically support multiple bootloaders, and we
keep the convention of boot(x64|ia32).
Signed-off-by: California Sullivan
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-bsp/grub/grub-e
We can no longer rely on the kernel having a static name of "vmlinuz".
This means we can't use it as a sentinel value in our sed commands, and
we can't just copy vmlinuz to the boot directory.
Instead, we'll use "root=" as the sentinel value for our sed commands,
and we'll search for common kernel
This part is useful on its own, whereas the whole class together is
specific for image-live.
Signed-off-by: California Sullivan
---
.../{grub-efi.bbclass => grub-efi-cfg.bbclass} | 40 ---
meta/classes/grub-efi.bbclass | 122 +
2 files changed, 1
This makes use of the grub-efi-cfg bbclass that was split out to create
a grub.cfg file just like the old one.
Signed-off-by: California Sullivan
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 30 +
1 file changed, 30 insertions(+)
create mode 100644 meta/recipes-
This gives the class access to the DISK_SIGNATURE_UUID variable.
Signed-off-by: California Sullivan
---
meta/classes/image.bbclass | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ec940a4b659..38709691721 100644
--- a/meta/class
Previously this wasn't needed because the kernel was added at image
creation time to the boot partition. Now that the boot partition is
created from the /boot/ partition of the rootfs, it needs to be
installed there.
Signed-off-by: California Sullivan
---
meta/recipes-core/packagegroups/packageg
Since the bootloader is now installed instead of added at image creation
time, this is necessary for booting.
Also set the default to grub-efi. This is done because a default of
grub-efi is already used by live-vm-common.bbclass, and in the event
that EFI_PROVIDER isn't defined errors would occur.
EFI systems need their /boot/ directory in its own partition. By
splitting it into its own directory like this, we avoid /boot/ ending up
in the primary rootfs, and can easily create the EFI partition from the
IMAGE_BOOTFS directory.
Signed-off-by: California Sullivan
---
meta/classes/rootfs-pos
I couldn't find anywhere it was being used, and in trying to use it it
just spit out an error.
It now generates a random UUID and puts it in the deploy dir for
consumption.
Also use DISK_SIGNATURE_UUID for the replacement function, since that
is user-overridable.
Signed-off-by: California Sulliv
Rather than renaming the kernel to vmlinuz and assuming the name is
vmlinuz in the grub.cfg, copy to ${KERNEL_IMAGETYPE} and also use that
value in the grub.cfg file.
Signed-off-by: California Sullivan
---
meta/classes/grub-efi-cfg.bbclass | 4 +++-
meta/classes/grub-efi.bbclass | 2 +-
2 fi
If the EFI_PROVIDER is systemd-boot, install as boot(x64|ia32) as per
convention. If its not the EFI_PROVIDER, install as
systemd-boot(x64|ia32), as to not collide with other possible
bootloaders.
Signed-off-by: California Sullivan
---
meta/recipes-core/systemd/systemd-boot_234.bb | 28 +
Since /boot/ will be recipe/package controlled now we can't just deploy.
Signed-off-by: California Sullivan
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 32 +---
1 file changed, 25 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-bsp/grub/grub-efi_2.02.bb
b/m
Reuses our systemd-boot-cfg bbclass to generate systemd-boot
configuration files.
Signed-off-by: California Sullivan
---
meta/recipes-core/systemd/systemd-bootconf_1.00.bb | 31 ++
1 file changed, 31 insertions(+)
create mode 100644 meta/recipes-core/systemd/systemd-bootconf
First, note that this is based on top of Haris' multiple kernels patch:
http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144031.html
Currently, the boot partition of an EFI system is entirely controlled by
image creation. Either done entirely through wic, or one of the
bootl
I can't find VM_DEFAULT_KERNEL used anywhere else, and we should not be
statically installing the kernel as vmlinuz.
Signed-off-by: California Sullivan
---
meta/classes/live-vm-common.bbclass | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/meta/classes/live-vm-common
> -Original Message-
> From: Burton, Ross [mailto:ross.bur...@intel.com]
> Sent: Tuesday, December 19, 2017 2:02 PM
> To: Manjukumar Harthikote Matha
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] kernel-fitimage: Fix bad image type
> replacement for
> a
On Tue, Dec 19, 2017 at 2:06 PM, Tom Rini wrote:
> On Tue, Dec 19, 2017 at 10:04:29PM +, Burton, Ross wrote:
>>
>> I suspect this will just hang in master-next and never merge into master.
>
> That sounds good. And I suppose at this point, it would be pretty
> likely to not, too. Maybe in th
initramfs-framework is more modular and expandable. This change was
proposed in commit 28fc6ba761ed4a47efa7c43e7f7dff5e2fe72b5e
"core-image-minimal-initramfs: use initramfs-framework by default" but
reverted due to the selftests runqemu.RunqemuTests.test_boot_machine_iso
and runqemu.RunqemuTests.te
On Tue, Dec 19, 2017 at 10:04:29PM +, Burton, Ross wrote:
> On 19 December 2017 at 21:20, Tom Rini wrote:
>
> > On Tue, Dec 19, 2017 at 01:19:09PM -0800, Andre McCurdy wrote:
> > > On Tue, Dec 19, 2017 at 12:54 PM, Tom Rini wrote:
> > > > On Tue, Dec 19, 2017 at 12:11:48PM -0800, Saul Wold w
On 19 December 2017 at 21:20, Tom Rini wrote:
> On Tue, Dec 19, 2017 at 01:19:09PM -0800, Andre McCurdy wrote:
> > On Tue, Dec 19, 2017 at 12:54 PM, Tom Rini wrote:
> > > On Tue, Dec 19, 2017 at 12:11:48PM -0800, Saul Wold wrote:
> > >> We have seen more failures, but have not been able to direc
This is queued in ross/mut2 and should be in master shortly, although as
it's almost the Christmas holidays here it may be in the new year.
Ross
On 19 December 2017 at 21:34, Manjukumar Harthikote Matha <
manju...@xilinx.com> wrote:
> Ping?
>
> Any reason for this being in pending status? Please
Ping?
Any reason for this being in pending status? Please let me know
Thanks,
Manju
> -Original Message-
> From: Manjukumar Matha [mailto:manjukumar.harthikote-ma...@xilinx.com]
> Sent: Wednesday, December 13, 2017 10:27 AM
> To: openembedded-core@lists.openembedded.org
> Cc: Thomas Perr
From: Stefan Agner
When compiling OpenSSL with binutils 2.29 for ARM with Thumb2 enabled
crashes and unexpected behavior occurs. E.g. connecting to a OpenSSH
server using the affected binary fails with:
ssh_dispatch_run_fatal: Connection to 192.168.10.171 port 22: incorrect
signature
Backport
From: Stefan Agner
Deals with two CVEs:
* bn_sqrx8x_internal carry bug on x86_64 (CVE-2017-3736)
* Malformed X.509 IPAddressFamily could cause OOB read (CVE-2017-3735)
Signed-off-by: Stefan Agner
Acked-by: Otavio Salvador
---
.../openssl/{openssl_1.1.0f.bb => openssl_1.1.0g.bb}
From: Stefan Agner
Deals with two CVEs:
* bn_sqrx8x_internal carry bug on x86_64 (CVE-2017-3736)
* Malformed X.509 IPAddressFamily could cause OOB read (CVE-2017-3735)
Signed-off-by: Stefan Agner
Acked-by: Otavio Salvador
---
Changes since v2:
- Rebased to rocko-next
.../0001-Fix-build-with-
From: Stefan Agner
When compiling OpenSSL with binutils 2.29 for ARM with Thumb2 enabled
crashes and unexpected behavior occurs. E.g. connecting to a OpenSSH
server using the affected binary fails with:
ssh_dispatch_run_fatal: Connection to 192.168.10.171 port 22: incorrect
signature
Backport
On Tue, Dec 19, 2017 at 01:19:09PM -0800, Andre McCurdy wrote:
> On Tue, Dec 19, 2017 at 12:54 PM, Tom Rini wrote:
> > On Tue, Dec 19, 2017 at 12:11:48PM -0800, Saul Wold wrote:
> >> We have seen more failures, but have not been able to directly reproduce
> >> it maybe svaing the rootfs and it con
On Tue, Dec 19, 2017 at 12:54 PM, Tom Rini wrote:
> On Tue, Dec 19, 2017 at 12:11:48PM -0800, Saul Wold wrote:
>> We have seen more failures, but have not been able to directly reproduce
>> it maybe svaing the rootfs and it contains some content that is tripping
>> up the e2fsprogs mkfs.ext4 popul
On Tue, Dec 19, 2017 at 12:11:48PM -0800, Saul Wold wrote:
> We have seen more failures, but have not been able to directly reproduce
> it maybe svaing the rootfs and it contains some content that is tripping
> up the e2fsprogs mkfs.ext4 populate_rootfs() function
>
> Signed-off-by: Saul Wold
> -
We have seen more failures, but have not been able to directly reproduce
it maybe svaing the rootfs and it contains some content that is tripping
up the e2fsprogs mkfs.ext4 populate_rootfs() function
Signed-off-by: Saul Wold
---
meta/classes/image_types.bbclass | 7 ++-
1 file changed, 6 ins
We search for packages related to the sdk environment
being used for a test.
Signed-off-by: Joe Slater
---
meta/lib/oeqa/sdk/cases/buildgalculator.py | 7 ---
meta/lib/oeqa/sdk/context.py | 15 +--
2 files changed, 17 insertions(+), 5 deletions(-)
diff --git a/met
On Tue, Dec 19, 2017 at 4:14 PM, Otavio Salvador
wrote:
> The 'wic' image may use files which has been deployed (e.g in
> do_deploy) for some partitions that may need to be copied in a
> specific partition or filesystem (e.g a bootloader).
>
> When using 'bitbake -c image_wic', from a clean build
On Tue, Dec 19, 2017 at 4:07 PM, Richard Purdie
wrote:
> On Tue, 2017-12-19 at 15:38 -0200, Otavio Salvador wrote:
>> On Tue, Dec 19, 2017 at 3:22 PM, Richard Purdie
>> wrote:
>> >
>> > On Tue, 2017-12-19 at 15:17 -0200, Otavio Salvador wrote:
>> > >
>> > > The 'wic' image may use files which has
The 'wic' image may use files which has been deployed (e.g in
do_deploy) for some partitions that may need to be copied in a
specific partition or filesystem (e.g a bootloader).
When using 'bitbake -c image_wic', from a clean build, the
contents of do_deploy must also be available so we need to e
On Tue, 2017-12-19 at 15:38 -0200, Otavio Salvador wrote:
> On Tue, Dec 19, 2017 at 3:22 PM, Richard Purdie
> wrote:
> >
> > On Tue, 2017-12-19 at 15:17 -0200, Otavio Salvador wrote:
> > >
> > > The 'wic' image may use files which has been deployed (e.g in
> > > do_deploy) for some partitions th
On Tue, Dec 19, 2017 at 3:22 PM, Richard Purdie
wrote:
> On Tue, 2017-12-19 at 15:17 -0200, Otavio Salvador wrote:
>> The 'wic' image may use files which has been deployed (e.g in
>> do_deploy) for some partitions that may need to be copied in a
>> specific partition or filesystem (e.g a bootloade
On Tue, 2017-12-19 at 15:17 -0200, Otavio Salvador wrote:
> The 'wic' image may use files which has been deployed (e.g in
> do_deploy) for some partitions that may need to be copied in a
> specific partition or filesystem (e.g a bootloader).
>
> When using 'bitbake -c image_wic', from a clean bui
The 'wic' image may use files which has been deployed (e.g in
do_deploy) for some partitions that may need to be copied in a
specific partition or filesystem (e.g a bootloader).
When using 'bitbake -c image_wic', from a clean build, the
contents of do_deploy must also be available so we need to e
Test case ID 1422 is not correct for this issue, the correct test
case ID for test_qemu is 1424.
Signed-off-by: Joshua Lock
---
meta/lib/oeqa/selftest/cases/wic.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/selftest/cases/wic.py
b/meta/lib/oeqa/selftest/ca
I've created
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12434
to track this issue.
I get this QA error now 100% reproducible when the "right" do_package
sstate archive is being used, but still haven't found the root cause (aka
why/how this bad sstate archive was created in first place).
On
From: Leonardo Sandoval
Run in parallel the (oe)selftests using GNU/Parallel: for each test
defined, a job will be launched and at any time at maximum of jobs
will be executing (defaults to 4).
1. Run all modules
parallel-oe-selftest.sh
2. Run certain modules and print results in order (se
On Mon, 18 Dec 2017 12:26:32 -0800
Andre McCurdy wrote:
> On Mon, Dec 18, 2017 at 9:43 AM,
> wrote:
> > From: Leonardo Sandoval
> >
> > Parallelize oe-selftest execution using GNU/Parallel: for each test
> > defined, a job will be launched and at any time at maximun of jobs will
>
> Typo.
>
The kernel class now sets RDEPENDS_${KERNEL_PACKAGE_NAME}-base so this include
needs to do the same, otherwise bitbake emits a warning and the kernel isn't
removed.
Signed-off-by: Ross Burton
---
meta/conf/machine/include/qemu.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, Dec 19, 2017 at 12:23 AM, ChenQi wrote:
> On 12/19/2017 12:45 PM, Bruce Ashfield wrote:
>>
>> On Mon, Dec 18, 2017 at 11:03 AM, Ross Burton
>> wrote:
>>>
>>> Hi,
>>>
>>> Another batch of patches from the list which have passed autobuilder
>>> testing and
>>> review.
>>>
>>> Ross
>>>
>>> T
Hi Richard
My target is a X86_64 camera, and I have only tried with it.
On Tue, Dec 19, 2017 at 12:08 PM, Richard Purdie
wrote:
> On Tue, 2017-12-12 at 09:23 -0800, Khem Raj wrote:
>> From: Ricardo Ribalda Delgado
>>
>> Without this patch libbacktrace cannot be included/link during
>> libgfortr
Thanks for the heads up. I'll pull the changeset into my testing branch
and touch up all the meta-python recipes to remove the now non-existent
packages.
On Tue, Dec 19, 2017 at 8:43 AM, Burton, Ross wrote:
> On 19 December 2017 at 13:23, Derek Straka wrote:
>
>> Cool. Works for me. Thanks.
On 19 December 2017 at 13:23, Derek Straka wrote:
> Cool. Works for me. Thanks.
>
There's an epic patch on the list which I'm reviewing right now that
drastically changes how the core Python library is packaged. If you'd like
to have a look, the almost-final (my bandaid fixes need to be squas
Signed-off-by: Alexander Kanavin
---
meta/conf/distro/include/maintainers.inc | 48
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 68542bbed9a..1c99201ab4a
Signed-off-by: Alexander Kanavin
---
meta/conf/distro/include/maintainers.inc | 17 -
1 file changed, 17 deletions(-)
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 1e7f249b611..68542bbed9a 100644
--- a/meta/conf/distro/inc
Cool. Works for me. Thanks.
-Derek
On Tue, Dec 19, 2017 at 8:12 AM, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> On 12/19/2017 02:31 PM, Derek Straka wrote:
>
>> Well, I've been able to do it just fine for the majority of packages in
>> meta-python by myself. Since I contri
On 12/19/2017 02:31 PM, Derek Straka wrote:
Well, I've been able to do it just fine for the majority of packages in
meta-python by myself. Since I contribute the majority of the patches
and maintain the layer, I want this capability maintained in
meta-python. If you plan on removing that func
From: Stefan Agner
The udhcpc script calls ip addr flush .. which flushes addresses
of any address family, including IPv6. However, busybox udhcpc is
IPv4 only and should not influence IPv6 addressing. Hence use ip
addr flush with family constrait.
The script particularly broke IPv6 SLAAC: Typic
There is a race with rm_work when tasks run deltask do_build since
do_rm_work becomes a floating task. Handle this by injecting
the populate_sysroot/lic dependencies manually if the tasks returned
are empty. This depends on a change to fix bb.build.preceedtask() in
bitbake too.
[YOCTO #12365]
Sig
Well, I've been able to do it just fine for the majority of packages in
meta-python by myself. Since I contribute the majority of the patches and
maintain the layer, I want this capability maintained in meta-python. If
you plan on removing that functionality in oe-core, I'd like to have the
oppor
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/buildoptions.py | 14 ++
1 file changed, 14 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/buildoptions.py
b/meta/lib/oeqa/selftest/cases/buildoptions.py
index cf221c3..e60e32d 100644
--- a/meta/lib/oeqa/selftes
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/archiver.py | 13 +
1 file changed, 13 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/archiver.py
b/meta/lib/oeqa/selftest/cases/archiver.py
index f61a522..0a6d4e3 100644
--- a/meta/lib/oeqa/selftest/cases/archi
In 6.x and 7.x gcc, libgfortran now needs libbacktrace. Enable building of this
so that libgfortran builds correctly.
[YOCTO #12394]
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/gcc/libgfortran.inc | 28 +---
1 file changed, 17 insertions(+), 11 deletions(-)
On Tue, Dec 12, 2017 at 03:54:04AM -0800, anelliot wrote:
> The wic help output formally consisted of manually created strings mixed with
> argparse,
> which wasunformatted and unusable. This fix cleans up the help messages,
> rewrites help
> functionality to use argparse, and adds functionality
On Tue, 2017-12-12 at 09:23 -0800, Khem Raj wrote:
> From: Ricardo Ribalda Delgado
>
> Without this patch libbacktrace cannot be included/link during
> libgfortran build.
>
> libbtool: link: cannot find the library
> `../libbacktrace/libbacktrace.la'
> or unhandled argument `../libbacktrace/libb
Related, the musl autobuilder failed like this:
ERROR: bind-9.11.2-r0 do_package_qa: QA Issue: /usr/sbin/dnssec-keymgr
contained in package bind requires
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-musl-x86-64/build/build/tmp/hosttools/python3,
but no providers found in RDEPENDS_bind? [
The Virtio Vring implementation in QEMU allows local OS guest users to
cause a denial of service (divide-by-zero error and QEMU process crash)
by unsetting vring alignment while updating Virtio rings.
Reference:
https://nvd.nist.gov/vuln/detail/CVE-2017-17381
Upstream patch:
https://git.qemu.org/
Update the SRC_URI to point to kernel.org location where
i2c-tools is hosted these days.
Remove Modules.mk since it was used for deprecated binaries
(eepromer, eeprom)
Added the following patches to fix races during build:
a) 0001-tools-Module.mk-Add-missing-dependencies.patch
b)
This recipe inherits nopackages but has a non-empty PACKAGES which confuses
the archiver class when:
INHERIT += "archiver"
ARCHIVER_MODE[srpm] = "1"
Ensuring PACKAGES is empty removes the errors that occur in this configuration.
[YOCTO #11121]
Signed-off-by: Richard Purdie
---
meta/recipes-ke
76 matches
Mail list logo
