From: Derek Straka <derek@asterius.io>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 2/3] font-bh-lucidatypewriter-100dpi: update depends to fix builds with RSS
Date: Fri, 24 Feb 2017 18:09:54 -0500 [thread overview]
Message-ID: <1487977795-2611-2-git-send-email-derek@asterius.io> (raw)
In-Reply-To: <1487977795-2611-1-git-send-email-derek@asterius.io>
Resolves build issue exposed by RSS
See http://errors.yoctoproject.org/Errors/Details/130625/
Signed-off-by: Derek Straka <derek@asterius.io>
---
.../xorg-font/font-bh-lucidatypewriter-100dpi_1.0.3.bb | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/meta-oe/recipes-graphics/xorg-font/font-bh-lucidatypewriter-100dpi_1.0.3.bb b/meta-oe/recipes-graphics/xorg-font/font-bh-lucidatypewriter-100dpi_1.0.3.bb
index bffeb95..6e0b33c 100644
--- a/meta-oe/recipes-graphics/xorg-font/font-bh-lucidatypewriter-100dpi_1.0.3.bb
+++ b/meta-oe/recipes-graphics/xorg-font/font-bh-lucidatypewriter-100dpi_1.0.3.bb
@@ -6,7 +6,7 @@ SECTION = "x11/font"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=0d221a9cd144806cb469735cc4775939"
-DEPENDS = "util-macros-native font-util-native bdftopcf-native"
+DEPENDS = "util-macros-native font-util-native bdftopcf-native font-util"
RDEPENDS_${PN} = "encodings font-util"
RDEPENDS_${PN}_class-native = "font-util-native"
@@ -16,5 +16,3 @@ REQUIRED_DISTRO_FEATURES = "x11"
SRC_URI[md5sum] = "c8b73a53dcefe3e8d3907d3500e484a9"
SRC_URI[sha256sum] = "62a83363c2536095fda49d260d21e0847675676e4e3415054064cbdffa641fbb"
-
-PNBLACKLIST[font-bh-lucidatypewriter-100dpi] ?= "Fails to build with RSS http://errors.yoctoproject.org/Errors/Details/130625/"
--
2.7.4
next prev parent reply other threads:[~2017-02-24 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 23:09 [meta-oe][PATCH 1/3] font-misc-misc: update depends to fix builds with RSS Derek Straka
2017-02-24 23:09 ` Derek Straka [this message]
2017-02-24 23:09 ` [meta-oe][PATCH 3/3] font-bh-100dpi: " Derek Straka
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=1487977795-2611-2-git-send-email-derek@asterius.io \
--to=derek@asterius.io \
--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