From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/4] Make adjust_git work in both worlds
Date: Fri, 13 Aug 2021 05:40:42 -0700 (PDT) [thread overview]
Message-ID: <9030e8b4-5a26-42b8-bca4-7e07977044b1n@googlegroups.com> (raw)
In-Reply-To: <3665f9de-913c-620c-0327-61894494bbe6@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1856 bytes --]
When I previously looked at patch.bbclass, I noted, that we don't use it
completely.
There are some patch_task_patch_prefunc() and patch_task_postfunc() here
that are used in OE when PATCHTOOL='git'. But in our case they are never
run due to not using PATCH_COMMIT_FUNCTIONS in isar.
I suppose (but can't be completely sure without deep look to OE) that
prefunc may fix this 'patch is allready applied' issue in OE.
On Friday, August 13, 2021 at 3:28:45 PM UTC+3 Jan Kiszka wrote:
> On 13.08.21 14:23, Uladzimir Bely wrote:
> > In addition to this series we still need something like I had done in
> > "[RFC,2/2] dpkg-gdb: Reset git to SRCREV revision before patching".
> >
> > Because the problem with git has gone, but there is a problem that we
> > try apply patch on top of git tree where it's already applied.
> >
> > Steps to reproduce are quite simple:
> >
> > - Run first build: bitbake mc:qemuamd64-buster:isar-image-base
> > - Modify local.conf (e.g. set ISAR_USE_CACHED_BASE_REPO ?= "1" or do
> > something else that will cause packages rebuild)
> > - Run second build: bitbake mc:qemuamd64-buster:isar-image-base
> >
> > It ends up with:
> >
> > ERROR:mc:qemuamd64-buster:cowsay-git-r0 do_patch: Applying 'isar.patch'
> > failed:
> > The next patch would create the file debian/patches/isar.patch,
> > which already exists! Assume -R? [n]
> >
> > In CI tests we remove build/tmp, so that we don't face this problem.
> >
>
> This is supposed to be handled by the patch class - when it works
> properly. Please check if quilt-based patching addresses this and only
> git is affected and, if yes, also cross-check how that works in OE. We
> either miss something from OE while using their patch class or there is
> actually an upstream issue.
>
> Jan
>
> --
> Siemens AG, T RDA IOT
> Corporate Competence Center Embedded Linux
>
[-- Attachment #1.2: Type: text/html, Size: 2351 bytes --]
next prev parent reply other threads:[~2021-08-13 12:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 11:48 Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 1/4] dpkg-base: Lock do_adjust_git against each other Jan Kiszka
2021-08-13 13:55 ` Henning Schild
2021-08-15 18:55 ` Jan Kiszka
2021-08-26 8:00 ` [PATCH v3 " Jan Kiszka
2021-08-26 8:06 ` Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 2/4] dpkg-base: Make mirror link relative Jan Kiszka
2021-08-13 14:04 ` Henning Schild
2021-08-13 17:49 ` [PATCH] dpkg-base: "unshare" git clones in adjust_git Henning Schild
2021-08-13 20:13 ` [PATCH v2] " Henning Schild
2021-08-13 20:14 ` Henning Schild
2021-08-15 18:55 ` [PATCH] " Jan Kiszka
2021-08-16 11:36 ` Henning Schild
2021-08-16 16:57 ` Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 3/4] Rework do_adjust_git to support inside and outside usage Jan Kiszka
2021-08-12 11:48 ` [PATCH v2 4/4] Revert "dpkg: adjust task order to allow using "git" for patching" Jan Kiszka
2021-08-13 8:31 ` [PATCH v2 0/4] Make adjust_git work in both worlds Uladzimir Bely
2021-08-13 10:13 ` Jan Kiszka
2021-08-13 12:23 ` Uladzimir Bely
2021-08-13 12:28 ` Jan Kiszka
2021-08-13 12:40 ` Uladzimir Bely [this message]
2021-08-15 19:02 ` Jan Kiszka
2021-08-16 7:52 ` Uladzimir Bely
2021-08-16 7:55 ` Jan Kiszka
2021-08-16 8:27 ` Uladzimir Bely
2021-08-16 10:45 ` Jan Kiszka
2021-08-16 11:01 ` Jan Kiszka
2021-08-16 11:26 ` Henning Schild
2021-08-16 12:49 ` Uladzimir Bely
2021-08-19 6:17 ` Uladzimir Bely
2021-08-19 6:21 ` Jan Kiszka
2021-08-26 7:57 ` Jan Kiszka
2021-08-27 8:39 ` ub...@ilbers.de
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=9030e8b4-5a26-42b8-bca4-7e07977044b1n@googlegroups.com \
--to=ubely@ilbers.de \
--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