BIRD 2.0.6 and 1.6.8
Dear BIRD users, we just released two new versions - 1.6.8 and 2.0.6. Version 1.6.8 just includes important bugfixes. Version 2.0.6 o RAdv: Solicited unicast RAs o BGP: Optional Adj-RIB-Out o BGP: Extended optional parameters length o Filter: Sets and set expressions in path masks o Several important bugfixes Cheers! Ondrej
On Wed, 11 Sep 2019, Ondrej Filip wrote:
we just released two new versions - 1.6.8 and 2.0.6.
Users consuming BIRD RPM packages from Fedora or EPEL (for RHEL/CentOS) repositories can get updated packages likely tomorrow or so - once they reached a mirror near to you. Alternatively the builds are available at the buildsystem via https://bodhi.fedoraproject.org/updates/?like=bird Who ever maintains ftp://bird.network.cz/pub/bird/fedora/: it could be a good idea for the admins to fix the permissions (missing read access for 1.6.7 and 2.0.5) in order to make the repository usable...just in case somebody uses that repository. Regards, Robert
On 12. 09. 19 0:09, Robert Scheck wrote:
On Wed, 11 Sep 2019, Ondrej Filip wrote:
we just released two new versions - 1.6.8 and 2.0.6.
Who ever maintains ftp://bird.network.cz/pub/bird/fedora/: it could be a good idea for the admins to fix the permissions (missing read access for 1.6.7 and 2.0.5) in order to make the repository usable...just in case somebody uses that repository.
Thank you for pointing this out. Fixed. Ondrej
Regards, Robert
On Thu, Sep 12, 2019 at 09:41:20AM +0200, Clemens Schrimpe wrote:
What would it take to get this
Version 2.0.6 o RAdv: Solicited unicast RAs
"backported" to 1.6.x ?
Hi Well, we do not plan to backport new features to 1.6.x, only bugfixes. Any reason why this feature should be an exception and why not just migrate to 2.0.x? OTOH, it seems simple to backport, it applies cleanly and probably all what is necessary is to change current_time() wit 'now'. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Well, we do not plan to backport new features to 1.6.x, only bugfixes.
Any reason why this feature should be an exception and why not just migrate to 2.0.x?
Quite some work, $people afraid of change and too lazy to test ... the usual. But technically: No, not really. You are right that we should!
OTOH, it seems simple to backport, it applies cleanly and probably all what is necessary is to change current_time() wit 'now'.
Well ... ;-) Thanks, Clemens
participants (4)
-
Clemens Schrimpe -
Ondrej Filip -
Ondrej Zajicek -
Robert Scheck