On Wed, 2017-02-15 at 18:33 +0100, Geoffrey Levillain wrote:
> In order to keep do_install_overlay to reexecute it's needed to keep
> stamps of fetching tasks.
>
> Without that do_install_overlay would reexecute and do_image as well
> but
> do_image will crash since there is no rootfs.
>
> Signed
On Wed, 2017-02-15 at 18:33 +0100, Geoffrey Levillain wrote:
> There is often a need to add configuration files specific to an
> image,
> to simplify this process we can use a task.
>
> Fetching is set as noexec for images, but there is a need to fetch
> files
> here. This class permit to use do_f
On Fri, 2017-02-10 at 14:19 -0600, mariano.lo...@linux.intel.com wrote:
> From: Mariano Lopez
>
> package_qa task requires some tools installed in sysroot; with
> the introduction of recipe specific sysroot this task won't
> have such tools installed if it's forced to run.
>
> Signed-off-by: Mar
On 2017-02-15 18:33, Geoffrey Levillain wrote:
Hi,
These patches introduce a capability to install overlay into image after
fetching them.
There is actually a need to add image-specific configurations files into
image recipes, and these patches are a way to standardize this process as
well as s
From: Yi Zhao
There is a carry propagating bug in the Broadwell-specific Montgomery
multiplication procedure that handles input lengths divisible by, but
longer than 256 bits.
External References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7055
https://www.openssl.org/news/secadv/201
From: Alexandru Moise
If an SSL/TLS server or client is running on a 32-bit host, and a
specific cipher is being used, then a truncated packet can cause that
server or client to perform an out-of-bounds read, usually resulting
in a crash.
Backported from:
https://github.com/openssl/openssl/comm
From: Stefan Agner
Add packages for Marvells sd88xx SDIO WiFi firmwares.
Signed-off-by: Stefan Agner
---
.../recipes-kernel/linux-firmware/linux-firmware_git.bb | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmwa
From: Stefan Agner
Add packages for Marvells sd88xx SDIO WiFi firmwares.
Signed-off-by: Stefan Agner
---
.../recipes-kernel/linux-firmware/linux-firmware_git.bb | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmwa
zImage is the default KERNEL_IMAGETYPE_FOR_MAKE for non x86 fitImage.
On ARM64 architecture, zImage is not a valid kernel build target. This
change overrides KERNEL_IMAGETYPE_FOR_MAKE to Image on ARM64 platforms.
Cc: xe-ker...@external.cisco.com
Signed-off-by: Nikunj Kela
---
meta/classes/kernel
On 2/15/17 1:54 PM, Bryan Evenson wrote:
> For one project I'm using an Atmel AT91SAM9G25 processor, and I started when
> support for the chip wasn't fully integrated into the mainline kernel. As a
> result, I was using Atmel's Linux fork. Support has been in the mainline
> kernel for a whil
For one project I'm using an Atmel AT91SAM9G25 processor, and I started when
support for the chip wasn't fully integrated into the mainline kernel. As a
result, I was using Atmel's Linux fork. Support has been in the mainline
kernel for a while now, so in the middle of doing other updates I pl
Minimal update for swig
Signed-off-by: Edwin Plauchu
---
meta/recipes-devtools/swig/{swig_3.0.11.bb => swig_3.0.12.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/swig/{swig_3.0.11.bb => swig_3.0.12.bb} (58%)
diff --git a/meta/recipes-devtools/swig/sw
Resolves #11003
Adds oe-selftest for rootfs-pcbios-ext plugin
---
.../recipes-test/images/wic-image-single-ext.bb| 13 ++
.../recipes-test/images/wic-image-single-ext.wks | 6 +
meta/lib/oeqa/selftest/wic.py | 22
.../lib/wic/plugins/source/rootfs_pcbios_ext.py
On Wed, Feb 15, 2017 at 03:03:41AM +, Nikunj Kela wrote:
> Allow the load address for the FDT segment in the fitImage. This
> allows U-Boot to load the FDT at a specific address.
>
> UBOOT_FDT_LOADADDRESS - Specifies the load address used by u-boot
> for the FDT
>
> Signed-off-
Are all changes necessary for this to work already in master?
Yesterday I've noticed that rm_work for some components which are early in
the dependency (like qtbase) are executed relatively late (together with
do_package_qa).
So I've tried very naive way to find out if the rm_work tasks are execu
Minimal update for swig
Signed-off-by: Edwin Plauchu
---
meta/recipes-devtools/swig/{swig_3.0.11.bb => swig_3.0.12.bb} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/recipes-devtools/swig/{swig_3.0.11.bb => swig_3.0.12.bb} (100%)
diff --git a/meta/recipes-devtools/swig/swig_3
In order to keep do_install_overlay to reexecute it's needed to keep
stamps of fetching tasks.
Without that do_install_overlay would reexecute and do_image as well but
do_image will crash since there is no rootfs.
Signed-off-by: Geoffrey Levillain
---
meta/classes/rm_work.bbclass | 4
1 fi
There is often a need to add configuration files specific to an image,
to simplify this process we can use a task.
Fetching is set as noexec for images, but there is a need to fetch files
here. This class permit to use do_fetch, do_unpack and do_patch in order
to get your image-specific overlays t
If there is a user-defined licence there is no need to enforce MIT
licence instead. Therefor we set MIT if there is no licence defined.
Note : It also permit to set the licence before inherit image
in overlayable images (where a licence is needed because of the files
associated to the image).
Sig
Hi,
These patches introduce a capability to install overlay into image after
fetching them.
There is actually a need to add image-specific configurations files into
image recipes, and these patches are a way to standardize this process as
well as simplify it by re-enabling fetching when image_ove
On Wed, 2017-02-15 at 06:21 +, Wold, Saul wrote:
> This should also be applied Morty please
Whilst we can likely do this in master, it does have side effects you
aren't highlighting. You're making the kernel version check default for
*all* kernels linux-yocto or otherwise. This is a significan
There is often a need to add configuration files specific to an image,
to simplify this process we can use a task.
Fetching is set as noexec for images, but there is a need to fetch files
here. This class permit to use do_fetch, do_unpack and do_patch in order
to get your image-specific overlays t
In order to keep do_install_overlay to reexecute it's needed to keep
stamps of fetching tasks.
Without that do_install_overlay would reexecute and do_image as well but
do_image will crash since there is no rootfs.
Signed-off-by: Geoffrey Levillain
---
meta/classes/rm_work.bbclass | 4
1 fi
If there is a user-defined licence there is no need to enforce MIT
licence instead. Therefor we set MIT if there is no licence defined.
Note : It also permit to set the licence before inherit image
in overlayable images (where a licence is needed because of the files
associated to the image).
Sig
[PATCH 1/3] No need to force image licence on MIT
[PATCH 2/3] Add possibility to install overlays to image through a class
[PATCH 3/3] Do not remove fetching and install_overlay stamps
These patches introduce a capability to install overlay into image after
fetching them.
There is actually a need
On 02/15/2017 01:18 PM, André Draszik wrote:
Was there a specific reason to switch from rpm -e --nodeps to (the
differently-working) dnf remove?
No specific reason, just rewriting the code from scratch, coupled with
poorly documented API for the class. There's too much cruft in the old
code,
On 02/15/2017 12:28 PM, André Draszik wrote:
Shouldn't there be a package that actually RPROVIDES /bin/sh, rather than
having to add a fake RPROVIDES?
I tried that approach first, with a fake-sdkdeps package. It's too
complicated to make it work with nativesdk packages and still have all
the
On Wed, 2017-02-15 at 12:51 +0200, avalluri wrote:
>
> On 15.02.2017 12:36, André Draszik wrote:
> > What about opkg - is it OK with PATHs (my blind guess would be no)? Has
> > it
> > been tested?
>
> Yes, i tested wit 'ipk' packaging, it did not complain about file paths.
OK, thanks :-)
Cheers
On Mon, 2017-02-13 at 17:05 +0200, Alexander Kanavin wrote:
> To properly look at this patch, you probably need a side-by-side diff
> viewing tool.
I don't normally use rpm, but it seems to me that the new 'remove' is not
right.
Looking at the description, clean_requirements_on_remove is meant to
On 15.02.2017 12:36, André Draszik wrote:
On Mon, 2017-02-13 at 17:06 +0200, Alexander Kanavin wrote:
From: Amarnath Valluri
Unlike rpm, debian packaging does not allow file paths in 'Provides:'
field.
When 'usrmerge' distro feature enabled bash/busybox packages adds
'/bin/sh' to
it's RPROVID
Add .xz to the list of extensions recognized by patch_path(), so that
compressed patches ending in .patch.xz or .diff.xz are automatically
applied.
Signed-off-by: Dominic Sacré
---
meta/lib/oe/patch.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oe/patch.py b/met
Incorrect data was printed (recipe name instead of epoch number) when
displaying changes in epoch.
Signed-off-by: Markus Lehtonen
---
scripts/buildstats-diff | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/buildstats-diff b/scripts/buildstats-diff
index 5cea184..adeba
On Mon, 2017-02-13 at 17:06 +0200, Alexander Kanavin wrote:
> From: Amarnath Valluri
>
> Unlike rpm, debian packaging does not allow file paths in 'Provides:'
> field.
> When 'usrmerge' distro feature enabled bash/busybox packages adds
> '/bin/sh' to
> it's RPROVIDES to satisfy build dependencies
On Mon, 2017-02-13 at 17:06 +0200, Alexander Kanavin wrote:
> nativesdk-* rpm packages all require /bin/sh because postinst scriptlets
> are run with it. We can either teach rpm4 and dnf to ignore that
> dependency
> (a lot of non-upstreamable work), or add auto-satisfy the dependency
> in each pac
On Mon, 2017-02-13 at 17:06 +0200, Alexander Kanavin wrote:
> dnf insists that it cannot be done:
>
> Error: package libglib-2.0-0-1:2.50.2-r0.i586 requires /bin/sh, but none
> of the providers can be installed
> - package libdnf1-0.2.3+git0+367545629c-r0.i586 requires libglib-2.0-0
> >= 2.50.2,
[NVD] -- https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6131
The demangler in GNU Libiberty allows remote attackers to cause a denial
of service (infinite loop, stack overflow, and crash) via a cycle in the
references of remembered mangled types.
[BZ #71696] -- https://gcc.gnu.org/bugz
On 02/15/2017 11:10 AM, Anders Darander wrote:
Well, if the qemu emulation isn't working for a particular target, but
might work for another target, the post_install script can't be moved to
pkg_postinst_ontarget_${PN} anyway, it'll break ro-rootfs for the 2nd
machine as well..
You still seem t
[NVD] -- https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6131
The demangler in GNU Libiberty allows remote attackers to cause a denial
of service (infinite loop, stack overflow, and crash) via a cycle in the
references of remembered mangled types.
[BZ #71696] -- https://gcc.gnu.org/bugz
* Alexander Kanavin [170215 10:01]:
> On 02/15/2017 10:17 AM, Anders Darander wrote:
> > How will this be handled when using ro-rootfs?
> Same as it's handled now: by halting bitbake. See the email I just wrote to
> the oe-arch list for details.
> > We don't need to make it easier to write on-f
On 15 February 2017 at 00:42, Martin Jansa wrote:
> On Tue, Feb 14, 2017 at 11:54:58AM +0200, Jussi Kukkonen wrote:
> > * New feature release with lots of changes
> > * Versioning change (17 as in 2017, no longer relates to GL bumps)
>
> There is also this paragraph in release notes:
> https://ww
Replaced sys.exit with raising WicError in main module.
Signed-off-by: Ed Bartosh
---
scripts/wic | 56 +++-
1 file changed, 23 insertions(+), 33 deletions(-)
diff --git a/scripts/wic b/scripts/wic
index b12c743..b8be5b8 100755
--- a/scripts/w
There is no need to raise special exceptions. Raising
WicError should be enough.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/plugin.py | 4 ++--
scripts/lib/wic/plugins/imager/direct.py| 6 +++---
scripts/lib/wic/plugins/source/bootimg-pcbios.py| 4 ++-
Removed unused exceptions from error.py
Moved definition of WicError to lib/wic/__init__.py
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/__init__.py| 20 +++
scripts/lib/wic/engine.py | 2 +-
scripts/lib/wic/errors.py
Replaced sys.exit with raising WicError in wic plugins.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/plugins/imager/direct.py | 6 +--
scripts/lib/wic/plugins/source/bootimg-efi.py | 32 +--
.../lib/wic/plugins/source/bootimg-partition.py| 11 ++--
scripts/lib/wic/pl
Replaced msger with wic logger in the core wic modules.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/engine.py | 19 ++-
scripts/lib/wic/help.py | 8 +++--
scripts/lib/wic/ksparser.py | 7 ++--
scripts/lib/wic/partition.py| 72 +++-
Replaced sys.exit with raising WicError in the core wic modules.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/engine.py | 21 ---
scripts/lib/wic/partition.py| 46 +++--
scripts/lib/wic/utils/misc.py | 6 +++---
scripts/lib/wic/ut
Moved from lib/wic/utils/ to lib/wic as this is a core module.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/{utils => }/errors.py | 0
scripts/lib/wic/plugin.py | 4 ++--
scripts/lib/wic/plugins/imager/direct.py| 2 +-
scripts/lib/wic/plugins/
Replaced msger with wic logger in the direct plugin.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/plugins/imager/direct.py | 83 +---
1 file changed, 43 insertions(+), 40 deletions(-)
diff --git a/scripts/lib/wic/plugins/imager/direct.py
b/scripts/lib/wic/plugins/i
Removed custom logger module msger as it's replaced
by wic logger.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/engine.py | 4 -
scripts/lib/wic/msger.py | 209 --
2 files changed, 213 deletions(-)
delete mode 100644 scripts/lib/wic/msger.py
diff
Replaced msger with wic logger in wic source plugins.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/plugins/source/bootimg-efi.py | 60 --
.../lib/wic/plugins/source/bootimg-partition.py| 28 ---
scripts/lib/wic/plugins/source/bootimg-pcbios.py | 41 +
scripts/
On 02/15/2017 10:17 AM, Anders Darander wrote:
How will this be handled when using ro-rootfs?
Same as it's handled now: by halting bitbake. See the email I just wrote
to the oe-arch list for details.
We don't need to make it easier to write on-first-boot only post_install
scripts, rather, t
Set up wic logger using standerd logging module.
This is going to replace custom msger module.
Signed-off-by: Ed Bartosh
---
scripts/wic | 77 +++--
1 file changed, 44 insertions(+), 33 deletions(-)
diff --git a/scripts/wic b/scripts/wic
i
Hi,
This patchset takes care of logging and error handling:
- remove custom msger module in favor of standard python logging
- raise WicError exception instead of calling sys.exit
This is the one of the last changes for this time.
I'm thinking about refactoring wic plugin system, but haven't dec
* Alexander Kanavin [170213 16:08]:
> All commands that cannot be executed during cross-install and can only be run
> on target
> should go into this function. They will only be executed on first boot (if
> package was
> cross-installed) or immediately during package installation on target.
Ho
54 matches
Mail list logo
