From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Alexander Kanavin : gcr: remove the recipe due to its move to oe-core
Date: Thu, 8 Oct 2015 12:17:09 +0200 [thread overview]
Message-ID: <20151008101709.GH2385@jama> (raw)
In-Reply-To: <20150923134118.A8135504DC@opal.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 2346 bytes --]
On Wed, Sep 23, 2015 at 01:41:18PM +0000, git@git.openembedded.org wrote:
> Module: meta-openembedded.git
> Branch: master
> Commit: 7e13bb138c5e9b66b77bf942c2add861356ffb66
> URL: http://git.openembedded.org/?p=meta-openembedded.git&a=commit;h=7e13bb138c5e9b66b77bf942c2add861356ffb66
>
> Author: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> Date: Mon Sep 14 15:26:43 2015 +0300
>
> gcr: remove the recipe due to its move to oe-core
>
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>
> ---
>
> meta-gnome/recipes-gnome/gcr/gcr_3.8.2.bb | 24 ------------------------
> 1 file changed, 24 deletions(-)
>
> diff --git a/meta-gnome/recipes-gnome/gcr/gcr_3.8.2.bb b/meta-gnome/recipes-gnome/gcr/gcr_3.8.2.bb
> deleted file mode 100644
> index e9a837b..0000000
> --- a/meta-gnome/recipes-gnome/gcr/gcr_3.8.2.bb
> +++ /dev/null
> @@ -1,24 +0,0 @@
> -SUMMARY = "A library for bits of crypto UI and parsing etc"
> -HOMEPAGE = "http://www.gnome.org/"
> -BUGTRACKER = "https://bugzilla.gnome.org/"
> -
> -LICENSE = "GPLv2"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=55ca817ccb7d5b5b66355690e9abc605"
> -
> -DEPENDS = "gtk+3 p11-kit glib-2.0 libgcrypt"
> -
> -PNBLACKLIST[gcr] ?= "CONFLICT: 4 files conflict with gnome-keyring"
> -# e.g. sysroots/qemux86-64/usr/share/glib-2.0/schemas/org.gnome.crypto.pgp.gschema.xml
> -# sysroots/qemux86-64/usr/share/GConf/gsettings/org.gnome.crypto.pgp.convert
I don't see this issue resolved in the version moved to oe-core, why did
you remove PNBLACKLIST?
It's still failing:
http://errors.yoctoproject.org/Errors/Details/20244/
> -
> -inherit autotools gnomebase gtk-icon-cache gtk-doc
> -
> -GNOME_COMPRESS_TYPE="xz"
> -
> -SRC_URI[archive.md5sum] = "f5e66afcab19897a0de0590735329fb1"
> -SRC_URI[archive.sha256sum] = "a1e615ce2cfd375f383bbdd289935a8e3e16901c3c6f032780847055e8bec2c1"
> -
> -FILES_${PN} += " \
> - ${datadir}/dbus-1 \
> - ${datadir}/gcr-3 \
> -"
>
> --
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
parent reply other threads:[~2015-10-08 10:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20150923134118.A8135504DC@opal.openembedded.org>]
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=20151008101709.GH2385@jama \
--to=martin.jansa@gmail.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-commits@lists.openembedded.org \
--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.