From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Koch, Stefan (DI PA DCP R&D 3)" <stefan-koch@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan (T CED EDC-DE)" <adriaan.schmidt@siemens.com>,
"amikan@ilbers.de" <amikan@ilbers.de>,
"Moessbauer, Felix (T CED OES-DE)" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH v2 0/5] More kbuild improvements, single-build source packages, cross profile fix
Date: Thu, 16 May 2024 18:37:26 +0200 [thread overview]
Message-ID: <d3a97e1d-d33d-48aa-bbc3-28ef19ea8d51@siemens.com> (raw)
In-Reply-To: <b84566e6-fc13-467d-816e-43f47f8ce1aa@siemens.com>
On 15.05.24 19:40, 'Jan Kiszka' via isar-users wrote:
> On 15.05.24 15:47, Koch, Stefan (DI PA DCP R&D 3) wrote:
>> Since applying this series, I get this build error:
>>
>> ERROR: linux-audis-kbuildtarget-5.10.209-audis-rtp-r0 do_dpkg_build:
>> ExecutionError('/home/z003jsce/kbuildboards/build/tmp/work/audis-
>> bullseye-latest-arm64/linux-audis-kbuildtarget/5.10.209-audis-rtp-
>> r0/temp/run.dpkg_runbuild.77935', 1, None, None)
>> ERROR: Logfile of failure stored in:
>> /home/z003jsce/kbuildboards/build/tmp/work/audis-bullseye-latest-
>> arm64/linux-audis-kbuildtarget/5.10.209-audis-rtp-
>> r0/temp/log.do_dpkg_build.77935
>> Log data follows:
>> | DEBUG: Executing python function sstate_task_prefunc
>> | DEBUG: Python function sstate_task_prefunc finished
>> | DEBUG: Executing python function do_dpkg_build
>> | DEBUG: Executing shell function dpkg_schroot_create_configs
>> | Creating /etc/schroot/chroot.d/isar-builder-cbda93bb-87d8-4b8d-ae73-
>> 2495897f4aaf-77935
>> | DEBUG: Shell function dpkg_schroot_create_configs finished
>> | DEBUG: Executing shell function dpkg_runbuild
>> | WARNING: Export of 'CCACHE_UMASK=000' detected, please migrate to
>> templates
>> | dpkg-parsechangelog: error: cannot open file
>> /home/z003jsce/kbuildboards/build/debian/changelog: No such file or
>> directory
>> | E: Could not parse
>> /home/z003jsce/kbuildboards/build/debian/changelog:
>> | WARNING: exit code 1 from a shell command.
>> | DEBUG: Executing shell function schroot_delete_configs
>> | Removing /etc/schroot/isar-builder-cbda93bb-87d8-4b8d-ae73-
>> 2495897f4aaf-77935
>> | Removing /etc/schroot/chroot.d/isar-builder-cbda93bb-87d8-4b8d-ae73-
>> 2495897f4aaf-77935
>> | DEBUG: Shell function schroot_delete_configs finished
>> | DEBUG: Python function do_dpkg_build finished
>> ERROR: Task
>> (virtual:kbuildtarget:/home/z003jsce/kbuildboards/build/../audis-
>> isar/recipes-kernel/linux/linux-audis.bb:do_dpkg_build) failed with
>> exit code '1'
>> NOTE: Tasks Summary: Attempted 97 tasks of which 0 didn't need to be
>> rerun and 1 failed.
>>
>
> Can you find a reproduction path with upstream? Or identify the required
> modification for it to trigger this? I suspect some downstream kernel
> recipe bits play an central role because we no longer run
> dpkg-parsechangelog in upstream do_dpkg_build.
>
Were you able to clarify what is needed to trigger this? As this series
fixes the remaining issues of the kbuild changes (to my best knowledge),
it would be good to have them ready ASAP.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-05-16 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 11:08 Jan Kiszka
2024-05-15 11:08 ` [PATCH v2 1/5] dpkg-base: Fix enabling of cross build profile Jan Kiszka
2024-05-16 6:06 ` Schmidt, Adriaan
2024-05-16 6:15 ` Jan Kiszka
2024-05-15 11:08 ` [PATCH v2 2/5] linux-custom: Model cross-built kbuild package separately Jan Kiszka
2024-05-15 11:08 ` [PATCH v2 3/5] linux-custom: Resolve native source package differences Jan Kiszka
2024-05-15 11:08 ` [PATCH v2 4/5] dpkg: Retrieve Debian source name from variable Jan Kiszka
2024-05-15 11:08 ` [PATCH v2 5/5] dpkg-source: Build source package only once Jan Kiszka
2024-05-17 12:21 ` Jan Kiszka
2024-05-15 13:47 ` [PATCH v2 0/5] More kbuild improvements, single-build source packages, cross profile fix Koch, Stefan
2024-05-15 17:40 ` Jan Kiszka
2024-05-16 16:37 ` Jan Kiszka [this message]
2024-05-17 9:03 ` Koch, Stefan
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=d3a97e1d-d33d-48aa-bbc3-28ef19ea8d51@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=stefan-koch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox