November 2019 - dev - lists.frrouting.org

Re: [dev] Bug#944392: frr: /usr/share/man/man8/vrrpd.8.gz is already shipped by vrrpd
by David Lamparter 09 Nov '19

09 Nov '19

On Sat, Nov 09, 2019 at 03:33:05AM +0100, Andreas Beckmann wrote: > Package: frr > Version: 7.2-1 > Severity: serious > > during a test with piuparts I noticed your package failed to install > because it tries to overwrite other packages files. [...] > dpkg: error processing archive /tmp/apt-dpkg-install-3pfMjQ/16-frr_7.2-1_amd64.deb (--unpack): > trying to overwrite '/usr/share/man/man8/vrrpd.8.gz', which is also in package vrrpd 1.0-2+b2 Hi Andreas, Thanks for catching this. vrrpd is one of FRR's "protocol" daemons, installed to /usr/lib/frr/ (hence the binary isn't colliding), but obviously the manpage doesn't have this private directory. I need to go dig through the Debian policy on what it says about this. I'm guessing we should just rename our manpages to "frr-<daemon>". The binary isn't in PATH either, i.e. you can't run FRR vrrpd by just typing "vrrpd", so not getting the manpage with "man vrrpd" is consistent. (It does make sense for vrrpd to be installed in parallel with FRR, in particular since VRRP support is a recent FRR addition and existing setups may very well want to stick with a vrrpd+FRR configuration.) (Cc'ing onto FRR dev list for further comment. Please keep the debian bugtracker address in Cc:. Also opening an issue on FRR github.) Cheers, -David

1 0

Request for a BGP-LS development branch
by olivier.dugeon＠orange.com 08 Nov '19

08 Nov '19

Dear all, I got request from FRR developers to share our respective work on BGP Link State (BGP-LS a.k.a RFC7752) This new functionality has been identify in the feature request list (see https://github.com/FRRouting/frr/wiki/Feature-Requests) following issue 3520 (see https://github.com/FRRouting/frr/issues/3520) The development branch is necessary as: - No one have a complete solution and we would build a global solution without redeveloping everything from scratch: we have parser & serializer, others have integration in latest FRR version ... - This is a complex feature which re-use BGP as transport protocol, but which is completely new in FRR and need large amount of work - BGP-LS needs to collect Link State information from OSPF or IS-IS. For that purpose, new Traffic Engineering Database will be introduce in lib directory. This TED will be fulfil by OSPF or IS-IS and modification sent to BGP through new ZAPI message. This method will avoid to code an OSPF parser and an IS-IS parser inside BGP-LS code and reduce the amount of data that transit through zebra layer. Please inform me once the branch created. Regards Olivier _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

3 3

Request for a Development Branch for ISIS Segment Routing
by olivier.dugeon＠orange.com 01 Nov '19

01 Nov '19

Dear all, Following decision taken during the meeting of 29th of October 2019, I would request the creation of a development branch for IS-IS Segment Routing. This new functionality has been identify in the feature request list (see https://github.com/FRRouting/frr/wiki/Feature-Requests) following issue 2639 (see https://github.com/FRRouting/frr/issues/2639) The development branch is necessary in order to converge both development that have been submitted recently (see https://github.com/FRRouting/frr/pull/4945 and https://github.com/FRRouting/frr/pull/4800) Please inform me once the branch created. Regards Olivier _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

3 3

TSC Voting Results.
by Alistair Woodman 01 Nov '19

01 Nov '19

All 17 maintainers have finished voting in the TSC Election for the 2019-2020 session. By the single transferable vote algorithm, the following candidates are elected to the TSC. (in alphabetical, not ranked order) . Lou Berger . Donald Sharp . Sri Mohana Singamsetty . Russ White . Martin Winter . Quentin Young Your elections officer /a

1 0