Some of gdbm's ptest cases require gdbmtool, which is packaged into
${PN}-bin. So extend the RDEPENDS_${PN}-ptest to include the package.
Signed-off-by: Chen Qi
---
meta/recipes-support/gdbm/gdbm_1.18.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Previously I do the test on qemumips, qemuarm, qemuarm64
and missed qemux86/qemux86-64 which caused the defect.
After applied the V2 fix, I do runqemu boot test each 4 times on the
following qemu
The qemux86
[ 2.536936] random: crng init done
[ 2.795946] random: crng init done
[
*** BLURB HERE ***
The following changes since commit 84eecb017ef92ef36b4df730908828e54aeff85c:
build-appliance-image: Update to master head revision (2018-10-29 17:38:16
+)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/gdbm-ptest
*** BLURB HERE ***
The following changes since commit 84eecb017ef92ef36b4df730908828e54aeff85c:
build-appliance-image: Update to master head revision (2018-10-29 17:38:16
+)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/go-dep
The current go-dep does not compile ptest successfully on mips
and mips64. So as a workaround, disable PTEST_ENABLED explicitly
to avoid error like below.
| vet config not found
Signed-off-by: Chen Qi
---
meta/recipes-devtools/go/go-dep_0.5.0.bb | 5 +
1 file changed, 5 insertions(+)
From: Mingli Yu
The official repo for mtd-utils is git://git.infradead.org/mtd-utils.git,
however there comes below error:
$ git ls-remote git://git.infradead.org/mtd-utils.git
fatal: unable to connect to git.infradead.org:
git.infradead.org[0: 198.137.202.133]: errno=Connection timed out
On Tue, 2018-10-30 at 11:12 +0100, Fabien Lahoudere wrote:
> In order to be more efficient, we use xz as compression method
> to create GPL sources archives.
>
> Signed-off-by: Fabien Lahoudere
> ---
> meta/classes/archiver.bbclass | 7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
In order to be more efficient, we use xz as compression method
to create GPL sources archives.
Signed-off-by: Fabien Lahoudere
---
meta/classes/archiver.bbclass | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta/classes/archiver.bbclass
Current Dev Position: YP 2.6 M4 is in QA.
Next Deadline: YP 2.6 M4 Release Target was Oct. 26, 2018
SWAT Team Rotation:
· SWAT lead is currently: Tracy
· SWAT team rotation: Tracy -> Chen on Nov. 2, 2018
· SWAT team rotation: Chen -> Armin on Nov. 9, 2018
·
Pyvenv is just a small script that uses venv to create virtual
environments.
https://www.python.org/dev/peps/pep-0405/#creating-virtual-environments
This patch adds the python3-venv module as a self-contained package which
python3-pyvenv must depend on at run-time.
The patch also provides the
The machine is only down temporarily and should be back soon. I don't
think we should merge this as we'll be reverting shortly.
Ross
On Tue, 30 Oct 2018 at 07:53, wrote:
>
> From: Mingli Yu
>
> The official repo for mtd-utils is git://git.infradead.org/mtd-utils.git,
> however there comes
Hi,
Having updated poky from 028a292001f64ad86c6b960a05ba1f6fd72199de (end-of
July) to 3b77e7b7852549dcfbc426d4ce258e6e857c0acd (mid October), at least
two broken sstate archives have been created:
* the sstate archive for update-rc.d package_write_ipk contains a broken
main package
On Tue, 30 Oct 2018 at 16:13, Hugues Kamba wrote:
> I am not sure where you saw the commit message say that pyvenv has been
> removed.
The python3-pyvenv package is literally being removed:
packages/corei7-64-poky-linux/python3: PACKAGES: removed
"python3-pyvenv", added "python3-venv"
Ross
--
Hello Ross,
Thank you for reviewing.
I am not sure where you saw the commit message say that pyvenv has been removed.
What it says about pyvenv is that it is deprecated in python3.6 (to explain why
it has been provided via the newly created venv package).
Regards
Hugues
Get Outlook for
Patch looks good, but the commit message contradicts itself a few
times. python3-pyvenv is removed, but:
" This patch adds the python3-venv module as a self-contained package which
python3-pyvenv must depend on at run-time."
This patch specifies the newly created
python3-venv as a
mpfr.org is not accessible at the moment.
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-support/mpfr/mpfr_4.0.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support/mpfr/mpfr_4.0.1.bb
b/meta/recipes-support/mpfr/mpfr_4.0.1.bb
index
On Tue, 2018-10-30 at 15:45 +, André Draszik wrote:
> Having updated poky from 028a292001f64ad86c6b960a05ba1f6fd72199de
> (end-of
> July) to 3b77e7b7852549dcfbc426d4ce258e6e857c0acd (mid October), at
> least
> two broken sstate archives have been created:
>
> * the sstate archive for
On Tue, Oct 30, 2018 at 10:17 AM Bruce Ashfield
wrote:
>
> On 10/30/18 1:02 PM, Andre McCurdy wrote:
> > On Mon, Oct 29, 2018 at 8:39 PM Bruce Ashfield
> > wrote:
> >>
> >> As was warned by commit 312ee68752fa [kconfig: announce removal of
> >> oldnoconfig if used], oldnoconfig has been removed
On Mon, Oct 29, 2018 at 8:39 PM Bruce Ashfield
wrote:
>
> As was warned by commit 312ee68752fa [kconfig: announce removal of
> oldnoconfig if used], oldnoconfig has been removed from the 4.20 kernel.
>
> So we switch our default mode to olddefconfig.
>
> commit fb16d8912 [kconfig: replace
On 10/30/18 1:02 PM, Andre McCurdy wrote:
On Mon, Oct 29, 2018 at 8:39 PM Bruce Ashfield
wrote:
As was warned by commit 312ee68752fa [kconfig: announce removal of
oldnoconfig if used], oldnoconfig has been removed from the 4.20 kernel.
So we switch our default mode to olddefconfig.
commit
Several distros are now shipping "python" as python v3 contra to the original
python guidelines. This causes users confusion/pain in trying to use our tools.
We can just force "python" to "python2" within HOSTTOOLS to avoid this issue
and hide the complexity from the user.
Signed-off-by: Richard
Hi,
A PATCH v2 for this fix has been submitted providing the pyvenv package from
the venv package.
Thanks
Hugues
On 29/10/2018, 14:06, "Richard Purdie"
wrote:
On Mon, 2018-10-29 at 13:07 +, Burton, Ross wrote:
> If pyvenv is going to disappear, would it be neater to just put
On 2018-10-30 2:51 PM, Martin Jansa wrote:
Agreed with Andre, also the quotes in new version don't match, which
makes me wonder how well this was actually tested.
Where are you seeing the non matching quotes ? The CC="" blocks
have been there for a while, and haven't caused any issues.
Other
On 2018-10-30 3:46 PM, Andre McCurdy wrote:
On Tue, Oct 30, 2018 at 12:05 PM Bruce Ashfield
wrote:
As was warned by commit 312ee68752fa [kconfig: announce removal of
oldnoconfig if used], oldnoconfig has been removed from the 4.20 kernel.
So we switch our default mode to olddefconfig.
It's back now.
Ross
On Tue, 30 Oct 2018 at 12:13, Burton, Ross wrote:
>
> The machine is only down temporarily and should be back soon. I don't
> think we should merge this as we'll be reverting shortly.
>
> Ross
> On Tue, 30 Oct 2018 at 07:53, wrote:
> >
> > From: Mingli Yu
> >
> > The
Agreed with Andre, also the quotes in new version don't match, which makes
me wonder how well this was actually tested.
Using apostrophes inside quoted string value would make it easier to see
that there is extra " after the useless yes call.
On Tue, Oct 30, 2018 at 6:31 PM Andre McCurdy wrote:
== Series Details ==
Series: kernel: use olddefconfig as the primary target for
KERNEL_CONFIG_COMMAND (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/14712/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated
On Tue, Oct 30, 2018 at 12:05 PM Bruce Ashfield
wrote:
>
> As was warned by commit 312ee68752fa [kconfig: announce removal of
> oldnoconfig if used], oldnoconfig has been removed from the 4.20 kernel.
>
> So we switch our default mode to olddefconfig.
>
> commit fb16d8912 [kconfig: replace
As was warned by commit 312ee68752fa [kconfig: announce removal of
oldnoconfig if used], oldnoconfig has been removed from the 4.20 kernel.
So we switch our default mode to olddefconfig.
commit fb16d8912 [kconfig: replace 'oldnoconfig' with 'olddefconfig',
and keep the old name as an alias]
Running strace ptest is failing with file not found errors.
../../strace: Process 1990 attached
diff: ../../../ptest0/tests/strace-ff.expected: No such file or directory
Even though file is present in the /usr/lib/strace/ptest/tests
directory.
Issue is caused by sed doing a find and replace
On 2018-10-30 5:13 PM, Martin Jansa wrote:
+KERNEL_CONFIG_COMMAND ?= "oe_runmake_call -C ${S} CC="${KERNEL_CC}"
O=${B} olddefconfig || yes '' | oe_runmake -C ${S} O=${B}
CC="${KERNEL_CC}" oldnoconfig"
It's the 2 apostrophes after "yes", which look like double quotes in the
font used in
+KERNEL_CONFIG_COMMAND ?= "oe_runmake_call -C ${S} CC="${KERNEL_CC}" O=${B}
olddefconfig || yes '' | oe_runmake -C ${S} O=${B} CC="${KERNEL_CC}"
oldnoconfig"
It's the 2 apostrophes after "yes", which look like double quotes in the
font used in gmail, sorry.
On Tue, Oct 30, 2018 at 7:58 PM Bruce
Paul,
Thanks for sending.
Contributors
I have an initial section at
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
which is based on Richard's input. I am sure there are more items.
Thanks,
Scott
On Tue, Oct 23, 2018 at 2:14 PM Paul
On Tue, Oct 30, 2018 at 9:22 AM Oleksandr Kravchuk
wrote:
>
> mpfr.org is not accessible at the moment.
>
it seems to back/working ok
> Signed-off-by: Oleksandr Kravchuk
> ---
> meta/recipes-support/mpfr/mpfr_4.0.1.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
The fix is similar to what was done for PowerPC32.
It solves below error, while compiling for PowerPC64,
-- snip --
| ../../../../valgrind-3.13.0/none/tests/ppc64/test_isa_2_06_part2.c: In
function 'usage':
| ../../../../valgrind-3.13.0/none/tests/ppc64/test_isa_2_06_part2.c:1778:3:
warning:
On 2018年10月31日 03:51, Burton, Ross wrote:
It's back now.
Got it, thanks Ross!
Thanks,
Ross
On Tue, 30 Oct 2018 at 12:13, Burton, Ross wrote:
The machine is only down temporarily and should be back soon. I don't
think we should merge this as we'll be reverting shortly.
Ross
On Tue,
I am still new to Yocto but my understanding of adding pyvenv to venv's
RPROVIDES is that python3-pyvenv is available (albeit as an alias of
python3-venv).
I therefore have not removed the possibility for one to choose to include the
pyvenv package instead of the new venv package.
In fact, I
On Tue, 30 Oct 2018 at 04:53, Randy MacLeod wrote:
> I think what started us down this path is a FACE [1] compliance test.
> If there's resistance to moving the package to oe-core, can we
> enable python-tk even if tk stayed in meta-oe, Grace?
> Also, this should be done using using
For changes, please see:
https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/?qt=range=e4fe79cf0d9a05ee3f3a027148ef0aeb2b1b34e1...0932a6b37ba6d5c9e916a1cb6ab89c3205b81a0c
Enable sna by default and remove upstreamed patches.
Signed-off-by: Anuj Mittal
---
Hi Richard,
Thanks for sharing with us your inputs for this patch.
For the weird "_" prefixes, the 3 new methods were initially developed in
“OESelftestTestContextExecutor” class to gather information needed for selftest
to write json test result file, while the
40 matches
Mail list logo
