All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH v2 1/3] tests: upgrade most non-lcitool debian tests to debian 13
Date: Thu, 26 Feb 2026 17:00:06 +0000	[thread overview]
Message-ID: <87a4wvzbhl.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260225193856.959771-2-jsnow@redhat.com> (John Snow's message of "Wed, 25 Feb 2026 14:38:54 -0500")

John Snow <jsnow@redhat.com> writes:

> Debian 11 was EOL in 2024, and Debian 12 will be EOL this June. This
> patch moves all but one of our tests, debian-legacy-test-cross, onto
> Debian 13.
>
> This patch does the bare minimum to upgrade these tests and doesn't make
> any attempt at optimization or cleanup that may or may not be possible
> with this upgrade.
>
> Signed-off-by: John Snow <jsnow@redhat.com>

Queued to testing/next, thanks.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  parent reply	other threads:[~2026-02-26 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 19:38 [PATCH v2 0/3] tests: upgrade containers to debian 13 John Snow
2026-02-25 19:38 ` [PATCH v2 1/3] tests: upgrade most non-lcitool debian tests " John Snow
2026-02-26 14:47   ` Daniel P. Berrangé
2026-02-26 17:00   ` Alex Bennée [this message]
2026-02-25 19:38 ` [PATCH v2 2/3] tests: upgrade debian-legacy-test-cross " John Snow
2026-02-25 22:57   ` Alex Bennée
2026-02-26 16:23     ` John Snow
2026-02-26 14:47   ` Daniel P. Berrangé
2026-02-25 19:38 ` [PATCH v2 3/3] python: upgrade minimum setuptools/wheel/pip versions John Snow
2026-02-26  7:59   ` Thomas Huth
2026-02-26 14:45   ` Daniel P. Berrangé

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=87a4wvzbhl.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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 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.