Skip to contentSkip to conversation

grub does not require freetype

PATCH In review Dan Callaghan 2 participants 2 messages Sep 16, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 grub does not require freetype

Freetype is only needed for the grub-mkfont utility, but that is disabled at configure time by passing --disable-grub-mkfont.

---
 meta/recipes-bsp/grub/grub-efi_2.04.bb | 2 +-
 meta/recipes-bsp/grub/grub_2.04.bb     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
meta/recipes-bsp/grub/grub-efi_2.04.bb +1 -1
index aaa198ea23..e3a8bf39ab 100644
@@ -3,7 +3,7 @@ require grub2.inc
 GRUBPLATFORM = "efi"
 
 DEPENDS_append_class-target = " grub-efi-native"
-RDEPENDS_${PN}_class-target = "diffutils freetype grub-common virtual/grub-bootconf"
+RDEPENDS_${PN}_class-target = "diffutils grub-common virtual/grub-bootconf"
 
 SRC_URI += " \
            file://cfg \
meta/recipes-bsp/grub/grub_2.04.bb +1 -1
index 1d1a45670c..3166d1f2fb 100644
@@ -1,7 +1,7 @@
 require grub2.inc
 
 RDEPENDS_${PN}-common += "${PN}-editenv"
-RDEPENDS_${PN} += "diffutils freetype ${PN}-common"
+RDEPENDS_${PN} += "diffutils ${PN}-common"
 
 RPROVIDES_${PN}-editenv += "${PN}-efi-editenv"
 
Signature · 1 line
2.20.1
#1 lore raw

✗ patchtest: failure for grub does not require freetype

== Series Details ==

Series: grub does not require freetype
Revision: 1
URL : https://patchwork.openembedded.org/series/19959/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Patch            grub does not require freetype
 Issue             Shortlog does not follow expected format [test_shortlog_format] 
  Suggested fix    Commit shortlog (first line of commit message) should follow the format "<target>: <summary>"
* Patch            grub does not require freetype
 Issue             Patch is missing Signed-off-by [test_signed_off_by_presence] 
  Suggested fix    Sign off the patch (either manually or with "git commit --amend -s")

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe