From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
felix.moessbauer@siemens.com, cip-dev@lists.cip-project.org
Subject: Re: [cip-dev][isar-cip-core][PATCH v4] efibootguard: use debian folder from salsa
Date: Mon, 24 Apr 2023 10:31:56 +0200 [thread overview]
Message-ID: <cb6b51f2-be45-d758-e718-c18fdd37c4de@siemens.com> (raw)
In-Reply-To: <f4ec927f-5d19-48e3-84ec-b8dea9b5c13e@siemens.com>
On 4/21/23 19:56, Jan Kiszka wrote:
> On 21.04.23 16:13, Quirin Gylstorff wrote:
>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>
>> To avoid package name conflicts between cip-core and Debian upstream
>> use the debian folder from upstream to build efibootguard.
>>
>> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>> ---
>> Changes v4:
>> - readd patch 0002-d-control-remove-native-from-python3-shtab.patch to
>> allow build for qemu-arm64 and qemu-arm. see https://gitlab.com/cip-project/cip-core/isar-cip-core/-/pipelines/844580247
>
> Is that patch also upstream relevant? Or is that only needed for older
This looks like a conflict with crossbuilding the package in ISAR. The
error does not occur on upstream as upstream builds the package native.
I need to test if the patch is necessary for bookworm.
Quirin
> bullseye/buster?
>
> Jan
>
next prev parent reply other threads:[~2023-04-24 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:13 [cip-dev][isar-cip-core][PATCH v4] efibootguard: use debian folder from salsa Quirin Gylstorff
2023-04-21 17:56 ` Jan Kiszka
2023-04-24 8:31 ` Gylstorff Quirin [this message]
2023-04-24 8:50 ` Moessbauer, Felix
2023-04-24 11:55 ` Jan Kiszka
2023-04-24 14:41 ` Gylstorff Quirin
2023-04-23 5:11 ` Moessbauer, Felix
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=cb6b51f2-be45-d758-e718-c18fdd37c4de@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.