On 11/30/11 11:38 AM, Richard Purdie wrote:
On Wed, 2011-11-30 at 09:24 +0100, Koen Kooi wrote:
This fixes startup issues like this:
2011-11-30T09:02:10+01:00 beaglebone ck-log-system-start[91]: **
(process:91): WARNING **: Couldn't create log
file /var/log/ConsoleKit/history (No such file or directory)
Signed-off-by: Koen Kooi<[email protected]>
---
.../recipes-support/consolekit/consolekit_0.4.5.bb | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-support/consolekit/consolekit_0.4.5.bb
b/meta/recipes-support/consolekit/consolekit_0.4.5.bb
index 562dfb3..a02203c 100644
--- a/meta/recipes-support/consolekit/consolekit_0.4.5.bb
+++ b/meta/recipes-support/consolekit/consolekit_0.4.5.bb
@@ -2,7 +2,7 @@ DESCRIPTION = "ConsoleKit is a framework for defining and
tracking users, login
HOMEPAGE="http://www.freedesktop.org/wiki/Software/ConsoleKit";
BUGTRACKER="https://bugs.freedesktop.org/buglist.cgi?query_format=specific&product=ConsoleKit";
-PR = "r5"
+PR = "r6"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
@@ -23,7 +23,7 @@ EXTRA_OECONF =
"--with-systemdsystemunitdir=${base_libdir}/systemd/system/ \
${@base_contains('DISTRO_FEATURES', 'pam',
'--enable-pam-module --with-pam-module-dir=${base_libdir}/security',
'--disable-pam-module', d)} \
"
-FILES_${PN} += "${libdir}/ConsoleKit ${base_libdir} ${datadir}/dbus-1
${datadir}/PolicyKit ${datadir}/polkit*"
+FILES_${PN} += "${localstatedir}/log/ConsoleKit ${libdir}/ConsoleKit ${base_libdir}
${datadir}/dbus-1 ${datadir}/PolicyKit ${datadir}/polkit*"
FILES_${PN}-dbg += "${base_libdir}/security/.debug"
PACKAGES =+ "pam-plugin-ck-connector"
Looks like this is breaking builds:
| consolekit ##################################################
| error: unpacking of archive failed on file /var/log: cpio: rename failed -
Invalid argument
This is a bit of an obscure error, but what it really means is that something
created a directory called /var/log, while something else created a symlink
called /var/log. The directory owner was installed before the symlink owner..
so when the symlink was being installed cpio went "huh?!" (note: the problem
could be /var... hard to tell)
This is one of the situations that the system wide directory "fixing" in
packages.bbclass is support to resolve.
--Mark
:(
http://autobuilder.pokylinux.org:8010/builders/nightly-x86-64/builds/197/steps/shell_30/logs/stdio
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
