From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: dpkg:do_patch failure with today's updates to dizzy branch
Date: Sat, 18 Apr 2015 09:01:01 +0100 [thread overview]
Message-ID: <1429344061.6976.209.camel@linuxfoundation.org> (raw)
In-Reply-To: <0D818C7A2259ED42912C1E04120FDE26710A76BB@ORSMSX111.amr.corp.intel.com>
On Fri, 2015-04-17 at 23:05 +0000, Chatre, Reinette wrote:
> Today there was an update to the dizzy branch that includes the patch below:
>
> [...]
>
> Unfortunately the patch introduced by this commit does not apply cleanly to the version of dpkg that can be found in dizzy release. It seems that the patch was generated against dpkg version 1.17.21 while dizzy uses version 1.17.4. The build fails with:
>
> NOTE: Applying patch 'tar-error-code.patch' (../meta/recipes-devtools/dpkg/dpkg/tar-error-code.patch)
> ERROR: Command Error: exit status: 1 Output:
> Applying patch tar-error-code.patch
> patching file dpkg-deb/build.c
> Hunk #1 succeeded at 443 (offset 45 lines).
> Hunk #2 FAILED at 493.
> Hunk #3 FAILED at 581.
> 2 out of 3 hunks FAILED -- rejects in file dpkg-deb/build.c
> Patch tar-error-code.patch does not apply (enforce with -f)
There was a mixup with some branches unfortunately but the correct patch
is now on the branch and this should be fixed. Thanks for reporting.
Cheers,
Richard
prev parent reply other threads:[~2015-04-18 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 23:05 dpkg:do_patch failure with today's updates to dizzy branch Chatre, Reinette
2015-04-18 8:01 ` Richard Purdie [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=1429344061.6976.209.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=reinette.chatre@intel.com \
/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