From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied: [PATCH frr] Fix #4810: bump to 8.5.2-1+pve1
Date: Wed, 30 Aug 2023 17:11:47 +0200 [thread overview]
Message-ID: <e8d4ebc2-5ff9-4a09-8279-9168b7914d8e@proxmox.com> (raw)
In-Reply-To: <20230823142613.3948275-1-aderumier@odiso.com>
Am 23/08/2023 um 16:26 schrieb Alexandre Derumier:
> frr 8.5.1 a critical bug evpn bug with Type-3 EVPN route
>
> This is fixed with
> https://github.com/FRRouting/frr/pull/14094
>
> Not yet applied in 8.5.2, but already in stable/8.5 branch.
>
> This patch serie update frr to stable/8.5 on commit 3d1b6c0e604ef96ee9a4601b31b6561258fd80f0
> (Please update frr mirror to this commit)
FYI, you can update the submodule to that commit and then add that as change
in git, then the change from old to new commit ID will be sent along with the
patch and one avoids
>
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> debian/changelog | 6 ++
> .../0001-zebra-fix-evpn-dup-detected.patch | 46 ------------
> .../0002-zebra-evpn-handle-del-event.patch | 71 -------------------
> debian/patches/series | 2 -
> 4 files changed, 6 insertions(+), 119 deletions(-)
> delete mode 100644 debian/patches/frr/0001-zebra-fix-evpn-dup-detected.patch
> delete mode 100644 debian/patches/frr/0002-zebra-evpn-handle-del-event.patch
>
>
applied, and bumped to current stable/8.5, which now also contain a fix for:
https://blog.benjojo.co.uk/post/bgp-path-attributes-grave-error-handling
thanks!
next prev parent reply other threads:[~2023-08-30 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:26 [pve-devel] " Alexandre Derumier
2023-08-30 15:11 ` Thomas Lamprecht [this message]
2023-08-30 15:46 ` [pve-devel] applied: " DERUMIER, Alexandre
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=e8d4ebc2-5ff9-4a09-8279-9168b7914d8e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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