From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 10/11] geany-plugins: blacklist because of QA issues
Date: Wed, 31 Aug 2016 21:41:05 +0200 [thread overview]
Message-ID: <20160831194106.14065-10-Martin.Jansa@gmail.com> (raw)
In-Reply-To: <20160831194106.14065-1-Martin.Jansa@gmail.com>
geany-plugins_1.27.bb: LICENSE_geany-plugins-pairtaghighlighter includes licenses (BSD-2-Clause) that are not listed in LICENSE
geany-plugins-1.27: geany-plugins: Files/directories were installed but not shipped in any package:
/usr/lib/geany/git-changebar.so
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
geany-plugins: 1 installed and not shipped files. [installed-vs-shipped]
geany-plugins-1.27: geany-plugins-scope rdepends on libvte9, but it isn't a build dependency, missing vte9 in DEPENDS or PACKAGECONFIG? [build-deps]
geany-plugins-1.27: geany-plugins-debugger rdepends on libvte9, but it isn't a build dependency, missing vte9 in DEPENDS or PACKAGECONFIG? [build-deps]
geany-plugins-1.27: geany-plugins-multiterm rdepends on libvte9, but it isn't a build dependency, missing vte9 in DEPENDS or PACKAGECONFIG? [build-deps]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb b/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb
index b56d8f4..0e333c7 100644
--- a/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb
+++ b/meta-oe/recipes-devtools/geany/geany-plugins_1.27.bb
@@ -218,3 +218,5 @@ RDEPENDS_${PN}-xmlsnippets = "${PN}"
PACKAGES =+ "${PLUGINS}"
RDEPENDS_${PN} = "${PLUGINS}"
ALLOW_EMPTY_${PN} = "1"
+
+PNBLACKLIST[geany-plugins] ?= "Causes multiple QA errors and LICENSE warnings"
--
2.9.2
next prev parent reply other threads:[~2016-08-31 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 19:40 [meta-oe][PATCH 01/11] xf86-input-tslib: remove Martin Jansa
2016-08-31 19:40 ` [meta-oe][PATCH 02/11] efl: remove dependency on tslib Martin Jansa
2016-08-31 19:40 ` [meta-oe][PATCH 03/11] directfb: add PACKAGECONFIG for inputdrivers Martin Jansa
2016-08-31 19:40 ` [meta-oe][PATCH 04/11] gpsd, foxtrotgps: blacklist, fails to build with new binutils-2.27 Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 05/11] gnome-menus, gnome-panel3, gnome-control-center: blacklist, gnome-menus fails to build because of python Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 06/11] accel-ppp: blacklist, fails to build with new binutils-2.27 Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 07/11] samba: " Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 08/11] glmark2: blacklist, fails to build with gcc-6 Martin Jansa
2016-08-31 19:41 ` [meta-oe][PATCH 09/11] tracker: blacklist, fails to build with new binutils-2.27 Martin Jansa
2016-08-31 19:41 ` Martin Jansa [this message]
2016-08-31 21:16 ` [meta-oe][PATCH 10/11] geany-plugins: blacklist because of QA issues Andreas Müller
2016-08-31 19:41 ` [meta-oe][PATCH 11/11] smbnetfs: blacklist, depends on broken samba Martin Jansa
2016-09-04 4:03 ` [meta-oe][PATCH 01/11] xf86-input-tslib: remove Jonathan Liu
2016-09-04 10:06 ` 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=20160831194106.14065-10-Martin.Jansa@gmail.com \
--to=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox