From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>,
Tim Orling <ticotimo@gmail.com>
Cc: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] conf: add new debian version "bookworm"
Date: Fri, 17 Sep 2021 12:22:07 +0200 [thread overview]
Message-ID: <a15c1947-8d4d-b8d4-d0de-79a75b7937dd@siemens.com> (raw)
In-Reply-To: <20210917094520.730dce65@md1za8fc.ad001.siemens.net>
On 17.09.21 09:45, Henning Schild wrote:
> Am Thu, 16 Sep 2021 18:48:30 -0700
> schrieb Tim Orling <ticotimo@gmail.com>:
>
>> On Thu, Sep 16, 2021 at 6:18 AM Anton Mikanovich <amikan@ilbers.de>
>> wrote:
>>
>>> 14.09.2021 13:35, Henning Schild wrote:
>>>> Add all configuration files and CI targets.
>>>>
>>>> Signed-off-by: Henning Schild <henning.schild@siemens.com>
>>>
>>> We are almost ready to migrate on Avocado and adding bookworm
>>> supposed to be the next step after that.
>>> So I can prepare v12 rebased on this patch to have Avocado upped to
>>> date when it will be ok to merge next week.
>>> Or we can only add bookworm into avocado CI implementation and keep
>>> legacy shell script as is.
>>>
>>> After merging Avocado I will send full test cases regroup RFC,
>>> because current one don't even cover all the targets but have
>>> already become too heavy.
>>>
>>
>> Can someone please revisit debian-sid-ports and add tests for it? I
>> hacked it to work locally (archive 2021 key and “buster” InRelease
>> key), but I am not familiar enough to know what is hack and what was
>> necessary. Proving sifive-fu540 is buildable should be enough.
>
> Can you maybe describe the problem you have with it? My guess is that
> it might not build anymore because sid switched from bullseye to
> bookworm and probably switched keys. As far as i can see there seems to
> be no CI testing for it.
>
> But i am just guessing here. Maybe start with the problem and repro
> steps.
The problem is that riscv64 is still only an inofficial port, forcing
you to go to sid. I recently wondered with some local Debian folks what
all might be missing, more builder or more people, but no one in that
round was aware of the background.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-09-17 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 10:35 Henning Schild
2021-09-16 13:17 ` Anton Mikanovich
2021-09-17 1:48 ` Tim Orling
2021-09-17 7:45 ` Henning Schild
2021-09-17 10:22 ` Jan Kiszka [this message]
2021-09-17 8:12 ` Anton Mikanovich
2021-09-17 16:25 ` Anton Mikanovich
2021-09-17 16:43 ` Jan Kiszka
2021-09-17 18:29 ` Tim Orling
2021-09-17 7:19 ` Henning Schild
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=a15c1947-8d4d-b8d4-d0de-79a75b7937dd@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ticotimo@gmail.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