public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/3] Fix gbp patching after configuration change
Date: Fri, 17 Sep 2021 11:51:38 +0300	[thread overview]
Message-ID: <05e4ed9c-c315-dc9a-e4b8-1f0653b98c65@ilbers.de> (raw)
In-Reply-To: <20210911175119.5910-1-ubely@ilbers.de>

11.09.2021 20:51, Uladzimir Bely wrote:
> Changes since v1:
>   - rebased on latest `next`
>   - changed dat from RFC to PATCH
>
> Attempt to rebuild ISAR after some changes in local.conf was leading
> to failure on `cowsay` package because of an attempt to apply
> custom patch while it was already applied at first build.
>
> The problem was in isar.patch format - it used `git` as PATCHTOOL
> but was not in format compatible with `git am`. So the fallback way
> of patching was used.
>
> The series fixes isar.patch format, adds CI test for this condition
> and adds an appropriate section to the documentation
>
> Uladzimir Bely (3):
>    meta-isar: reformat isar.patch for cowsay to properly work with git
>    ci: Test for rebuild with no cleanup after configuration change
>    doc: Add a section on gbp-compatible packages
>
>   doc/user_manual.md                            | 15 +++++++++
>   meta-isar/recipes-app/cowsay/files/isar.patch | 32 +++++++++++++++----
>   scripts/ci_build.sh                           | 11 ++++---
>   3 files changed, 47 insertions(+), 11 deletions(-)
>
Applied to next, thanks.

-- 
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov


      parent reply	other threads:[~2021-09-17  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 17:51 Uladzimir Bely
2021-09-11 17:51 ` [PATCH v2 1/3] meta-isar: reformat isar.patch for cowsay to properly work with git Uladzimir Bely
2021-09-11 17:51 ` [PATCH v2 2/3] ci: Test for rebuild with no cleanup after configuration change Uladzimir Bely
2021-09-11 17:51 ` [PATCH v2 3/3] doc: Add a section on gbp-compatible packages Uladzimir Bely
2021-09-17  8:51 ` Anton Mikanovich [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=05e4ed9c-c315-dc9a-e4b8-1f0653b98c65@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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