public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] bird: Update to version 2.14
Date: Thu, 18 Jan 2024 12:40:18 +0100	[thread overview]
Message-ID: <20240118114031.6171-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3896 bytes --]

- Update from version 2.0.12 to 2.14
- Update of rootfile not required
- Changelog
    2.14 (2023-10-06)
	  o MPLS subsystem
	  o L3VPN: BGP/MPLS VPNs (RFC 4364)
	  o BGP: Access to unknown route attributes
	  o RAdv: Custom options
	  o Babel: RTT metric extension
	  o BMP: Refactored route monitoring
	  o BMP: Multiple instances of BMP protocol
	  o BMP: Both pre-policy and post-policy monitoring
	  o Experimental route aggregation
	  o Filter: Method framework
	  o Filter: Functions have return type statements
	  o Filter: New bytestring data type
	  o Kernel: Option to learn kernel routes
	  o Many bugfixes and improvements
	Notes:
	  User-defined filter functions that return values now should have return type
	   statements. We still accept functions without such statement, if they could be
	   properly typed.
	  For loops allowed to use both existing iterator variables or ones defined in
	   the for statement. We no longer support the first case, all iterator variables
	   must be defined in the for statement (e.g. 'for int i in bgp_path ...').
	  Due to oversight, VRF interfaces were not included in respective VRFs, this is
	   fixed now.
    2.13.1 (2023-06-23)
	  o BGP: Fix role check when no capability option is present
	  o Filter: Fixed segfault when a case option had an empty block
	  This is a bugfix version.
    2.13 (2023-04-21)
	  o Babel: IPv4 via IPv6 extension (RFC 9229)
	  o Babel: Improve authentication on lossy networks
	  o BGP: New 'allow bgp_med' option
	  o BSD: Support for IPv4 routes with IPv6 nexthop on FreeBSD
	  o Experimental BMP protocol implementation
	  o Important bugfixes
	Notes:
	  We changed versioning scheme from <epoch>.<major>.<minor> to more common
	   <major>.<minor>.<patch> . From now on, you may expect that BIRD 2.13.x will be
	   strictly only fixing bugs found in 2.13, whereas BIRD 2.14 will also contain
	   new features.
	  This BIRD version contains an alpha release of BMP protocol implementation.
	   It is not ready for production usage and therefore it is not compiled by
	   default and have to be enabled during installation.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/bird | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/lfs/bird b/lfs/bird
index 0c8c97055..e9dc6c5f8 100644
--- a/lfs/bird
+++ b/lfs/bird
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2023  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2024  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = The BIRD Internet Routing Daemon
 
-VER        = 2.0.12
+VER        = 2.14
 
 THISAPP    = bird-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = bird
-PAK_VER    = 12
+PAK_VER    = 13
 
 DEPS       =
 
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = ca00574bb8e508255afb90e0d65f4e1763880699cff9877731d072efc48944b9f9ac77b35bb7ffd7b780e8e8b1c2eacdc38ee273353817c53723e7972fb5f0d6
+$(DL_FILE)_BLAKE2 = fe16b89c7f0ff35c5126366920960e0c55f57fe343380b2c32230122cf24f9abc3eb4d6ed9f37d2176f9e9340a83dffd1e68fed276b59b86cf1bdf5b8bd3c169
 
 install : $(TARGET)
 
-- 
2.43.0


             reply	other threads:[~2024-01-18 11:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 11:40 Adolf Belka [this message]
2024-01-18 11:40 ` [PATCH] dmidecode: Update to version 3.5 Adolf Belka
2024-01-18 11:40 ` [PATCH] fmt: Update to version 10.2.1 Adolf Belka
2024-01-18 11:40 ` [PATCH] haproxy: Update to version 2.9.2 Adolf Belka
2024-01-18 11:40 ` [PATCH] ipset: Update to version 7.19 Adolf Belka
2024-01-18 11:40 ` [PATCH] libtalloc: Update to version 2.4.1 Adolf Belka
2024-01-18 11:40 ` [PATCH] libvirt: Update to version 10.0.0 Adolf Belka
2024-01-18 11:40 ` [PATCH] lshw: Update to version B.02.20 Adolf Belka
2024-01-18 11:40 ` [PATCH] memtest: Update to version 7.00 Adolf Belka
2024-01-18 11:40 ` [PATCH] pixman: Update to version 43.0 Adolf Belka
2024-01-18 11:40 ` [PATCH] poppler: Update to version 24.01.0 Adolf Belka
2024-01-18 11:40 ` [PATCH] stunnel: Update to version 5.71 Adolf Belka
2024-01-18 11:40 ` [PATCH] transmission: Update to version 4.0.5 Adolf Belka
2024-01-18 11:40 ` [PATCH] wavemon: Update to version 0.9.5 Adolf Belka

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=20240118114031.6171-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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