From: "Kevin Hilman" <khilman@baylibre.com>
To: Karsten Merker <merker@debian.org>,
Aurelien Jarno <aurelien@aurel32.net>,
David Abdurachmanov <david.abdurachmanov@sifive.com>,
Atish Patra <Atish.Patra@wdc.com>,
"drew@beagleboard.org" <drew@beagleboard.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
"lakshmipathi.ganapathi@collabora.co.uk"
<lakshmipathi.ganapathi@collabora.co.uk>,
"kernelci@groups.io" <kernelci@groups.io>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"raj.khem@gmail.com" <raj.khem@gmail.com>,
"clabbe@baylibre.com" <clabbe@baylibre.com>,
Manuel Montecelo <mafm@debian.org>,
Karsten Merker <merker@debian.org>
Cc: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Subject: Re: Improve kernelci setup for RISC-V
Date: Thu, 02 Jul 2020 11:25:33 -0700 [thread overview]
Message-ID: <7hmu4hixk2.fsf@baylibre.com> (raw)
In-Reply-To: <20200702181553.GA3226@aletheia.cgn.bolug.org>
Karsten Merker <merker@debian.org> writes:
> On Thu, Jul 02, 2020 at 04:49:55PM +0200, Aurelien Jarno wrote:
>> On 2020-07-02 10:12, David Abdurachmanov wrote:
> [...]
>> > Recap: KernelCI uses Debian debootstrap for their test infrastructure.
>> > I believe they are using Buster for it now.
>> >
>> > On Thu, Jul 2, 2020 at 10:02 AM Atish Patra <Atish.Patra@wdc.com> wrote:
>> > > On Wed, 2020-07-01 at 17:17 -0700, Kevin Hilman wrote:
>> > > > Atish Patra <Atish.Patra@wdc.com> writes:
> [...]
>> > > > > The main blocker here is the rootfs. As kernelci only
>> > > > > supports debian based rootfs to actually run tests. I think
>> > > > > it is not that difficult to bootstrap a debian rootfs for
>> > > > > RISC-V but I have not done that in ages. I think palmer uses
>> > > > > debian rootfs for his testing. I have cc'd him for his
>> > > > > inputs.
>> > > >
>> > > > For every other arch, we debootstrap a buster rootfs, and this
>> > > > doesn't work for riscv. But, I just discovered[1] that this
>> > > > should work for unstable using debian-ports, so we'll need to
>> > > > update our rootfs builder to support unstable/debian-ports.
>> > > >
>> > > > I've cc'd Lakshmipathi from Collabora who has been doing work
>> > > > on our rootfs builder tool to see how we can extend this.
>
>> Yes, so far the riscv64 port of debian is only available for the sid
>> distribution. debootstrap should work fine in general (I have just
>> tested now), but it might break from time to time (I hope rarely).
>> Do not hesitate to contact us if it happens. In short just use
>> debian-ports/ in the URL instead of debian/, for example
>> https://deb.debian.org/debian-ports
>
> Hello,
>
> I don't know how strongly the kernelci infrastructure is bound to using
> debootstrap for creating a Debian rootfs, but if you need to make
> adjustments anyway for using the debian-ports archive, using mmdebstrap
> instead of debootstrap for debian-ports architectures such as riscv64
> might be worth a thought.
We're currently relying on the debos tool[1] which itself uses
debootstrap under the hood. I've cc'd some developers of debos to see
it they have any thoughts about using mmdepbstrap instead.
Kevin
[1] https://github.com/go-debos/debos
next prev parent reply other threads:[~2020-07-02 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3c2cba2849caa6ea0116611c1da3268b41432b76.camel@wdc.com>
2020-07-02 0:17 ` Improve kernelci setup for RISC-V Kevin Hilman
2020-07-02 7:02 ` Atish Patra
2020-07-02 7:12 ` David Abdurachmanov
2020-07-02 13:19 ` David Abdurachmanov
2020-07-02 14:50 ` Aurelien Jarno
2020-07-02 14:55 ` Colin Ian King
2020-07-02 14:49 ` Aurelien Jarno
2020-07-02 18:15 ` Karsten Merker
2020-07-02 18:25 ` Kevin Hilman [this message]
2020-07-02 20:15 ` Manuel A. Fernandez Montecelo
2020-07-08 23:31 ` Manuel A. Fernandez Montecelo
2020-07-09 6:52 ` Lakshmipathi Ganapathi
2020-07-02 20:19 ` Alistair Francis
2020-07-02 15:49 ` Khem Raj
2020-07-02 11:24 ` Mark Brown
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=7hmu4hixk2.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Alistair.Francis@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=aurelien@aurel32.net \
--cc=clabbe@baylibre.com \
--cc=david.abdurachmanov@sifive.com \
--cc=drew@beagleboard.org \
--cc=kernelci@groups.io \
--cc=lakshmipathi.ganapathi@collabora.co.uk \
--cc=mafm@debian.org \
--cc=merker@debian.org \
--cc=palmer@dabbelt.com \
--cc=raj.khem@gmail.com \
--cc=sjoerd.simons@collabora.co.uk \
/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.