From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org
Subject: Re: [PATCH] docker: update Ubuntu to 20.04
Date: Fri, 5 Jun 2020 10:32:09 +0200 [thread overview]
Message-ID: <280da8d7-187a-ea53-72db-cb36e5d76b4f@redhat.com> (raw)
In-Reply-To: <20200604231716.11354-1-pbonzini@redhat.com>
On 6/5/20 1:17 AM, Paolo Bonzini wrote:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> tests/docker/dockerfiles/ubuntu.docker | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/docker/dockerfiles/ubuntu.docker b/tests/docker/dockerfiles/ubuntu.docker
> index eeb3b22bf2..43872417de 100644
> --- a/tests/docker/dockerfiles/ubuntu.docker
> +++ b/tests/docker/dockerfiles/ubuntu.docker
> @@ -9,7 +9,7 @@
> # system won't pick up that it has changed.
> #
>
> -FROM ubuntu:19.04
> +FROM ubuntu:20.04
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
I know we want to use recent features, but I'd also keep the oldest
supported image in testing (from our policy, 2 latest).
This one is LTS, so:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Still not sure how to do. Add ubuntu-old.docker based on 19.04 and then
roll 'ubuntu.docker' -> 'ubuntu-old.docker' for each new releases?
> ENV PACKAGES flex bison \
> ccache \
> clang \
>
next prev parent reply other threads:[~2020-06-05 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 23:17 [PATCH] docker: update Ubuntu to 20.04 Paolo Bonzini
2020-06-05 7:41 ` Alex Bennée
2020-06-05 8:32 ` Philippe Mathieu-Daudé [this message]
2020-06-05 9:21 ` Paolo Bonzini
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=280da8d7-187a-ea53-72db-cb36e5d76b4f@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).