From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev, ross@kallisti.us
Cc: mcgrof@kernel.org
Subject: [PATCH kdevops 4/4] guestfs: make debian trixie default
Date: Thu, 10 Oct 2024 18:01:11 -0700 [thread overview]
Message-ID: <20241011010111.3543993-5-mcgrof@kernel.org> (raw)
In-Reply-To: <20241011010111.3543993-1-mcgrof@kernel.org>
kdevops relies on rolling distributions. We've been stuck with
debian12 because that's what the virt-builder servers have and
it's a bit old for our taste in kernel hacking the latest and
greatest kernels.
Since we are now boosting efforts on CI kernel hacking testing,
we want to make bringup as fast as possible, and since the first
thing we typically want is the *latest and greatest* we tend to
sometimes upgrade a system on bringup. Even if we skip that,
buster 12 default is still a bit... old... and so to help speed
up bringup in both cases where we just want the latest debian
testing *or* an updated system, make debian 13 trixie the default
image now that we've fixed it.
Tested with:
make linux
make fstests
And we've been running tests on guests where the host is trixie and the
guest is debian 12 (buster) but then due to the host having a local apt
mirror, we rely on CONFIG_GUESTFS_COPY_SOURCES_FROM_HOST_TO_GUEST to
do immediately do upgrades from debian 12 --> debian 13. And debian 13
has been tested for many of our workflows including the latest sysbench
workflow.
So all in all, debian trixie has been being tested for a while, it was
just this painful upgrade process we've had to deal with for a long
time.
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
kconfigs/Kconfig.guestfs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kconfigs/Kconfig.guestfs b/kconfigs/Kconfig.guestfs
index da2f5e3961d7..a804c8fce2fd 100644
--- a/kconfigs/Kconfig.guestfs
+++ b/kconfigs/Kconfig.guestfs
@@ -83,7 +83,7 @@ if GUESTFS_DEBIAN
choice
prompt "Debian version"
- default GUESTFS_DEBIAN_BUSTER
+ default GUESTFS_DEBIAN_TRIXIE
config GUESTFS_DEBIAN_TRIXIE
bool "Debian 13 - Trixie"
--
2.43.0
next prev parent reply other threads:[~2024-10-11 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 1:01 [PATCH kdevops 0/4] kdevops: make trixie default Luis Chamberlain
2024-10-11 1:01 ` [PATCH kdevops 1/4] guestfs: make trixie generic image the default Luis Chamberlain
2024-10-11 1:01 ` [PATCH kdevops 2/4] guestfs: fix uefi boot for debian trixie Luis Chamberlain
2024-10-11 1:01 ` [PATCH kdevops 3/4] guestfs: fix trixie bringup Luis Chamberlain
2024-10-11 1:01 ` Luis Chamberlain [this message]
2024-10-11 19:00 ` [PATCH kdevops 0/4] kdevops: make trixie default Luis Chamberlain
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=20241011010111.3543993-5-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=ross@kallisti.us \
/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