On Thursday, 4 May 2017 1:31:52 AM NZST Patchwork wrote:
> * Issue Series sent to the wrong mailing list
[test_target_mailing_list]
> Suggested fixSend the series again to the correct mailing list (ML)
> Suggested ML p...@yoctoproject.org [http://git.yoctoproject.org/cgit/
The path to where to install and find the sysroot components is used
in many places. This warrants it to get its own variable.
Signed-off-by: Peter Kjellerstedt
---
meta/classes/native.bbclass | 2 +-
meta/classes/staging.bbclass| 6 +++---
meta/conf/bitba
The export of PSEUDO in useradd_sysroot() contains references to
${COMPONENTS_DIR}. These need to be handled when restoring
postinst-useradd-${PN} from the sstate cache.
Signed-off-by: Peter Kjellerstedt
---
meta/classes/staging.bbclass | 2 +-
meta/classes/useradd.bbclass | 5 +
2 files cha
Similar to the problem with the hosttools directory and the state
cache that was recently fixed, there is another problem with the
sysroots-components directory. This only affects postinst-useradd
scripts, so in this case the fix can be activated from useradd.bbclass
rather than sstate.bbclass and
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: den 1 maj 2017 10:15
> To: Peter Kjellerstedt ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 0/2] Handle the hossttools directory when
> restoring from the sstate c
This patch helps to build cpio images that are binary reproducible.
The changes are as follows:
1. By default, cpio from the host is used, which can be quite old.
Hence we need to implement a way to use/call cpio-native, which supports
new features needed for binary reproducibility, notably
By default, bitbake uses host cpio, which can be quite old
and missing crucial newever features.
This patch allows to use the cpio-native instead, which is the
latest upstream version. To use the cpio-native instead of the
cpio from host, you need to specify:
IMAGE_DEPENDS_cpio_append = " cpio-rep
From: Leonardo Sandoval
As described in [1], "Empty lines in field values are usually escaped by
representing
them by a space followed by a dot." so default to the latter.
[1] https://www.debian.org/doc/debian-policy/ch-controlfields.html
Signed-off-by: Leonardo Sandoval
---
meta/classes/pac
On Wed, May 3, 2017 at 9:13 AM, Stefan Wiehler
wrote:
> Adds development shell support for out-of-tree kernel modules by reproducing
> the build environment of the compile task.
>
> Signed-off-by: Stefan Wiehler
> ---
> meta/classes/module.bbclass | 21 +
> 1 file changed, 21
On 3 May 2017 at 19:41, Max Krummenacher wrote:
> > It was only in oe-core because of LSB; let's remove it. Current libpng
> is 1.6.x.
>
> This will break at least meta-openembedded glmark2 and glcompbench.
Then meta-oe can continue to host libpng12.
Ross
--
__
Hi Alexander
Am Mittwoch, den 03.05.2017, 16:11 +0300 schrieb Alexander Kanavin:
> It was only in oe-core because of LSB; let's remove it. Current libpng is
> 1.6.x.
This will break at least meta-openembedded glmark2 and glcompbench.
Max
> Signed-off-by: Alexander Kanavin
> ---
> .../package
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
||q
Adds development shell support for out-of-tree kernel modules by reproducing
the build environment of the compile task.
Signed-off-by: Stefan Wiehler
---
meta/classes/module.bbclass | 21 +
1 file changed, 21 insertions(+)
diff --git a/meta/classes/module.bbclass b/meta/clas
Currently the LICENSE of every image is hard set to MIT.
This allows this to be overriden in derived images.
Signed-off-by: Pascal Bach
---
meta/classes/image.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index
On Wed, 2017-05-03 at 15:30 +, niko.ma...@vaisala.com wrote:
>
> On 03.05.2017 18:09, Leonardo Sandoval wrote:
> > On Wed, 2017-05-03 at 10:39 +, niko.ma...@vaisala.com wrote:
> >> Change certain variable assignments from 'hard' (=) to 'soft' (?=) so that
> >> suitable permutations of valu
On 03.05.2017 18:09, Leonardo Sandoval wrote:
> On Wed, 2017-05-03 at 10:39 +, niko.ma...@vaisala.com wrote:
>> Change certain variable assignments from 'hard' (=) to 'soft' (?=) so that
>> suitable permutations of values for these variables can be assigned eg. in
>> custom meta layers. Other
All,
I'm on poky/krogoth and I am in the process of moving to poky/morty on an Atmel
AT91SAM9G25 platform (arm926ejste architecture). On the first try booting with
my image built under morty, I noticed that the kernel image was larger. I've
done some more testing and I see that the rest of th
On Wed, 2017-05-03 at 10:39 +, niko.ma...@vaisala.com wrote:
> Change certain variable assignments from 'hard' (=) to 'soft' (?=) so that
> suitable permutations of values for these variables can be assigned eg. in
> custom meta layers. Otherwise eg. fossology server is limited to run on same
>
On 3 May 2017 at 09:23, wrote:
> +# Check for incompatible TARGET_ARCH
> +python __anonymous () {
> +if d.getVar('TARGET_ARCH') == "arc":
> +raise bb.parse.SkipRecipe("ghostscript is incompatible with
> target arc")
> +}
>
Wouldn't it be neater to use COMPATIBLE_HOST? For example sy
That a utility function permanently changes the process environment is
bad style and leads to subtle, hard to debug problems.
For example, we had one oe-selftest which used runqemu() with an
override for DEPLOY_DIR_IMAGE. Another test then just called runCmd()
and ended up passing the wrong DEPLOY
== Series Details ==
Series: "liberation-fonts: update to 2" and 4 more
Revision: 1
URL : https://patchwork.openembedded.org/series/6590/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been e
This recipe was carried only for LSB compatibility,
with upstream being defunct for a long time; if there is a need
for a modern, supported implementation of mail/mailx, then
s-nail (http://sdaoden.eu/code.html) or mailutils (http://mailutils.org/)
should be used.
Signed-off-by: Alexander Kanavin
These were required by LSB 4.1 tests; there's no other reason to continue
carrying them in oe-core.
Signed-off-by: Alexander Kanavin
---
.../packagegroups/packagegroup-core-lsb.bb | 6
meta/recipes-lsb4/perl/libclass-isa-perl_0.36.bb | 31 -
meta/recipes-lsb4/
Last version of qt4 was released 2 years ago, and Qt4 was
officially EOLd at the end of 2015. On the other hand, LSB is no longer
being developed, and so will 'require' Qt4 until the end of time.
Let's pull the plug.
Signed-off-by: Alexander Kanavin
---
.../conf/distro/include/poky-world-exclud
'fontforge issue' was actually a non-issue; fontforge is required only
when building ttf fonts from sfd source. We took prebuilt ttf fonts
when using 1.04 version, and can do the same thing with 2.00.1 version,
it's just that the tarball name for prebuilt fonts has slightly changed
and no one notic
It was only in oe-core because of LSB; let's remove it. Current libpng is 1.6.x.
Signed-off-by: Alexander Kanavin
---
.../packagegroups/packagegroup-core-lsb.bb | 1 -
meta/recipes-lsb4/libpng/libpng12_1.2.57.bb| 36 --
2 files changed, 37 deletions(-)
delet
On 3 May 2017 at 13:40, Patrick Ohly wrote:
> +env = dict(os.environ.items())
>
os.environ.copy() seems neater.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo
On Wed, 2017-05-03 at 13:53 +0100, Richard Purdie wrote:
> > Anyway, the variables weren't logged before either, so I'll just
> keep
> > that and change to passing an env dict.
>
> You could pass in the specific env delta you want to the function and
> leave launch to infill anything which isn't s
On Wed, 2017-05-03 at 14:17 +0200, Patrick Ohly wrote:
> On Wed, 2017-05-03 at 13:00 +0100, Burton, Ross wrote:
> >
> >
> > On 3 May 2017 at 12:53, Patrick Ohly
> > wrote:
> > Then it wouldn't get logged. Not a particularly strong
> > argument, though.
> > If that's prefe
That a utility function permanently changes the process environment is
bad style and leads to subtle, hard to debug problems.
For example, we had one oe-selftest which used runqemu() with an
override for DEPLOY_DIR_IMAGE. Another test then just called runCmd()
and ended up passing the wrong DEPLOY
On Wed, May 03, 2017 at 10:47:45AM +0200, Andreas Reichel wrote:
> On Tue, May 02, 2017 at 04:36:22PM +0300, Ed Bartosh wrote:
> > On Fri, Apr 21, 2017 at 02:11:45PM +0200, Andreas J. Reichel wrote:
> > > To increase code maintainability, use dictionaries
> > > as enum-like container for parameter
On 3 May 2017 at 13:17, Patrick Ohly wrote:
> They could be logged in start(), but at the moment the logging is in
> launch(), and if we keep the semantic the same as in subprocess.Popen()
> (i.e. caller provides entire environment), then that logging doesn't
> know which env variables might be w
On Wed, 2017-05-03 at 13:00 +0100, Burton, Ross wrote:
>
> On 3 May 2017 at 12:53, Patrick Ohly wrote:
> Then it wouldn't get logged. Not a particularly strong
> argument, though.
> If that's preferred, I can change the implementation.
>
>
>
> I prefer the clari
On 3 May 2017 at 12:53, Patrick Ohly wrote:
> Then it wouldn't get logged. Not a particularly strong argument, though.
> If that's preferred, I can change the implementation.
>
I prefer the clarity of copying os.environ and adding to it over running
env, especially as you have whitespace/quoting
On Wed, 2017-05-03 at 12:13 +0100, Richard Purdie wrote:
> Why not pass in an env to the subprocess call in launch()?
Then it wouldn't get logged. Not a particularly strong argument, though.
If that's preferred, I can change the implementation.
--
Best Regards, Patrick Ohly
The content of this
Change certain variable assignments from 'hard' (=) to 'soft' (?=) so that
suitable permutations of values for these variables can be assigned eg. in
custom meta layers. Otherwise eg. fossology server is limited to run on same
machine as bitbake, and generated SPDX files are placed into home direct
On Wed, 2017-05-03 at 12:56 +0200, Patrick Ohly wrote:
> That a utility function permanently changes the process environment
> is
> bad style and leads to subtle, hard to debug problems.
>
> For example, we had one oe-selftest which used runqemu() with an
> override for DEPLOY_DIR_IMAGE. Another t
== Series Details ==
Series: Allow overriding environment specific SPDX variables
Revision: 1
URL : https://patchwork.openembedded.org/series/6584/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have
That a utility function permanently changes the process environment is
bad style and leads to subtle, hard to debug problems.
For example, we had one oe-selftest which used runqemu() with an
override for DEPLOY_DIR_IMAGE. Another test then just called runCmd()
and ended up passing the wrong DEPLOY
Change certain variable assignments from 'hard' (=) to 'soft' (?=) so that
suitable permutations of values for these variables can be assigned eg. in
custom meta layers. Otherwise eg. fossology server is limited to run on same
machine as bitbake, and generated SPDX files are placed into home direct
On Wed, May 03, 2017 at 10:45:52AM +0200, Andreas Reichel wrote:
> On Tue, May 02, 2017 at 03:56:38PM +0300, Ed Bartosh wrote:
> > On Fri, Apr 21, 2017 at 02:11:41PM +0200, Andreas J. Reichel wrote:
> > > Handle exception if a file could not be deleted during clean-up of
> > > unwanted files, thus
On Tue, May 02, 2017 at 05:37:31PM +0300, Ed Bartosh wrote:
> On Fri, Apr 21, 2017 at 02:11:40PM +0200, Andreas J. Reichel wrote:
> > * wic uses optparse and a rather complicated approach of its
> > initialization. It is much easier to switch from the
> > deprecated optparse to
On Tue, May 02, 2017 at 04:36:22PM +0300, Ed Bartosh wrote:
> On Fri, Apr 21, 2017 at 02:11:45PM +0200, Andreas J. Reichel wrote:
> > To increase code maintainability, use dictionaries
> > as enum-like container for parameter string comparisons.
> >
> > Signed-off-by: Andreas Reichel
> > Signed-o
On Tue, May 02, 2017 at 03:56:38PM +0300, Ed Bartosh wrote:
> On Fri, Apr 21, 2017 at 02:11:41PM +0200, Andreas J. Reichel wrote:
> > Handle exception if a file could not be deleted during clean-up of
> > unwanted files, thus preventing a failure of wic in this case.
>
> Can you explain why partit
From: Chang Rebecca Swee Fun
The following warning occurs when building with meta-zephyr
with MACHINE set to arduino-101-sss:
WARNING:
/srv/sdc/builds/11319/meta/recipes-extended/ghostscript/ghostscript_9.20.bb:
Unable to get checksum for ghostscript SRC_URI entry objarch.h: file could not
be
From: Chang Rebecca Swee Fun
Hi,
The following warning occurs when building zephyr with arduino-101-sss.
WARNING:
/srv/sdc/builds/11319/meta/recipes-extended/ghostscript/ghostscript_9.20.bb:
Unable to get checksum for ghostscript SRC_URI entry objarch.h: file could not
be found
This can be
On 05/02/2017 07:50 PM, Tomas Novotny wrote:
this package contains platform independent xml and dtd only. So I guess that
allarch class can be inherited. Does it makes sense to create a separate patch
or
is it better to squash it here?
A separate patch is better - feel free to send one and tak
47 matches
Mail list logo
