public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v5] u-boot: Deprecate BUILD_DEPENDS in favor of DEBIAN_BUILD_DEPENDS
Date: Fri, 6 Nov 2020 09:51:30 +0100	[thread overview]
Message-ID: <ef1193aa-8915-bbf0-924d-f17e258af23e@siemens.com> (raw)
In-Reply-To: <20201105142911.GL5078@yssyq.m.ilbers.de>

On 05.11.20 15:29, Baurzhan Ismagulov wrote:
> On Wed, Nov 04, 2020 at 10:47:42AM +0100, Jan Kiszka wrote:
>> Aligns this recipe with deb_debianize. Provide a compat path along with
>> a warning to ease migration.
> 
> Hmm, git am 13.txt failed for me:
> 
> Applying: u-boot: Deprecate BUILD_DEPENDS in favor of DEBIAN_BUILD_DEPENDS
> error: corrupt patch at line 35
> Patch failed at 0001 u-boot: Deprecate BUILD_DEPENDS in favor of DEBIAN_BUILD_DEPENDS
> hint: Use 'git am --show-current-patch' to see the failed 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".
> 
> patch -p1 <13.txt failed as well:
> 
> patching file RECIPE-API-CHANGELOG.md
> patching file meta/recipes-bsp/u-boot/files/debian/control.tmpl
> patch: **** malformed patch at line 183: diff --git a/meta/recipes-bsp/u-boot/u-boot-custom.inc b/meta/recipes-bsp/u-boot/u-boot-custom.inc
> 
> I've rebased v4 and applied to next as below. After a quick check, all changes
> seem to be in, but you might want to check as well.
> 

Thanks for fixing up! I rebased locally, and that went smoothly.

Apparently, I have local tooling issue with routing out my patches.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

      reply	other threads:[~2020-11-06  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04  9:47 Jan Kiszka
2020-11-05 14:29 ` Baurzhan Ismagulov
2020-11-06  8:51   ` Jan Kiszka [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=ef1193aa-8915-bbf0-924d-f17e258af23e@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.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