From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] gnome-keyring: fix gsettings_data_convert seg fault
Date: Tue, 27 Dec 2011 10:42:44 -0800 [thread overview]
Message-ID: <4EFA11A4.8030205@linux.intel.com> (raw)
In-Reply-To: <3bdd615755d7a911dbee7aaa2c86043c0caa351b.1324991041.git.edwin.zhai@intel.com>
On 12/27/2011 05:06 AM, edwin.zhai@intel.com wrote:
> From: Zhai Edwin<edwin.zhai@intel.com>
>
> gsttings_data_convert cause seg fault as gnome-keyring's schema is not
> installed properly. As a fix, running glib-compile-schemas from glib-utils to
> made "gschemas.compiled".
>
> [YOCTO #1779] got fixed.
>
> Signed-off-by: Zhai Edwin<edwin.zhai@intel.com>
> ---
> meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb | 12 ++++++++++--
> 1 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb b/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
> index cc97225..a92ac4d 100644
> --- a/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
> +++ b/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
> @@ -11,12 +11,12 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
>
> SECTION = "x11/gnome"
>
> -PR = "r3"
> +PR = "r4"
>
> inherit autotools gnome pkgconfig
>
> DEPENDS = "gtk+ libgcrypt libtasn1 libtasn1-native gconf ${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}"
> -RDEPENDS_${PN} = "libgnome-keyring"
> +RDEPENDS_${PN} = "libgnome-keyring glib-2.0-utils"
>
> EXTRA_OECONF = "--disable-gtk-doc ${@base_contains('DISTRO_FEATURES', 'pam', '--enable-pam --with-pam-dir=${base_libdir}/security', '--disable-pam', d)}"
>
> @@ -30,6 +30,14 @@ do_install_append () {
> install -m 0644 ${WORKDIR}/org.gnome.keyring.service ${D}${datadir}/dbus-1/services
> }
>
> +pkg_postinst_gnome-keyring () {
I think you can use pkg_postinst_${PN}
> +if [ "x$D" != "x" ]; then
> + exit 1
> +fi
> +
> +test -x ${bindir}/glib-compile-schemas&& glib-compile-schemas ${datadir}/glib-2.0/schemas
> +}
> +
I think you are missing tabs here, I believe the standard for script
functions is to have tabs not spaces also.
Sau!
> FILES_${PN} += "${datadir}/dbus-1/services ${datadir}/gcr ${base_libdir}/security/*.so"
> FILES_${PN}-dbg += "${libdir}/gnome-keyring/standalone/.debug/ ${base_libdir}/security/*.la"
> FILES_${PN}-dbg += "${libdir}/gnome-keyring/devel/.debug/ ${base_libdir}/security/.debug"
prev parent reply other threads:[~2011-12-27 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 13:06 [PATCH 0/1] Fix gsettings-data-convert seg fault edwin.zhai
2011-12-27 13:06 ` [PATCH 1/1] gnome-keyring: fix gsettings_data_convert " edwin.zhai
2011-12-27 18:42 ` Saul Wold [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EFA11A4.8030205@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.