I have been using the resolvconf recipe, and I have discovered a few
things which keep it from working.
The resolvconf script uses /lib/resolvconf/list-records, but the
recipe does not install it. This causes an error when
/etc/resolvconf/update.d/libc runs. This can be resolved by adding the
list
On Thu, Jun 19, 2014 at 06:53:22PM -0400, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko
>
> Make probing of "platform" bus conditional based on PROBE_PLATFORM_BUS
> variable from /etc/default/udev-cache on subsequent boots when udev
> cache is used. PROBE_PLATFORM_BUS has to be set to "yes"
Also small cosmetic changes.
Signed-off-by: Cristian Iorga
---
meta/recipes-core/initrdscripts/files/init-install-testfs.sh | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-core/initrdscripts/files/init-install-testfs.sh
b/meta/recipes-core/initrdscripts/files/init-install-t
add control for generic grub pc via serial line
Implementation [YOCTO #5615].
Signed-off-by: Cristian Iorga
---
meta-yocto-bsp/lib/oeqa/controllers/grubtarget.py | 71 +++
1 file changed, 71 insertions(+)
create mode 100644 meta-yocto-bsp/lib/oeqa/controllers/grubtarget.py
Overwriting of /etc/mtab would fail as below if the /etc/mtab link already
exist during installation phase, this patch fix this problem by checking
existance of the link before try to overwrite it.
Error message during installation if the /etc/mtab exists:
"cat: /proc/mounts: input file is output
_EOF marker was not used properly
(space left before end of line).
Signed-off-by: Cristian Iorga
---
meta/recipes-core/initrdscripts/files/init-install-testfs.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/initrdscripts/files/init-install-testfs.sh
b/me
Various fixes related to master image install script and
GRUB targets controller implemented.
The following changes since commit 7c1a975a1c2fd884aa9f6f4736656d854a6c5edb:
bitbake: toaster: Fix spacing and layout in no image files notification
(2014-06-20 14:03:58 +0100)
are available in the g
For automated hardware testing, boot process control
via serial interface is needed. As such, in grub, serial
line support is added upon testmaster image install.
Also add a specific timeout to automatically start
the master image upon start of testing phase.
Tested on multiple hardware targets w
On Mon, 2014-06-16 at 13:18 +, Adrian Calianu wrote:
> Hi Tom,
>
> First of all, thanks for your review comments! I'm glad that community
> has interest for this features.
> I will answer to your comments in-line below...
>
> > -Original Message-
> > From: openembedded-co
The current substitution to package names is not correct, its original
purpose is: replace "mesa-" with "mesa-dri-", in which process the
"mesa" package is left out, this leads mesa package to announce to
conflict with itself, and therefore cause build failures when multilib
mesa are being added to
It also avoids following QA warnings:
..
WARNING: Multilib QA Issue: lib32-mesa package lib32-mesa-megadriver -
suspicious values 'mesa-driver-nouveau-vieux mesa-driver-r200
mesa-driver-i965 mesa-driver-radeon mesa-driver-swrast mesa-driver-i915'
in RPROVIDES
WARNING: Multilib QA Issue: lib32-m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Purdie schreef op 20-06-14 11:57:
> I know that with some of the changes in oe-core, meta-oe is suffering a
> little. I've been working on fixing up some of a world build of meta-oe
> with patches including the problematic autoconf one applie
I know that with some of the changes in oe-core, meta-oe is suffering a
little. I've been working on fixing up some of a world build of meta-oe
with patches including the problematic autoconf one applied.
My WIP is:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=rpurdie/meta-oe&
Hi Experts.
Package "sysvinit" introduced an init script "bootlogd" while it used
"savelog" as:
"savelog -p -c 5 boot > /dev/null 2>&1" in its "stop" function. I wonder
where can I
get such a tool/script? Which package I need to build?
Thanks
Xiao
--
__
Hi all,
On 19/06/14 19:19, Paul Eggleton wrote:
Thanks!
On Thursday 19 June 2014 10:08:58 Tom King wrote:
Yes,
its in there too.
Unfortunately the cherokee binary in sources.oe.org seems corrupted:
# http://sources.openembedded.org/cherokee-1.2.98.tar.gz
$ ls -o cherokee-1.2.98.tar.gz
409
15 matches
Mail list logo