When matching fails, m.group(0) is invalid and can't be used in the
error message.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/parsing.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/pybootchartgui/pybootch
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 <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/draw.py | 98 ++-
1 file changed, 50 insertions(
for long builds, which will be
addressed in a separate commit by storing the data in a more compact
form.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/buildstats.bbclass | 24 +
meta/lib/buildstats.py
and happens
to be 10, so everything still gets rendered exactly as before.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/draw.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/pybootchartgui/pybootchartgui/draw
epository at:
git://github.com/pohly/openembedded-core buildstats
https://github.com/pohly/openembedded-core/tree/buildstats
Patrick Ohly (11):
buildstats: add system state sampling
pybootchartgui/draw.py: allow moving process chart up and down
pybootchartgui/draw.py: fix drawing of samples
patch series
problem when there are these extra headers.
[YOCTO #10718]
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/send-pull-request | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/scripts/send-pull-request b/scripts/send-pull-request
ind
On Mon, 2016-11-28 at 16:35 -0600, Jose Lamego wrote:
>
> 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.
> >&g
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
ed to send cover-letter with automatic
> recipients."
> exit 1
And I don't understand why this proposed change has the described
effect. Does changing the threading parameters change the output of "git
send-email" and thus indirectly the mail headers of the f
the displayed value may
be slightly lower than the actual amount of space needed because
sampling does not record the actual initial state.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/draw.py| 62
scripts/pybootch
When matching fails, m.group(0) is invalid and can't be used in the
error message.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/parsing.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/pybootchartgui/pybootch
for monitoring system
utilization is small enough that it can be enabled by default.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/lib/buildstats.py | 114 -
1 file changed, 104 insertions(+), 10 deletions(-)
diff --git a/me
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 <patrick.o...@intel.com>
---
s
.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/parsing.py | 31
1 file changed, 31 insertions(+)
diff --git a/scripts/pybootchartgui/pybootchartgui/parsing.py
b/scripts/pybootchartgui/pybootchartgui/parsing.py
index 1
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 <patrick.o...@intel.com>
---
meta/c
there's no data, which will also have to be added
for the other two.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/draw.py| 16 +--
scripts/pybootchartgui/pybootchartgui/parsing.py | 61 +---
2 files changed, 57 inse
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 <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/draw.py | 98 ++-
1 file changed, 50 insertions(
ly/openembedded-core buildstats
https://github.com/pohly/openembedded-core/tree/buildstats
Patrick Ohly (11):
buildstats: add system state sampling
pybootchartgui/draw.py: allow moving process chart up and down
pybootchartgui/draw.py: fix drawing of samples not starting at zero
pybootc
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 <patrick.o...@intel.com>
---
scripts/pybootch
for long builds, which will be
addressed in a separate commit by storing the data in a more compact
form.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/buildstats.bbclass | 16 +
meta/lib/buildstats.py | 50 +
2
and happens
to be 10, so everything still gets rendered exactly as before.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/pybootchartgui/pybootchartgui/draw.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/pybootchartgui/pybootchartgui/draw
agic-dev on my build
host, the build was failing.
Is there a way to declare that ASSUME_PROVIDED does not apply to this
case? It sounds like there is a way (based on your comments about
building file-native when building file and the libbz2-devel example),
but it did not become clear to me how that
aught
my eye: when the rootfs contains xattrs, they get lost here.
Use oe.path.copyhardlinktree() instead, it also does the hardlinking
trick.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here
slight
> preference for the glob version, because I think it's less surprising,
> but I'm fine either way.
>
> I count myself and Ed in favor of glob version, Ulrich and Andreas in
> favor of rsync version. Patrick, you wanna be tie breaker? :-)
But I said I was undecided ;-} Okay, I
r now?
>
> As it shouldn't be hard to implement I'd go for it.
Additional code implies additional testing. Remember that it also should
better be supported by mkfs.ext4 and friends.
I'd rather start simple and only add additional complexity when needed.
--
Best Regards, Patrick Ohly
The conte
On Thu, 2016-11-24 at 09:09 -0500, Philip Balister wrote:
> On 11/24/2016 02:46 AM, 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 no passwd, so
ven clearer, and patchwork could get configured to
not track such patches or at least not show them as new? Just a thought.
As it stands now, there's an entry for this patch that someone
(Richard?) will have to close:
https://patchwork.openembedded.org/series/4056/
--
Best Regards, Patrick O
pseudo_1.8.1.bb gets the backported patch and pseudo_git.bb gets
updated to include the commit.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
Notes:
Change since V1:
Updated the commit message. It was still the one written
for the initial, broken upstream
pseudo_1.8.1.bb gets the backported patch and pseudo_git.bb gets
updated to include the commit, which currently is the most recent
commit on the pseudo master branch.
There's just one problem - it breaks other cases:
foo: security.SMACK64: No such attribute
Signed-off-by: Patrick Ohly
do_rootfs and ROOTFS_POSTPROCESS_COMMANDs don't run at
all.
The task gets added such that it runs roughly at the same time as
before. Probably it doesn't actually need to depend on do_rootfs, but
this way we don't write a useless qemuboot.conf in cases where
do_rootfs fails.
Signed-off-by: Patrick Ohly
fferent audience than OE-core. Poky can
assume to be used in a secure environment, OE-core can't (because it
might be used for all kinds of devices).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make he
On Thu, 2016-11-24 at 07:15 +0100, Ulrich Ölmann wrote:
> On Wed, Nov 23, 2016 at 04:56:56PM +0100, Patrick Ohly wrote:
> > Excluding only the directory content but not the actual directory is
> > indeed a good point. I'm a bit undecided. When excluding only the
> > direc
On Wed, 2016-11-23 at 15:22 +0200, Ed Bartosh wrote:
> On Wed, Nov 23, 2016 at 02:08:28PM +0100, Kristian Amlie wrote:
> > On 23/11/16 13:08, Ed Bartosh wrote:
> > > On Tue, Nov 22, 2016 at 12:54:52PM +0100, Kristian Amlie wrote:
> > >> On 22/1
-passwd doesn't achieve that.
Even then I'm still wondering what the benefit of a well-known password
compared to no password is. Both are equally insecure, so someone who
wants to allow logins might as well go with "empty password".
--
Best Regards, Patrick Ohly
The content of this messa
nt this approach with wic, wic needs to be taught how to
exclude directories from the main rootfs. Ideally, the mkfs.* tools
should also support that without having to make an intermediate copy of
the files for a certain partition, but initially wic could create
temporary directory tre
e.
Yes, that's indeed the effect. That has pros (the Upstream-Status tag is
preserved when working with devtool) and cons (patch as attached to a
recipe is not the same as the patch upstream).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employe
why this
> works, but it looks dubious. What is parsing=True intended to do?
>
> Is it documented somewhere that modifying SRC_URI from anonymous
> python isn't allowed? I've now seen two suppliers both independently
> run into the same problem when updating to OE 2.1.
Sorry, I do
(Evolution).
A random example:
http://lists.openembedded.org/pipermail/openembedded-core/2016-November/128861.html
Not sure what the netiquette is for this list, but at least I would
appreciate a bit more aggressive trimming in replies - thanks! ;-}
--
Best Regards, Patrick Ohly
The content
he := assignment expands based on the
currently defined variables at the time of parsing the assignment.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position
On Thu, 2016-11-10 at 18:53 +0100, Patrick Ohly wrote:
> On Thu, 2016-10-13 at 13:16 -0700, Jianxun Zhang wrote:
> > It turns out this change between 3.12.2 and 3.13 introduces
> > a 2% increase of build time based on statistic data in
> > bz10367.
>
> Let me add that
to do the same tricky
revert for the next upstream version update.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I au
of the old version, then do the normal rebase with conflictstyle =
diff3. At least I find that configstyle useful and have it in my
~/.gitconfig.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I m
quot;, if I remember correctly).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized
ips_patch iotivity-1.1.1-r2.tar.gz
iotivity-1.1.1-r2-hippomocks.tar.gz iotivity-1.1.1-r2-tinycbor.tar.gz
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/archiver.bbclass | 17 -
1 file changed, 16 insertions(+), 1 deletion(-
ure corret TOOLCHAIN_CONFIGSITE_NOCACHE value
(2016-09-26 10:05:53 +0100)
are available in the git repository at:
git://github.com/pohly/openembedded-core do_ar_original
https://github.com/pohly/openembedded-core/tree/do_ar_original
Patrick Ohly (2):
archiver.bbclass: ignore unpack sub-directories in do_a
unconditionally also for relative paths, because these
paths are not useful when archiving the original source (upstream
source does not have them, they only get used by the recipe during
compilation).
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/archiver.bbclass | 20 ++
patch applied in Patrick's
> upgrade).
The compile error is inside an #ifdef, so it could be that just that
particular configuration hadn't been tested. But yes, one has to wonder.
So what's preferred for OE-core master and the 2.2 release? Updating to
1.0.2i or backporting the critical patch?
I
ars we have some users with stripped down containers where it
> hasn't been installed though and having a user readable message is
> better
... and even better is one without typos ;-}
s/firts/first/
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and alt
Hello!
This patch can be applied stand-alone. I had it in a branch together
with the 1.0.2i update and then didn't export it independently, hence
the erroneous "PATCH 1/2" in the subject.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and alt
install.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-connectivity/openssl/openssl.inc | 13 +
1 file changed, 13 insertions(+)
diff --git a/meta/recipes-connectivity/openssl/openssl.inc
b/meta/recipes-connectivity/openssl/openssl.inc
index f83664c..a632d8a
via local patches, which can be removed now.
See https://www.openssl.org/news/secadv/20160922.txt for details.
Some patches had to be refreshed and one compile error fix from
upstream's OpenSSL_1_0_2-stable was required. The server.pem
file is needed for test_dtls.
Signed-off-by: Patrick Ohly
On Fri, 2016-09-23 at 15:11 +0300, Alexander Kanavin wrote:
> On 09/23/2016 01:27 PM, Patrick Ohly wrote:
> >
> > There is one FAIL:
> >
> > ../util/shlib_wrap.sh ./dtlstest ../apps/server.pem ../apps/server.pem
> > Starting Test 0
> > Failed to load server c
On Fri, 2016-09-23 at 10:38 +0200, Patrick Ohly wrote:
> Fixes several CVEs.
>
> It compiled for me okay for qemux86, but running the ptests showed a
> problem in one of the new tests. I'll investigate that further
There is one FAIL:
../util/shlib_wrap.sh ./dtlstest ../apps/server
via local patches, which can be removed now.
See https://www.openssl.org/news/secadv/20160922.txt for details.
Some patches had to be refreshed and one compile error fix from
upstream's OpenSSL_1_0_2-stable was required.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../o
/pohly/openembedded-core/tree/openssl-102i
Patrick Ohly (1):
openssl: update to 1.0.2i (CVE-2016-6304 and more)
.../openssl/openssl/CVE-2016-2177.patch| 286 -
.../openssl/openssl/CVE-2016-2178.patch| 51
.../openssl/Fix-typo-introduced
On Wed, 2016-09-21 at 17:39 +0200, Patrick Ohly wrote:
> new-rmwork-new-scheduler
> elapsed: 42:58.54
> final disk usage: 12873MiB
> max disk usage: 14230MiB
>
> A bit better in terms of max disk usage than with the completion
> scheduler, but not by much. My observatio
On Thu, 2016-09-22 at 10:37 -0700, Christopher Larson wrote:
>
> On Thu, Sep 22, 2016 at 5:52 AM, Patrick Ohly <patrick.o...@intel.com>
> wrote:
> That's bitbake specific. What I was remembering is something
> generic
> that works for anything
On Wed, 2016-09-21 at 18:08 +0200, Martin Jansa wrote:
> On Wed, Sep 21, 2016 at 05:39:02PM +0200, Patrick Ohly wrote:
> > Test script attached. I only ran this once, so I can't vouch that the
> > numbers are stable. I remember reading about a benchmark wrapper which
> > can r
k
+1 from me. The alternative solution would be to add
"systemd-compat-units->systemd" to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS in
meta/conf/layer.conf, but that's more complicated and probably not worth
it.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and
8:56:08 +0100)
are available in the git repository at:
git://github.com/pohly/openembedded-core static-ids
https://github.com/pohly/openembedded-core/tree/static-ids
Patrick Ohly (1):
useradd-staticids.bbclass: trigger reparsing when table files change
meta/classes/useradd-staticids.bbclas
instead
of re-parsing it with the new table content
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/useradd-staticids.bbclass | 13 +
1 file changed, 13 insertions(+)
diff --git a/meta/classes/useradd-staticids.bbclass
b/meta/classes/useradd-staticids.b
On Mon, 2016-07-11 at 12:17 -0300, Otavio Salvador wrote:
> On Mon, Jul 11, 2016 at 12:10 PM, Patrick Ohly <patrick.o...@intel.com> wrote:
> > On Mon, 2016-07-11 at 11:35 -0300, Otavio Salvador wrote:
> >> Hello Ross,
> >>
> >> On Fri, Ju
It still gets installed by default via RRECOMMENDS without having to update
users of the framework (because without it, the framework is incomplete),
but that recommendation can be overridden on a per-image basis.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../recipe
a another patch now,
okay?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to spe
From: Igor Stoppa <igor.sto...@intel.com>
The rootfs can be addressed also by referring to the PartUUID
value from the GPT.
This patch enables such type of reference.
Signed-off-by: Igor Stoppa <igor.sto...@intel.com>
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
n that was discussed on the OE
mailing list for future changes to initramfs-framework (like
supporting a "live CD" module, which would replace or further augment
mounting of the rootfs).
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../initrdscripts/initramfs-framework/fini
-framework: Add support for PartUUIDs
Patrick Ohly (1):
meta-ostro-fixes: initramfs-framework: add retry loop for slow boot
devices (like USB)
.../initrdscripts/initramfs-framework/finish | 33
.../initrdscripts/initramfs-framework/rootfs | 62
(as the name implies), or just of the main
partition? The two are not necessarily the same, because some image
types combine the main partition with additional content (like a boot
loader and the kernel).
This conceptual issue needs further work.
--
Best Regards, Patrick Ohly
The content of this messa
ce under
TravisCI ;-}
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to
On Wed, 2016-06-15 at 12:45 +0200, Martin Jansa wrote:
> libgphoto2, v4l-utils fail because recent upgrade of libjpeg-turbo in oe-core
> (PNBLACKLIST sent)
I have patches ready for that, will send them now.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinio
r d.setVar() that meet that
expectation, and thus the redundant (and in Python3, harmful)
.encode() gets removed.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/npm.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/npm.bbclas
r/sbin/mkelfImage' failed
...
Reverting the commit fixes that, so can we just do that in OE-core
master while the problem gets sorted out?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no
ystem --home /var/lib/empty
--no-create-home --shell /bin/false --gid restful restful "
The build then hangs because the useradd preinst loops forever.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the s
As suspected, invoking "git archive" with all intended files as
parameters can run into command line length limitations. Splitting up
the parameters into multiple invocations (xargs-style) works and was
tested after encountering the situation in practice.
Signed-off-by: Patrick Ohly
/combo-layer-history-fixes
Patrick Ohly (2):
combo-layer: fix default "update" mode
combo-layer: avoid too long command lines in update with history
scripts/combo-layer | 34 ++
1 file changed, 30 insertions
When the "history" option is not set in the combo-layer.conf, the
intended default was to use the traditional method. Passing "True" as
default when querying the config was unintentional.
Also remove some left-over debugging code.
Signed-off-by: Patrick Ohly <patrick.o...@
On Mon, 2016-05-02 at 11:15 -0500, Alejandro del Castillo wrote:
>
> On 05/02/2016 08:39 AM, Patrick Ohly wrote:
> > On Fri, 2016-04-22 at 14:51 +0100, Richard Purdie wrote:
> >> When enabling extra DEBUGFS image generation with opkg, errors are seen
> >> lik
alid user modification.
The usage of opkg here is during image building, but the operation
itself (opkg status) is not specific to image creation and thus should
be able to handle arbitrary states of /etc and the config files in
general.
--
Best Regards, Patrick Ohly
The content of this message is my personal op
that some opportunities for
refactoring (in particular regarding file filtering) were ignored.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/combo-layer | 391 +++-
1 file changed, 389 insertions(+), 2 deletions(-)
diff --git a/s
better.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
scripts/combo-layer | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/combo-layer b/scripts/combo-layer
index 41d69f8..9297d59 100755
--- a/scripts/combo-layer
+++ b/scripts/combo-layer
@@ -174,7
9 07:53:58 +0100)
are available in the git repository at:
git://github.com/pohly/openembedded-core combo-layer-update-history
https://github.com/pohly/openembedded-core/tree/combo-layer-update-history
Patrick Ohly (3):
combo-layer: dummy "update with history"
combo-layer: r
tently. This restriction could be removed later.
In practice, putting "history" into the "[DEFAULT]" section is the
easiest approach for configuring it.
The actual code changes split up action_update and the
combo-layer.conf handling in preparation for this new mode, without
imp
the daemons are needed?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter
large).
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/lib/oe/package_manager.py | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/meta/lib/oe/package_manager.py b/meta/lib/oe/package_manager.py
index 0d23d8b..b4b359a 100644
--- a/meta/
"mktemp -t" is deprecated and does not work when using Toybox. Replace
with something that works also with Toybox.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
.../update-ca-certificates-support-Toybox.patch| 35 ++
.../ca-certificates/ca-certi
that files
belonging to ncurses-terminfo-base are checked first.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/ncurses/ncurses.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/ncurses/ncurses.inc
b/meta/recipes-core/ncu
erialgetty is pulled
into images via RRECOMMENDS.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/systemd/systemd_229.bb | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-core/systemd/systemd_229.bb
b/meta/reci
Bluez 5.37 itself correctly installs bluetooth.conf, and honors
the path settings in dbus-1.pc.
Removing the obsolete workaround is necessary for compiling
"stateless" (= read-only system configuration moved out of /etc).
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
-
clude DDATETIME from task signature (2016-04-03
15:51:10 +0100)
are available in the git repository at:
git://github.com/pohly/openembedded-core stateless
https://github.com/pohly/openembedded-core/tree/stateless
Patrick Ohly (5):
bluez5.inc: remove obsolete workaround
ncurses: reorde
-in-image.txt still makes sense for such images, so
support them by creating the directory also in
buildhistory_get_imageinfo().
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/buildhistory.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/buildhistory.bbcl
NF_VERSION}
in the error message seems a bit more readable and consistent.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/sanity.bbclass | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index
The default file pattern may be amiguous and "meld" might not always
be the preferred tool, so allow distros to override those parts of the
error messages.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/sanity.bbclass | 11 ---
1 file changed, 8
The code now iterates over different config files, but always printed a
message about conf/bblayers.conf for each file.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/sanity.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/c
The list of variables influencing do_rootfs was not updated when
introducing ROOTFS_POSTUNINSTALL_COMMAND. As a result, making changes
in commands listed there or the variables they depend on did not trigger
a re-run of do_rootfs.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
iff" is invoked with "--quiet", which avoids
producing output that is just getting thrown away. As before, any kind
of problem or output causes the layer to be marked as "modified".
[Revision 2 of the change with some dead code removed]
Signed-off-by: Patrick Ohly <patr
iff" is invoked with "--quiet", which avoids
producing output that is just getting thrown away. As before, any kind
of problem or output causes the layer to be marked as "modified".
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/image-buildinfo.bbclas
erialgetty is pulled
into images via RRECOMMENDS.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/recipes-core/systemd/systemd_229.bb | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-core/systemd/systemd_229.bb
b/meta/reci
re/systemd/man/systemd-getty-generator.html
[2] http://0pointer.de/blog/projects/serial-console.html
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the
) because the build_boot_dd() method relied on the symlink.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
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 081a0b3..8b6c30b
AULT}'}"
The exact logic when to remove the extra suffix depends on the distro
and how it enables its own image type.
Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
---
meta/classes/image.bbclass | 4 +--
meta/classes/image_types.bbclass | 63 ++---
501 - 600 of 785 matches
Mail list logo
