Re: [OE-core] ✗ patchtest: failure for Fixes for eSDK and testsdkext

On 11/17/2016 05:02 PM, Burton, Ross wrote: On 17 November 2016 at 06:55, Patchwork > wrote: * Patch[7/8] oeqa/sdkext/devtool.py: skip test_extend_autotools_recipe_creation when no libxml2

Re: [OE-core] [PATCH] devtool: execute associated functions while preparing the source tree

On Monday, November 28, 2016 11:04:40 PM Christopher Larson wrote: > This will do the commit after the first postfunc is done, so won’t the > changes from the main func and the first postfunc both be included in that > commit? I suppose all changes from the main func have already been committed

[OE-core] [PATCH 4/5] runqemu: support mutiple qemus running when nfs

Fixed: * In build1: $ runqemu nfs qemux86-64 In build2: $ runqemu nfs qemux86-64 It would fail before since the port numerbs and conf files are conflicted, now make runqemu-export-rootfs work together with runqemu to fix the problem. * And we don't need export PSEUDO_LOCALSTATEDIR in

[OE-core] [PATCH 5/5] runqemu: set default device and hostfwd for slirp

There is no network rather than lo whitout set device, so set it by default. And set hostfwd: -> 22, 2323 -> 23 [YOCTO #7887] Signed-off-by: Robert Yang --- meta/conf/machine/include/qemuboot-x86.inc | 1 - meta/conf/machine/qemuarm64.conf | 1 -

[OE-core] [PATCH 2/5] qemuboot.bbclass: use IMGDEPLOYDIR

So that "bitbake -ccleansstate" can remove qemuboot.conf Signed-off-by: Robert Yang --- meta/classes/qemuboot.bbclass | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass index

[OE-core] [PATCH 0/5] runqemu: fixes for cpio.gz, nfs and slirp

The following changes since commit af280990bff4a484fd8a18e3442b56a0a39b7611: Revert "classes/populate_sdk_ext: require uninative" (2016-11-28 14:49:37 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/qemu

[OE-core] [PATCH 3/5] runqemu-export-rootfs: fix inconsistent var names

Fixed: $ runqemu nfs qemux86-64 [snip] On your target please remember to add the following options for NFS nfsroot=IP_ADDRESS:/path/to/nfsroot,nfsvers=3,port=,mountprog=,nfsprog=,udp,mountport= [snip] Note that the values are null, this is because their var names are inconsistent. [YOCTO #10519]

[OE-core] [PATCH 1/5] runqemu: fix checking for .cpio.gz

When "runqemu /path/to/.cpio.gz", it used the last suffix "gz" as the fstype which was wrong. Check filename against self.fstypes firstly can fix the problem. Signed-off-by: Robert Yang --- scripts/runqemu | 22 -- 1 file changed, 16 insertions(+),

Re: [OE-core] [PATCH 2/2] base-passwd: set root's default password to 'root'

On Tue, 29 Nov 2016 13:36:58 Robert Yang wrote: > On 11/29/2016 11:45 AM, Paul Eggleton wrote: > > On Tue, 29 Nov 2016 10:45:51 Robert Yang wrote: > >> We may also need something like IMAGE_FEATURES += "test" to make it can > >> work with -ctestimage. > > > > Not sure I follow your reasoning here

Re: [OE-core] [PATCH] qemu*.conf: Add slirp support for all qemu machines

On 11/29/2016 04:11 AM, Randy Witt wrote: This patch also moves the "-net user" part out of the config and into runqemu. This is done because the "-net user" portion isn't machine specific, and it contains what ports to forward. [ YOCTO #7887 ] Signed-off-by: Randy Witt

Re: [OE-core] [PATCH] devtool: execute associated functions while preparing the source tree

On Mon, Nov 28, 2016 at 7:59 PM, Jiajie Hu wrote: > Execute prefuncs and postfuncs associated with the task while preparing > the source tree. If any changes are made to the source tree by these > prefuncs or postfuncs, a separate commit will be created so that the > changes

Re: [OE-core] [PATCH 2/2] base-passwd: set root's default password to 'root'

On 11/29/2016 11:45 AM, Paul Eggleton wrote: On Tue, 29 Nov 2016 10:45:51 Robert Yang wrote: On 11/29/2016 09:57 AM, Khem Raj wrote: On Nov 24, 2016, at 10:59 AM, Paul Eggleton wrote:>> On Thu, 24 Nov 2016 08:46:29 Patrick Ohly wrote: On Thu, 2016-11-24 at

Re: [OE-core] [PATCH 2/2] base-passwd: set root's default password to 'root'

On Tue, 29 Nov 2016 10:45:51 Robert Yang wrote: > On 11/29/2016 09:57 AM, Khem Raj wrote: > >> On Nov 24, 2016, at 10:59 AM, Paul Eggleton > >> wrote:>> > >> On Thu, 24 Nov 2016 08:46:29 Patrick Ohly wrote: > >>> On Thu, 2016-11-24 at 11:38 +0800, Robert Yang

[OE-core] [PATCH] devtool: execute associated functions while preparing the source tree

Execute prefuncs and postfuncs associated with the task while preparing the source tree. If any changes are made to the source tree by these prefuncs or postfuncs, a separate commit will be created so that the changes won't get incorporated with other patches. Signed-off-by: Jiajie Hu

Re: [OE-core] [PATCH 2/2] base-passwd: set root's default password to 'root'

On 11/29/2016 09:57 AM, Khem Raj wrote: On Nov 24, 2016, at 10:59 AM, Paul Eggleton wrote: On Thu, 24 Nov 2016 08:46:29 Patrick Ohly wrote: On Thu, 2016-11-24 at 11:38 +0800, Robert Yang wrote: Currently, debug-tweaks is in EXTRA_IMAGE_FEATURES by default

Re: [OE-core] Kernel: Builds use old version of defconfig

> On Nov 24, 2016, at 5:55 AM, Bruce Ashfield wrote: > > > > On Thu, Nov 24, 2016 at 5:32 AM, Mike Looijmans > wrote: > On 24-11-16 11:10, Mike Looijmans wrote: > I'm currently experiencing a problem with

Re: [OE-core] [PATCH 2/2] base-passwd: set root's default password to 'root'

> On Nov 24, 2016, at 10:59 AM, Paul Eggleton > wrote: > > On Thu, 24 Nov 2016 08:46:29 Patrick Ohly wrote: >> On Thu, 2016-11-24 at 11:38 +0800, Robert Yang wrote: >>> Currently, debug-tweaks is in EXTRA_IMAGE_FEATURES by default for poky, >>> and >>> there is

[OE-core] [PATCH 0/1] multilib.bbclass: update DEFAULTTUNE for image recipe

The following changes since commit af280990bff4a484fd8a18e3442b56a0a39b7611: Revert "classes/populate_sdk_ext: require uninative" (2016-11-28 14:49:37 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/img

[OE-core] [PATCH 1/1] multilib.bbclass: update DEFAULTTUNE for image recipe

Fixed: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake -e lib32-core-image-minimal | grep ^TUNE_ARCH= TUNE_ARCH="x86_64" This is incorrect, it should be i686 (or other 32 bit tunes), this makes we can't

Re: [OE-core] [PATCH] base.bbclass: squash whitespace when printing BUILDCFG_VARS

On Mon, 2016-11-28 at 16:53 -0700, Christopher Larson wrote: > > On Mon, Nov 28, 2016 at 3:23 PM, Andre McCurdy > wrote: > > TUNE_FEATURES for ARM targets typically contains a lot of > > whitespace > > due to refactoring in OE 2.1: > > > >  

Re: [OE-core] [PATCH] base.bbclass: squash whitespace when printing BUILDCFG_VARS

On Mon, Nov 28, 2016 at 3:53 PM, Christopher Larson wrote: > > On Mon, Nov 28, 2016 at 3:23 PM, Andre McCurdy wrote: >> >> TUNE_FEATURES for ARM targets typically contains a lot of whitespace >> due to refactoring in OE 2.1: >> >>

Re: [OE-core] [PATCH] base.bbclass: squash whitespace when printing BUILDCFG_VARS

On Mon, Nov 28, 2016 at 3:23 PM, Andre McCurdy wrote: > TUNE_FEATURES for ARM targets typically contains a lot of whitespace > due to refactoring in OE 2.1: > > http://git.openembedded.org/openembedded-core/commit/?id= > f774b44fa007a2a756ada892ede832b1251d940c > > Squash

Re: [OE-core] [PATCH 06/18] cmake: update to 3.7.0

> On Nov 28, 2016, at 5:34 AM, Alexander Kanavin > wrote: > > License is still 3-clause BSD. OK. what triggered the checksum change then ? > > Signed-off-by: Alexander Kanavin > --- > .../cmake/{cmake-native_3.6.2.bb =>

Re: [OE-core] [PATCH V2] scripts.send-pull-request: Avoid multiple chain headers

On 11/28/2016 03:34 PM, Patrick Ohly wrote: > On Mon, 2016-11-28 at 14:28 -0600, Jose Lamego wrote: >> Agree. Please provide feedback about below comments and I will submit a >> v3 patch. >> >> On 11/28/2016 01:47 PM, Patrick Ohly wrote: >>> On Mon, 2016-11-28 at 10:23 -0600, Jose Lamego wrote:

[OE-core] [PATCH] base.bbclass: squash whitespace when printing BUILDCFG_VARS

TUNE_FEATURES for ARM targets typically contains a lot of whitespace due to refactoring in OE 2.1: http://git.openembedded.org/openembedded-core/commit/?id=f774b44fa007a2a756ada892ede832b1251d940c Squash whitespace when displaying BUILDCFG_VARS in buildcfg_vars(). Signed-off-by: Andre

Re: [OE-core] [PATCH V2] scripts.send-pull-request: Avoid multiple chain headers

On Mon, 2016-11-28 at 14:28 -0600, Jose Lamego wrote: > Agree. Please provide feedback about below comments and I will submit a > v3 patch. > > On 11/28/2016 01:47 PM, Patrick Ohly wrote: > > On Mon, 2016-11-28 at 10:23 -0600, Jose Lamego wrote: > More than 1 "In-Reply-To" and "References"

[OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232

* Drop support for rcS.d SysV init scripts. These are prone to cause dependency loops, and almost all packages with rcS scripts now ship a native systemd service. * Drop mount propagation patch, it only happens with libseccomp, OE doesnt enable it * kdbus option has disappeared from

Re: [OE-core] [PATCH V2] scripts.send-pull-request: Avoid multiple chain headers

Agree. Please provide feedback about below comments and I will submit a v3 patch. On 11/28/2016 01:47 PM, Patrick Ohly wrote: > On Mon, 2016-11-28 at 10:23 -0600, Jose Lamego wrote: More than 1 "In-Reply-To" and "References" message headers are in violation of rfc2822 [1] and may cause that some

[OE-core] [PATCH] qemu*.conf: Add slirp support for all qemu machines

This patch also moves the "-net user" part out of the config and into runqemu. This is done because the "-net user" portion isn't machine specific, and it contains what ports to forward. [ YOCTO #7887 ] Signed-off-by: Randy Witt ---

Re: [OE-core] [PATCH V2] scripts.send-pull-request: Avoid multiple chain headers

On Mon, 2016-11-28 at 10:23 -0600, Jose Lamego wrote: > When creating a patch set with cover letter using the > send-pull-request script, both the "In-Reply-To" and "References" > headers are appended twice in patch 2 and subsequent. The "why" part is missing in the commit header. "Why" is

Re: [OE-core] [PATCH V3 2/2] systemd: Upgrade to 232

On Mon, Nov 28, 2016 at 2:12 AM, Burton, Ross wrote: > 0001-use-lnr-wrapper-instead-of-looking-for-relative-opti.patch I synced this patch with systemd-232 and sent out V4. I did bitbake systemd-boot on turbot and it surprisingly build without seeing these patch failures.

[OE-core] [PATCH 2/2 V4] systemd: Upgrade to 232

* Drop support for rcS.d SysV init scripts. These are prone to cause dependency loops, and almost all packages with rcS scripts now ship a native systemd service. * Drop mount propagation patch, it only happens with libseccomp, OE doesnt enable it * kdbus option has disappeared from

[OE-core] [PATCH] buildhistory-diff: report directory renames

The script detects directory renaming if two different directories with the same set of files are added and removed. [YOCTO #10691] Signed-off-by: Ed Bartosh --- meta/lib/oe/buildhistory_analysis.py | 34 +++--- 1 file changed, 31

[OE-core] [PATCH V2] scripts.send-pull-request: Avoid multiple chain headers

When creating a patch set with cover letter using the send-pull-request script, both the "In-Reply-To" and "References" headers are appended twice in patch 2 and subsequent. This change appends only one header pointing to very first patch in series or to cover letter if available. [YOCTO #10718]

[OE-core] [PATCH v4] classes: Fix alternatives and rc.d ordering

Changes since v3: * Count the number of lines produced by update-alternatives to detect if lines were inserted. Failing to do so introduced bugs in native packages (e.g. binutils-cross-canadian-arm) -- ___ Openembedded-core

[OE-core] [PATCH] classes: Fix alternatives and rc.d ordering

When using an alternative as an initscript, the ordering between update-rc.d and update-alternatives tasks during prerm and postinst tasks must always be the following in order to work: * prerm: - stop daemon - remove alternative * postinst: - add alternative - start daemon

[OE-core] Yocto Project Status WW49

Current Dev Position: YP 2.3 M1 Next Deadline: YP 2.3 M1 by Dec. 12, 2016 SWAT team rotation: Juro -> Anibal https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: *We are switching these reports to Monday instead of Friday, at least for the next month

[OE-core] [PATCH 08/11] pybootchartgui: render disk space usage

This adds a new, separate chart showing the amount of disk space used over time for each volume monitored during the build. The hight of the graph entries represents the delta between current usage and minimal usage during the build. That's more useful than showing just the current usage, because

[OE-core] [PATCH 07/11] pybootchartgui/parsing.py: fix error handling in meminfo parser

When matching fails, m.group(0) is invalid and can't be used in the error message. Signed-off-by: Patrick Ohly --- scripts/pybootchartgui/pybootchartgui/parsing.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 10/11] buildstats: reduce amount of data stored for system utilization

Pre-processing /proc data during the build considerably reduces the amount of data written to disk: 176KB instead of 4.7MB for a 20 minuted build. Parsing also becomes faster. The disk monitor log added another 16KB in that example build. The overall buildstat was 20MB, so the overhead for

[OE-core] [PATCH 09/11] pybootchartgui: simplify drawing of memory usage

The internal representation after parsing now matches exactly what the drawing code needs, thus speeding up drawing a bit. However, the main motivation is to store exactly that required information in a more compact file. Signed-off-by: Patrick Ohly ---

[OE-core] [PATCH 11/11] pybootchartgui: support reading reduced /proc logs

Pre-processing /proc data during the build considerably reduces the amount of data written to disk: 176KB instead of 4.7MB for a 20 minuted build. Parsing also becomes faster. buildstats.bbclass only writes the reduced logs now, but support for the full /proc files is kept around as reference.

[OE-core] [PATCH 06/11] buildstats: record disk space usage

Hooks into the new monitordisk.py event and records the used space for each volume. That is probably the only relevant value when it comes to visualizing the build and recording more would only increase disk usage. Signed-off-by: Patrick Ohly ---

[OE-core] [PATCH 04/11] pybootchartgui: show system utilization

This enables rendering of the original bootchart charts for CPU, disk and memory usage. It depends on the /proc samples recorded by the updated buildstats.bbclass. Currently, empty charts CPU and disk usage charts are drawn if that data is not present; the memory chart already gets skipped when

[OE-core] [PATCH 05/11] pybootchartgui/draw.py: skip empty CPU and disk usage charts

The only real change is the addition of two if checks that skips the corresponding drawing code when there is no data. Signed-off-by: Patrick Ohly --- scripts/pybootchartgui/pybootchartgui/draw.py | 98 ++- 1 file changed, 50 insertions(+), 48

[OE-core] [PATCH 00/11] system statistics sampling

These patches depend on the corresponding patches to bitbake. buildstats.bbclass gets extended so that disk bandwidth and capacity, CPU and memory usage get sampled at regular time intervals by default. pybootchart had code for most of that data, which gets restored and re-enabled. The disk

[OE-core] [PATCH 03/11] pybootchartgui/draw.py: fix drawing of samples not starting at zero

The code did not handle x scaling correctly when drawing starts at some time larger than zero, i.e. it worked for normal bootchart data, but not for the system statistics recorded by buildstats.bbclass. Signed-off-by: Patrick Ohly ---

[OE-core] [PATCH 01/11] buildstats: add system state sampling

/proc/[diskstats|meminfo|stat] get sampled and written to the same proc_.log files as during normal bootchat logging. This will allow rendering the CPU, disk and memory usage charts. Right now sampling happens once a second, triggered by the heartbeat event.That produces quite a bit of data for

[OE-core] [PATCH 02/11] pybootchartgui/draw.py: allow moving process chart up and down

Substracting curr_y when determining the hight of the process chart is wrong because the height is independent of the position where the chart is about to be drawn. It happens to work at the moment because curr_y is always 10 when render_processes_chart() gets called. But it leads to a negative

Re: [OE-core] ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages"

On 28 November 2016 at 13:17, Patrick Ohly wrote: > I recently ran into a third usage of "file-native": swupd-server links > against libmagic from file and therefore has a DEPENDS = "file". But > building swupd-server-native didn't actually build file because of >

Re: [OE-core] ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages"

On Mon, 2016-11-28 at 14:17 +0100, Patrick Ohly wrote: > I recently ran into a third usage of "file-native": swupd-server > links against libmagic from file and therefore has a DEPENDS = > "file". But building swupd-server-native didn't actually build file > because of ASSUME_PROVIDED and because

[OE-core] [PATCH 18/18] ffmpeg: update to 3.2.1

Signed-off-by: Alexander Kanavin --- meta/recipes-multimedia/ffmpeg/{ffmpeg_3.2.bb => ffmpeg_3.2.1.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-multimedia/ffmpeg/{ffmpeg_3.2.bb => ffmpeg_3.2.1.bb} (97%) diff --git

[OE-core] [PATCH 15/18] rng-tools: use SOURCEFORGE_MIRROR in SRC_URI

This also fixes upstream version check. Signed-off-by: Alexander Kanavin --- meta/recipes-support/rng-tools/rng-tools_5.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-support/rng-tools/rng-tools_5.bb

[OE-core] [PATCH 17/18] epiphany: update to 3.22.3

Signed-off-by: Alexander Kanavin --- .../recipes-gnome/epiphany/{epiphany_3.22.1.bb => epiphany_3.22.3.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-gnome/epiphany/{epiphany_3.22.1.bb => epiphany_3.22.3.bb} (82%) diff

[OE-core] [PATCH 16/18] webkitgtk: update to 2.14.2

From: Carlos Alberto Lopez Perez Signed-off-by: Carlos Alberto Lopez Perez Signed-off-by: Alexander Kanavin --- meta/recipes-sato/webkit/{webkitgtk_2.14.1.bb => webkitgtk_2.14.2.bb} | 4 ++-- 1 file changed, 2

[OE-core] [PATCH 11/18] iso-codes: update to 3.71

Signed-off-by: Alexander Kanavin --- .../iso-codes/{iso-codes_3.70.bb => iso-codes_3.71.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-support/iso-codes/{iso-codes_3.70.bb => iso-codes_3.71.bb} (76%) diff

[OE-core] [PATCH 14/18] vala: update to 0.34.3

Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/vala/{vala_0.34.2.bb => vala_0.34.3.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-devtools/vala/{vala_0.34.2.bb => vala_0.34.3.bb} (56%) diff --git

[OE-core] [PATCH 10/18] gobject-introspection: update to 1.50.0

Signed-off-by: Alexander Kanavin --- ...ject-introspection_1.48.0.bb => gobject-introspection_1.50.0.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-gnome/gobject-introspection/{gobject-introspection_1.48.0.bb =>

[OE-core] [PATCH 13/18] npth: update to 1.3

Signed-off-by: Alexander Kanavin --- meta/recipes-support/npth/{npth_1.2.bb => npth_1.3.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-support/npth/{npth_1.2.bb => npth_1.3.bb} (81%) diff --git

[OE-core] [PATCH 12/18] msmtp: update to 1.6.6

Signed-off-by: Alexander Kanavin --- meta/recipes-extended/msmtp/{msmtp_1.6.5.bb => msmtp_1.6.6.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/msmtp/{msmtp_1.6.5.bb => msmtp_1.6.6.bb} (86%) diff --git

[OE-core] [PATCH 09/18] gnutls: update to 3.5.6

Signed-off-by: Alexander Kanavin --- meta/recipes-support/gnutls/{gnutls_3.5.5.bb => gnutls_3.5.6.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-support/gnutls/{gnutls_3.5.5.bb => gnutls_3.5.6.bb} (60%) diff --git

[OE-core] [PATCH 08/18] upstream-version-is-even.bbclass: ensure that the full version is matched.

Previously 4.3.2.1 would match as 3.2.1. Signed-off-by: Alexander Kanavin --- meta/classes/upstream-version-is-even.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/upstream-version-is-even.bbclass

[OE-core] [PATCH 07/18] gnome-desktop3: update to 3.22.2

Signed-off-by: Alexander Kanavin --- .../{gnome-desktop3_3.22.1.bb => gnome-desktop3_3.22.2.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-gnome/gnome-desktop/{gnome-desktop3_3.22.1.bb => gnome-desktop3_3.22.2.bb}

[OE-core] [PATCH 05/18] lighttpd: upgrade to 1.4.43

lighttpd no longer builds modules for which dependencies are not present, so some previously available modules are no more. Signed-off-by: Alexander Kanavin --- .../lighttpd/{lighttpd_1.4.42.bb => lighttpd_1.4.43.bb} | 4 ++-- 1 file changed, 2

[OE-core] [PATCH 02/18] sysprof: update to 3.22.2

Drop 0001-Forward-port-mips-arm-memory-barrier-patches.patch; upstream is using standard C11 facilities for this now. Drop 0001-callgraph-Use-U64_TO_POINTER.patch; it has been merged upstream. Signed-off-by: Alexander Kanavin ---

[OE-core] [PATCH 06/18] cmake: update to 3.7.0

License is still 3-clause BSD. Signed-off-by: Alexander Kanavin --- .../cmake/{cmake-native_3.6.2.bb => cmake-native_3.7.0.bb}| 1 + meta/recipes-devtools/cmake/cmake.inc | 8

[OE-core] [PATCH 00/18] Recipe version updates

Various stuff that has piled up over the past few weeks. Epiphany update requires also webkitgtk update, so that patch is included, just in case. The following changes since commit 12a0ee049e453b6d0d2ce2f3fa981d1b6e02bd78: dev-manual: Added note about RPM not dealing with post-install

[OE-core] [PATCH 03/18] btrfs-tools: update to 4.8.4

Signed-off-by: Alexander Kanavin --- .../btrfs-tools/{btrfs-tools_4.8.2.bb => btrfs-tools_4.8.4.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_4.8.2.bb => btrfs-tools_4.8.4.bb} (95%)

[OE-core] [PATCH 01/18] icu: update to 58.1

The copyright for the software has been transferred to Unicode Inc from IBM, but the terms are same. libiculx and libicule are no longer produced as they depend on an external package icu-le-hb (previous versions had an option of using an internal implementation which now has been dropped). I

[OE-core] [PATCH 04/18] ca-certificates: upgrade to 20161102

Signed-off-by: Alexander Kanavin --- .../{ca-certificates_20160104.bb => ca-certificates_20161102.bb}| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-support/ca-certificates/{ca-certificates_20160104.bb =>

Re: [OE-core] ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages"

On Mon, 2016-11-28 at 12:04 +, Richard Purdie wrote: > On Mon, 2016-11-28 at 06:20 -0500, Robert P. J. Day wrote: > > a bit confused by what i'm seeing in a recent > > qemuppc/core-image-minimal build on my fedora system regarding which > > native packages are built, despite what's in

Re: [OE-core] ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages"

On Mon, 2016-11-28 at 06:20 -0500, Robert P. J. Day wrote: >   a bit confused by what i'm seeing in a recent > qemuppc/core-image-minimal build on my fedora system regarding which > native packages are built, despite what's in bitbake.conf (using > current poky layer checkout). > >   first,

Re: [OE-core] npm.bbclass support for deep native modules?

On 28/11/16 10:35, Peter A. Bigot wrote: On 11/28/2016 04:11 AM, Paul Eggleton wrote: Hi Peter, On Sat, 26 Nov 2016 18:17:48 Peter A. Bigot wrote: I'm using the current head of morty and trying to get a handle on the new nodejs support in OE. I'm failing to build a recipe for statsd.

[OE-core] ASSUME_PROVIDED versus SANITY_REQUIRED_UTILITIES versus "The Build Host Packages"

a bit confused by what i'm seeing in a recent qemuppc/core-image-minimal build on my fedora system regarding which native packages are built, despite what's in bitbake.conf (using current poky layer checkout). first, here's a snippet from bitbake.conf: ASSUME_PROVIDED = "\

Re: [OE-core] [PATCH v1] wic: Add --exclude-path option to rootfs source plugin.

On Mon, Nov 28, 2016 at 12:01:09PM +0100, Kristian Amlie wrote: > On 28/11/16 11:52, Ed Bartosh wrote: > > On Mon, Nov 28, 2016 at 08:15:26AM +0100, Kristian Amlie wrote: > >>> > >>> What's the reason of insisting that path must be absolute? > >>> May be it's just me, but I find it a bit scaring

Re: [OE-core] [PATCH v1] wic: Add --exclude-path option to rootfs source plugin.

On 28/11/16 11:52, Ed Bartosh wrote: > On Mon, Nov 28, 2016 at 08:15:26AM +0100, Kristian Amlie wrote: >>> >>> What's the reason of insisting that path must be absolute? >>> May be it's just me, but I find it a bit scaring to use absolute path in >>> .wks >>> The patch is relative to the rootfs

Re: [OE-core] [PATCH v1] wic: Add --exclude-path option to rootfs source plugin.

On 28/11/16 11:46, Ed Bartosh wrote: > On Mon, Nov 28, 2016 at 08:07:05AM +0100, Kristian Amlie wrote: >> On 25/11/16 17:33, Ed Bartosh wrote: >>> On Fri, Nov 25, 2016 at 01:35:53PM +0100, Kristian Amlie wrote: On 25/11/16 13:28, Maciej Borzęcki wrote: > On Fri, Nov 25, 2016 at 11:15 AM,

Re: [OE-core] [PATCH v3] rootfs: Modify RPM installation

On vendredi 25 novembre 2016 13:09:30 CET Mark Hatle wrote: > On 11/25/16 12:17 PM, Burton, Ross wrote: > > On 24 November 2016 at 10:49, David Vincent > > > > wrote: > > -self._setup_dbg_rootfs(['/etc/rpm', '/var/lib/rpm', > >

Re: [OE-core] [PATCH v1] wic: Add --exclude-path option to rootfs source plugin.

On Mon, Nov 28, 2016 at 08:15:26AM +0100, Kristian Amlie wrote: > > > > What's the reason of insisting that path must be absolute? > > May be it's just me, but I find it a bit scaring to use absolute path in > > .wks > > The patch is relative to the rootfs directory from my point of view. > > >

Re: [OE-core] [PATCH v1] wic: Add --exclude-path option to rootfs source plugin.

On Mon, Nov 28, 2016 at 08:07:05AM +0100, Kristian Amlie wrote: > On 25/11/16 17:33, Ed Bartosh wrote: > > On Fri, Nov 25, 2016 at 01:35:53PM +0100, Kristian Amlie wrote: > >> On 25/11/16 13:28, Maciej Borzęcki wrote: > >>> On Fri, Nov 25, 2016 at 11:15 AM, Kristian Amlie > +#

Re: [OE-core] npm.bbclass support for deep native modules?

On 11/28/2016 04:11 AM, Paul Eggleton wrote: Hi Peter, On Sat, 26 Nov 2016 18:17:48 Peter A. Bigot wrote: I'm using the current head of morty and trying to get a handle on the new nodejs support in OE. I'm failing to build a recipe for statsd. Starting with this: devtool add

Re: [OE-core] npm.bbclass support for deep native modules?

Hi Peter, On Sat, 26 Nov 2016 18:17:48 Peter A. Bigot wrote: > I'm using the current head of morty and trying to get a handle on the > new nodejs support in OE. > > I'm failing to build a recipe for statsd. Starting with this: > > devtool add

[OE-core] [PATCH v2] ltp: 20160126 -> 20160920

From: Huang Qiyu 1)Upgrade ltp from 20160126 to 20160920. 2)Delete some patches, since they are integrated upstream. 0001-ltp-Don-t-link-against-libfl.patch 0006-sendfile-Use-off64_t-instead-of-__off64_t.patch 0007-replace-SIGCLD-with-SIGCHLD.patch

[OE-core] [PATCH] libxml2: Security fix CVE-2016-5131

CVE-2016-5131 libxml2: Use-after-free vulnerability in libxml2 through 2.9.4, as used in Google Chrome before 52.0.2743.82, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the XPointer range-to function. External References:

[OE-core] [PATCH] tiff: Security fix CVE-2016-9539

tools/tiffcrop.c in libtiff 4.0.6 has an out-of-bounds read in readContigTilesIntoBuffer(). Reported as MSVR 35092. External References: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-9539 Patch from: https://github.com/vadz/libtiff/commit/ae9365db1b271b62b35ce018eac8799b1d5e8a53

[OE-core] [PATCH] tiff: Security fix CVE-2016-9540

tools/tiffcp.c in libtiff 4.0.6 has an out-of-bounds write on tiled images with odd tile width versus image width. Reported as MSVR 35103, aka "cpStripToTile heap-buffer-overflow." External References: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-9540 Patch from: