Skip to content

Enable trixie backports#2872

Open
grandpaul wants to merge 2 commits into
google:mainfrom
grandpaul:paulliu-enable-trixie-backports
Open

Enable trixie backports#2872
grandpaul wants to merge 2 commits into
google:mainfrom
grandpaul:paulliu-enable-trixie-backports

Conversation

@grandpaul

Copy link
Copy Markdown
Collaborator

We enable backports on Trixie so that we can install newer kernel.
Also we fix the unit tests because the download scripts needs to be updated.

@grandpaul grandpaul added the kokoro:run Run e2e tests. label Jul 19, 2026
@GoogleCuttlefishTesterBot GoogleCuttlefishTesterBot removed the kokoro:run Run e2e tests. label Jul 19, 2026
@rmuthiah
rmuthiah force-pushed the paulliu-enable-trixie-backports branch from f1d34ed to 0198ab3 Compare July 21, 2026 18:50
@rmuthiah rmuthiah added kokoro:force-run Trigger a presubmit build unconditionally. kokoro:run Run e2e tests. labels Jul 21, 2026
@rmuthiah
rmuthiah requested review from dimorinny and rmuthiah July 21, 2026 18:54
@GoogleCuttlefishTesterBot GoogleCuttlefishTesterBot removed kokoro:run Run e2e tests. kokoro:force-run Trigger a presubmit build unconditionally. labels Jul 21, 2026
Ying-Chun Liu (PaulLiu) added 2 commits July 22, 2026 14:47
It seems that the nVidia driver are working now in trixie-backports.
Turn on backports so we can have newer version of kernel.

Signed-off-by: Ying-Chun Liu (PaulLiu) <liupa@google.com>
…SON API

The previous way to download the artifacts doesn't work.
We fix it by using the latest JSON API. And also make the
script more verbose on error.

Signed-off-by: Ying-Chun Liu (PaulLiu) <liupa@google.com>
@rmuthiah
rmuthiah force-pushed the paulliu-enable-trixie-backports branch from 0198ab3 to df0a4f9 Compare July 22, 2026 18:47
@rmuthiah
rmuthiah enabled auto-merge July 22, 2026 18:47
d-i apt-setup/cdrom/set-first boolean false
# Backport selection
# d-i apt-setup/services-select multiselect backports
d-i apt-setup/services-select multiselect backports

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By doing so, it becomes much harder to predict which kernel version we'll end up with, given how frequently backports are updated. For example, we might make an unrelated change to the installer, but simply rebuilding it later could trigger an unexpected major kernel upgrade. In fact, I booted a QEMU VM using this installer and it actually installed kernel 7.0.13 (since 11 Jul 2026), rather than 6.18 as expected.

I'm still figuring out what a good approach would look like, but in the meantime, do you think this is a real concern?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants