DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Luca Boccassi <bluca@debian.org>,
	"Xueming(Steven) Li" <xuemingl@nvidia.com>
Cc: dev@dpdk.org, Aaron Conole <aconole@redhat.com>,
	 Michael Santana <maicolgabriel@hotmail.com>,
	Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [PATCH 1/2] ci: bump tested distributions in GHA
Date: Thu, 22 May 2025 14:51:27 +0200	[thread overview]
Message-ID: <CAJFAV8yAfPZ8XrerzCj1ihGSgBLrsdQNS5D1USCEfOu+jjcEjg@mail.gmail.com> (raw)
In-Reply-To: <20240131174437.2494815-1-david.marchand@redhat.com>

Hello Luca, Xueming,

On Wed, Jan 31, 2024 at 6:44 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> Fedora 37 has reached end of life in December 2023.
> Ubuntu 20.04 is getting quite old.
>
> Switch to more recent versions.
>
> With this move, some packages provided by those distributions are now
> recent enough to extend our build coverage.
> Install additional dependencies like ipsec-mb, isal and other
> libbpf/libxdp devel packages.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>

The Ubuntu 20.04 image has been removed from GHA which means that GHA
testing in github is KO for 22.11 and 23.11 branches.
If you do care about GHA, I suggest backporting this current patch to
those LTS branches (+ fix ef2535d022b9 ("ci: fix ccache for Ubuntu
22.04")).
It should apply cleanly (or at least easily), but I can help otherwise.


-- 
David Marchand


      parent reply	other threads:[~2025-05-22 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 17:44 David Marchand
2024-01-31 17:44 ` [PATCH 2/2] ci: update versions of actions " David Marchand
2024-02-08 14:32   ` Aaron Conole
2024-02-08 14:32 ` [PATCH 1/2] ci: bump tested distributions " Aaron Conole
2024-02-13  9:35   ` David Marchand
2025-05-22 12:51 ` David Marchand [this message]

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=CAJFAV8yAfPZ8XrerzCj1ihGSgBLrsdQNS5D1USCEfOu+jjcEjg@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.com \
    --cc=maicolgabriel@hotmail.com \
    --cc=xuemingl@nvidia.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 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).