From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] directfb: move recipe to meta-oe
Date: Tue, 12 Jul 2016 14:00:48 +0300 [thread overview]
Message-ID: <20160712110048.GA26262@mbabyjoh-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20160711143536.s6nx2scag4j7sffc@jama>
Hi Martin,
On Mon, Jul 11, 2016 at 04:35:37PM +0200, Martin Jansa wrote:
> On Mon, Jul 04, 2016 at 04:45:53PM +0300, Maxin B. John wrote:
> > directfb.org has been down for about a year now. Since there
> > are active users for this recipe, it makes sense to move this
> > from oe-core to meta-oe.
>
> Fails to apply:
>
> OE @ ~/meta-openembedded $ pwam 126087
> 2016-07-11 15:29:51 URL:https://patchwork.openembedded.org/patch/126087/mbox/ [33428] -> "pw-am-126087.patch" [1]
> Applying: directfb: move recipe to meta-oe
> .git/rebase-apply/patch:51: trailing whitespace.
>
> .git/rebase-apply/patch:53: trailing whitespace.
>
> .git/rebase-apply/patch:56: space before tab in indent.
> AC_MSG_ERROR([$DIRECTFB_PKG_ERRORS
> .git/rebase-apply/patch:59: trailing whitespace.
> --
> .git/rebase-apply/patch:207: trailing whitespace.
>
> fatal: corrupt patch at line 401
> Patch failed at 0001 directfb: move recipe to meta-oe
> The copy of the patch that failed is found in: .git/rebase-apply/patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> OE @ ~/meta-openembedded $ patch -p1 < pw-am-126087.patch
> patching file meta-oe/recipes-graphics/directfb/directfb-examples/configure.in-Fix-string-argument-syntax.patch
> patching file meta-oe/recipes-graphics/directfb/directfb-examples_1.7.0.bb
> patching file meta-oe/recipes-graphics/directfb/directfb.inc
> patching file meta-oe/recipes-graphics/directfb/directfb/0001-gfx-direct-Aboid-usng-VLAs-and-printf-formats.patch
> patching file meta-oe/recipes-graphics/directfb/directfb/bashism.patch
> patching file meta-oe/recipes-graphics/directfb/directfb/compar_fn_t.patch
> patching file meta-oe/recipes-graphics/directfb/directfb/configurefix.patch
> patch: **** malformed patch at line 360: ages-split/directfb/usr/bin/dfbscreen contains probably-redundant RPATH /usr/libWARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/bin/mkdgiff contains probably-redundant RPATH /usr/libWARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/bin/dfbinspector contains probably-redundant RPATH /usr/lib
>
> Because there is extra line feed in
> meta-oe/recipes-graphics/directfb/directfb/configurefix.patch
> (very long line), please check your sender configuration to prevent mangling the patches in future.
Sorry for that. I had to send the patch with "--no-validate" option because it
contained lines longer than 998 characters.
> This time I've fixed and applied it manually.
Thank you very much.
Best Regards,
Maxin
prev parent reply other threads:[~2016-07-12 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 13:45 [PATCH] directfb: move recipe to meta-oe Maxin B. John
2016-07-11 14:35 ` Martin Jansa
2016-07-12 11:00 ` Maxin B. John [this message]
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=20160712110048.GA26262@mbabyjoh-desk.ger.corp.intel.com \
--to=maxin.john@intel.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