From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH frr 0/2] update frr to 8.0.1
Date: Fri, 5 Nov 2021 09:16:50 +0100 [thread overview]
Message-ID: <20211105081652.3191827-1-aderumier@odiso.com> (raw)
This patch series update frr to 8.0.1.
I'm running it in production since 1month, no bug detected, evpn works fine (with some fixes for ip mobility).
This need to bump the proxmox frr mirror to 8.0.1 tag.
Also, this need the libyang2, not available in debian repo.
Deb are available in frr repos:
https://deb.frrouting.org/frr/pool/frr-8/liby/libyang2/libyang2_2.0.7-1~deb11u1_amd64.deb
https://deb.frrouting.org/frr/pool/frr-8/liby/libyang2/libyang2-dev_2.0.7-1~deb11u1_amd64.deb
Alexandre Derumier (2):
update patches
bump to 8.0.1
Makefile | 4 +-
debian/changelog | 6 ++
debian/control | 56 +++++++++---------
...e-ax_python.m4-to-hardcode-python3.9.patch | 25 --------
.../patches/pve/0001-enable-bgp-daemon.patch | 8 +--
...on-for-RT-auto-derivation-to-force-A.patch | 59 ++++++++++---------
debian/patches/series | 1 -
7 files changed, 70 insertions(+), 89 deletions(-)
delete mode 100644 debian/patches/0001-Adjust-the-ax_python.m4-to-hardcode-python3.9.patch
--
2.30.2
next reply other threads:[~2021-11-05 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 8:16 Alexandre Derumier [this message]
2021-11-05 8:16 ` [pve-devel] [PATCH frr 1/2] update patches Alexandre Derumier
2021-11-05 8:16 ` [pve-devel] [PATCH frr 2/2] bump to 8.0.1 Alexandre Derumier
2021-11-09 18:03 ` [pve-devel] [PATCH frr 0/2] update frr " Thomas Lamprecht
2021-11-10 6:36 ` [pve-devel] applied-series: " Thomas Lamprecht
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=20211105081652.3191827-1-aderumier@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.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