All of lore.kernel.org
 help / color / mirror / Atom feed
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: add a recipe from meta-gnome
Date: Thu, 8 Oct 2015 12:18:47 +0200	[thread overview]
Message-ID: <20151008101847.GI2385@jama> (raw)
In-Reply-To: <20150912215134.9DA455043A@opal.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]

On Sat, Sep 12, 2015 at 09:51:34PM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 5bce77d2b3b822b741e67bbca236242285e091d1
> URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=5bce77d2b3b822b741e67bbca236242285e091d1
> 
> Author: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> Date:   Thu Jun  4 13:17:51 2015 +0300
> 
> gcr: add a recipe from meta-gnome
> 
> gcr is a dependency of epiphany
> 
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> 
> ---
> 
>  meta/recipes-gnome/gcr/gcr_3.16.0.bb | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/meta/recipes-gnome/gcr/gcr_3.16.0.bb b/meta/recipes-gnome/gcr/gcr_3.16.0.bb
> new file mode 100644
> index 0000000..8b5b6e4
> --- /dev/null
> +++ b/meta/recipes-gnome/gcr/gcr_3.16.0.bb
> @@ -0,0 +1,18 @@
> +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"
> +

meta-oe recipe had:
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/

> +DEPENDS = "gtk+3 p11-kit glib-2.0 libgcrypt vala"
> +
> +inherit autotools gnomebase gtk-icon-cache gtk-doc
> +
> +SRC_URI[archive.md5sum] = "d5835680be0b6a838e02a528d5378d9c"
> +SRC_URI[archive.sha256sum] = "ecfe8df41cc88158364bb15addc670b11e539fe844742983629ba2323888d075"
> +
> +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 --]

       reply	other threads:[~2015-10-08 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150912215134.9DA455043A@opal.openembedded.org>
2015-10-08 10:18 ` Martin Jansa [this message]
2015-10-08 11:42   ` [oe-commits] Alexander Kanavin : gcr: add a recipe from meta-gnome Alexander Kanavin

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=20151008101847.GI2385@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.