From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-gnome][PATCH 1/2] gnome-vfs 2.24.4: drop useless print
Date: Tue, 7 Jun 2016 13:40:32 +0200 [thread overview]
Message-ID: <5756B2B0.4020804@mlbassoc.com> (raw)
In-Reply-To: <1465288732-2288-1-git-send-email-koen.kooi@linaro.org>
On 2016-06-07 10:38, Koen Kooi wrote:
> This fixes the python3 traceback.
RP already sent patches for this and the other python3 related issue.
>
> Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
> ---
> meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb b/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb
> index f9b02b1..1c78474 100644
> --- a/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb
> +++ b/meta-gnome/recipes-gnome/gnome-vfs/gnome-vfs_2.24.4.bb
> @@ -53,8 +53,6 @@ FILES_${PN}-doc += "${datadir}/gtk-doc"
> PACKAGES_DYNAMIC += "^gnome-vfs-plugin-.*"
>
> python populate_packages_prepend () {
> - print d.getVar('FILES_gnome-vfs', 1)
> -
> plugindir = d.expand('${libdir}/gnome-vfs-2.0/modules/')
> do_split_packages(d, plugindir, '^lib(.*)\.so$', 'gnome-vfs-plugin-%s', 'GNOME VFS plugin for %s')
> }
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-06-07 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 8:38 [meta-gnome][PATCH 1/2] gnome-vfs 2.24.4: drop useless print Koen Kooi
2016-06-07 8:38 ` [meta-gnome][PATCH 2/2] abiword 3.0.1: fix python code to work with python3 Koen Kooi
2016-06-07 11:40 ` Gary Thomas [this message]
2016-06-08 20:09 ` [meta-gnome][PATCH 1/2] gnome-vfs 2.24.4: drop useless print Koen Kooi
2016-06-08 20:56 ` Martin Jansa
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=5756B2B0.4020804@mlbassoc.com \
--to=gary@mlbassoc.com \
--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.