From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>
Subject: [PATCH] ci: switch to Fedora 37
Date: Fri, 21 Apr 2023 16:34:47 +0200 [thread overview]
Message-ID: <20230421143447.3618180-1-david.marchand@redhat.com> (raw)
Fedora 35 has been declared EOL in 2022/12 (see [1]).
Fedora 36 will soon be EOL too.
Move to Fedora 37.
Fedora 37 libbpf does not support AF_XDP anymore, now provided by
libxdp.
1: https://docs.fedoraproject.org/en-US/releases/eol/
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
.github/workflows/build.yml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index edd39cbd62..7322eb59b7 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -149,7 +149,7 @@ jobs:
fail-fast: false
matrix:
config:
- - image: fedora:35
+ - image: fedora:37
steps:
- name: Generate various keys
@@ -198,9 +198,9 @@ jobs:
fail-fast: false
matrix:
config:
- - image: fedora:35
+ - image: fedora:37
compiler: gcc
- - image: fedora:35
+ - image: fedora:37
compiler: clang
steps:
@@ -250,7 +250,7 @@ jobs:
run: docker exec -i dpdk dnf update -y || true
- name: Install packages
run: docker exec -i dpdk dnf install -y ccache jansson-devel
- libarchive-devel libatomic libbsd-devel libbpf-devel libfdt-devel
+ libarchive-devel libatomic libbsd-devel libxdp-devel libfdt-devel
libpcap-devel ninja-build numactl-devel openssl-devel python3-pip
python3-pyelftools python3-setuptools python3-wheel rdma-core-devel
zlib-devel
--
2.40.0
next reply other threads:[~2023-04-21 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:34 David Marchand [this message]
2023-04-21 21:06 ` Aaron Conole
2023-04-25 13:13 ` David Marchand
2023-04-25 23:20 ` Stephen Hemminger
2023-04-26 5:45 ` David Marchand
2023-05-23 9:49 ` Thomas Monjalon
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=20230421143447.3618180-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.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).