From 0793aa7daf4b594fae1b412ab16a7d42d8c8560b Mon Sep 17 00:00:00 2001
From: Olaf Mandel o.man...@menlosystems.com
Date: Tue, 7 Oct 2014 15:12:08 +0200
Subject: [PATCH 1/2] Images: handle rowstride != width*bytes_per_pixel
Up till now, image data with a rowstride larger than the value
expected
Am 07.10.2014 18:43, schrieb Olaf Mandel:
Up till now, image data with a rowstride larger than the value
expected from width and bytes_per_pixel caused a trapezoid
distortion of the displayed image.
Signed-off-by: Olaf Mandel o.man...@menlosystems.com
-Snipp-
Hi,
my apologies: I should
Several recipes reference the LICENSE file in their LIC_FILES_CHKSUM
variable as ${COREBASE}/LICENSE. This forces distribution providers to
keep this file verbatim or to overload the affected recipes. The section
"Moving to the Yocto Project 1.6 Release" in the Yocto manual suggests
removing the
I ran into QA issues when inadvertently replacing OEs LICENSE with
Yoctos LICENSE file. Why should recipes depend on the license for
the complete collection of layers? At least for "normal" recipes
that generate target device packages, this makes no sense to me.
I patched out the global LICENSE
Hello,
Am 20.10.2016 um 12:44 schrieb Peter Kjellerstedt:
>> -Original Message-
-Snipp-
>> Subject: [OE-core] [PATCH 1/1] Remove $COREBASE/LICENSE from
-Snipp-
>
> Even after this is applied, there are still nine recipes in OE-Core
> that reference ${COREBASE}/LICENSE. There is also an
.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
scripts/combo-layer | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/combo-layer b/scripts/combo-layer
index 4a210fb..089b65f 100755
--- a/scripts/combo-layer
+++ b/scripts/combo-layer
@@ -426,7
When calling tempfile.NamedTemporaryFile().write(str()), at least on
Python 3.4.2 this fails with this error:
TypeError: 'str' does not support the buffer interface
Change the file-mode for all such files from binary to text mode.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.
Compiling texi2html 5.0 out-of-source with USE_NLS set to no failed
because it tried to copy from srcdir without using that variable.
Fix this issue and add a reference to the upstream commit.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
.../files/0001-Allow-compili
I forgot to signoff two of my last patches, so here is a v2 of both
of them.
Olaf Mandel (2):
combo-layer: handle file_exclude matching dirs
Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM
--
2.1.4
--
___
Openembedded-core mailing list
If file_exclude matches a directory, os.unlink() got called with this
directory as an argument.
Filter out paths that end in a directory separator.
This still leaves the (then empty) directories, but this does not affect
the git commit.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.
ckages do not change (the license files are not contained in
them), do not increase PR.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
meta-skeleton/recipes-skeleton/useradd/useradd-example.bb | 3 +--
meta/recipes-bsp/formfactor/formfactor_0.0.bb | 3 +--
meta/recipes-c
Compiling texi2html 5.0 out-of-source with USE_NLS set to no failed
because it trieed to copy from srcdir without using that variable.
Fix this issue.
No need to send upstream: current trunk already contains this.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
.../files/0001
declarations from all recipes that do not
need it.
CC: Paul Eggleton <paul.eggle...@linux.intel.com>
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
meta-selftest/recipes-test/error/error.bb | 1 -
meta/recipes-core/meta/buildtool
Hi Paul,
Am 21.10.2016 um 01:29 schrieb Paul Eggleton:
> On Wed, 19 Oct 2016 10:05:12 Olaf Mandel wrote:
-Snipp-
>> There are additional recipes that reference the global LICENSE
>> file, but where I am not sure if a less blanket license declaration
>> is appropriate or not
buildstats not being in USER_CLASSES is no reason to fail every
single task in toaster_collect_task_stats: using a non-existing
variable results in a None argument to os.path.join().
Check the variable availability before trying to use it.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.
If file_exclude matches a directory, os.unlink() got called with this
directory as an argument.
Filter out paths that end in a directory separator.
This still leaves the (then empty) directories, but this does not affect
the git commit.
---
scripts/combo-layer | 2 ++
1 file changed, 2
to be more ubiquitous (they
are generated by recipetool), place the new pattern first.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
meta/classes/mirrors.bbclass | 2 ++
meta/classes/own-mirrors.bbclass | 1 +
2 files changed, 3 insertions(+)
diff --git a/meta/classes/mirrors.b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Paul,
Am 24.08.2017 um 22:53 schrieb Paul Eggleton:
> On Friday, 25 August 2017 6:19:46 AM NZST Olaf Mandel wrote:
>> For URLs with the npm:// transport but with no other slash in it,
>> the common MIRRORS and PREMIRRORS
is searched for on the mirror with the same path that was
in the URI. Because of that, the pattern with the slash should be first
in the list, to prevent extra requests to the mirrors containing the
wrong path.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
meta/classes/mirrors.b
considered. So the fetch step fails with this error:
Exception: sre_constants.error: missing ), unterminated subpattern at
position 2
Probably because the pattern was split to:
['npm', '.*(', '/.*)?', '', '', OrderedDict()]
Best regards,
Olaf
- --
Olaf Mandel
-BEGIN PGP SIGNATURE-
Ve
, a pattern like 'npm://.*(/.*)?' would
probably be preferred, but that won't work here: the pattern gets split
into the substrings 'npm', '.*(' and '/.*)?', which are not valid
regular expressions individually.
Signed-off-by: Olaf Mandel <o.man...@menlosystems.com>
---
meta/classes/mirrors.b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello again,
Am 25.08.2017 um 18:14 schrieb Olaf Mandel:
> Am 25.08.2017 um 16:32 schrieb Leonardo Sandoval:
>> instead of adding a new npm regex, not sure if below one would
>> the same job
>
>> npm://.*(/.*)?
>
e location expected by nodejs (/usr/lib/node) seems the right
choice.
[1]: https://nodejs.org/api/modules.html#modules_loading_from_the_global_folders
[2]: https://nodejs.org/api/modules.html#modules_addenda_package_manager_tips
Signed-off-by: Olaf Mandel
---
meta/classes/npm.bbclass | 11 ++---
e location expected by nodejs (/usr/lib/node) seems the right
choice.
[1]: https://nodejs.org/api/modules.html#modules_loading_from_the_global_folders
[2]: https://nodejs.org/api/modules.html#modules_addenda_package_manager_tips
Signed-off-by: Olaf Mandel
---
meta/classes/npm.bbclass | 11 ++---
problem is: v1 does not actually work. What is the procedure to
handle this? Should I make a patch that works on top of the v1 already
in master?
Thanks,
Olaf
- --
Olaf Mandel
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEErGOsr28GGMKRE/TmVL2dtGJSHf8FAlvNqj8A
Signed-off-by: Olaf Mandel
---
meta/classes/npm.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/npm.bbclass b/meta/classes/npm.bbclass
index c351ff0866..d5ff0c6d57 100644
--- a/meta/classes/npm.bbclass
+++ b/meta/classes/npm.bbclass
@@ -10,7 +10,7 @@ def
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Am 23.10.2018 um 00:45 schrieb Richard Purdie:
> On Mon, 2018-10-22 at 12:45 +0200, Olaf Mandel wrote:
>> [...] What is the procedure to handle this? Should I make a
>> patch that works on top of the v1 already in master?
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Dan,
Am 26.10.2018 um 19:46 schrieb Dan McGregor:
> On Fri, 19 Oct 2018 at 09:29, Olaf Mandel
> wrote:
>> -NPM_INSTALLDIR = "${D}${libdir}/node_modules/${NPMPN}"
>> +NPM_INSTALLDIR = "${D}${libdir}/node/
Allow the use of an alternate SSH executable for deploy-target and
undeploy-target. The command can be specified with -e / --ssh-exec.
Signed-off-by: Olaf Mandel
---
scripts/lib/devtool/deploy.py | 20
1 file changed, 16 insertions(+), 4 deletions(-)
diff --git a/scripts
The bosybox version of tar in sumo considers symlink targets that start
with / or with ../ to be unsafe and refuses to unpack them unless the
EXTRACT_UNSAFE_SYMLINKS environment variable is set to 1.
As even many core packages legitimately contain such links (e.g.
coreutils-locale-*, dropbear,
The bosybox version of tar considers symlink targets that start with /
or with ../ to be unsafe and refuses to unpack them unless the
EXTRACT_UNSAFE_SYMLINKS environment variable is set to 1.
As even many core packages legitimately contain such links (e.g.
coreutils-locale-*, dropbear, eudev,
31 matches
Mail list logo