All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Manuel Bachmann <mbc@iot.bzh>
Subject: Re: [PATCH 1/2][meta-multimedia] gupnp: Update to 0.20.14
Date: Mon, 1 Feb 2016 16:07:10 +0100	[thread overview]
Message-ID: <20160201150710.GC2639@jama> (raw)
In-Reply-To: <1453474271-26539-1-git-send-email-manuel.bachmann@iot.bzh>

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

On Fri, Jan 22, 2016 at 03:51:11PM +0100, Manuel Bachmann wrote:
> From: Manuel Bachmann <mbc@iot.bzh>
> 
> Update to latest version (required for latest Rygel).

Causes new QA warning:
gupnp-0.20.14: /usr/bin/gupnp-binding-tool_gupnp-dev contained in
package gupnp-dev requires /usr/bin/python, but no providers found in
its RDEPENDS [file-rdeps]

> 
> Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh>
> ---
>  meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.12.bb |    8 --------
>  meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.14.bb |    8 ++++++++
>  2 files changed, 8 insertions(+), 8 deletions(-)
>  delete mode 100644 meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.12.bb
>  create mode 100644 meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.14.bb
> 
> diff --git a/meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.12.bb b/meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.12.bb
> deleted file mode 100644
> index c8c6164..0000000
> --- a/meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.12.bb
> +++ /dev/null
> @@ -1,8 +0,0 @@
> -require gupnp.inc
> -
> -SRC_URI = "${GNOME_MIRROR}/${BPN}/0.20/${BPN}-${PV}.tar.xz"
> -SRC_URI[md5sum] = "c01aa6d3a78792b3a24591f036dd91f4"
> -SRC_URI[sha256sum] = "205d47b950a1b7190df1115f454cb38a44d71aacfec75d4287299e400e139b69"
> -
> -LIC_FILES_CHKSUM = "file://COPYING;md5=3bf50002aefd002f49e7bb854063f7e7 \
> -                    file://libgupnp/gupnp.h;beginline=1;endline=20;md5=d78a69d9b6e63ee2dc72e7b674d97520"
> diff --git a/meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.14.bb b/meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.14.bb
> new file mode 100644
> index 0000000..ed07175
> --- /dev/null
> +++ b/meta-multimedia/recipes-connectivity/gupnp/gupnp_0.20.14.bb
> @@ -0,0 +1,8 @@
> +require gupnp.inc
> +
> +SRC_URI = "${GNOME_MIRROR}/${BPN}/0.20/${BPN}-${PV}.tar.xz"
> +SRC_URI[md5sum] = "63346ef90ac5cd925c3a941f51d8bca6"
> +SRC_URI[sha256sum] = "77ffb940ba77c4a6426d09d41004c75d92652dcbde86c84ac1c847dbd9ad59bd"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=3bf50002aefd002f49e7bb854063f7e7 \
> +                    file://libgupnp/gupnp.h;beginline=1;endline=20;md5=d78a69d9b6e63ee2dc72e7b674d97520"
> -- 
> 1.7.10.4
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-02-01 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 14:51 [PATCH 1/2][meta-multimedia] gupnp: Update to 0.20.14 Manuel Bachmann
2016-02-01 15:07 ` Martin Jansa [this message]
2016-02-02 15:19   ` Manuel Bachmann [ IoT.bzh ]

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=20160201150710.GC2639@jama \
    --to=martin.jansa@gmail.com \
    --cc=mbc@iot.bzh \
    --cc=openembedded-devel@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.