Bug 228499
| Summary: | net/exabgp upgrade to 4.0.6 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Olivier Cochard <olivier> | ||||||
| Component: | Individual Port(s) | Assignee: | Ryan Steinmetz <zi> | ||||||
| Status: | Closed Overcome By Events | ||||||||
| Severity: | Affects Only Me | CC: | freebsd, pi, sergey, timp87, w.schwarzenfeld | ||||||
| Priority: | --- | Flags: | zi:
maintainer-feedback-
|
||||||
| Version: | Latest | ||||||||
| Hardware: | Any | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
This is still a pre-release/development version. The latest stable/official release is 3.4.25. Do you need features in 4.0.6? Version 4.0.10 released. https://github.com/Exa-Networks/exabgp/releases 4.0.10 is still pre-release. Rejecting until upstream considers it ready to replace the 3.x branch: "This version is most likely the last one before we consider the master branch ready to replace 3.4.x." At https://github.com/Exa-Networks/exabgp/releases I now see 4.1.2 having the badge "Latest release". But does that mean it's a stable release or just the "latest release"? Reading the comment: "The control API / CLI command are however not yet frozen and will slightly change before a stable 4.1.0 release." ...plus the name "ISO-release" (for 4.1.1) sounds to me that it became stable last month. Currently I don't install ExaBGP in production because it requires python 2.7 Created attachment 206480 [details]
patch to upgrade exabgp to 4.1.2
Hi. Do we have any showstoppers to merge it? At a minimum, it looks like there are some issues with the rc script. Looking further now. With the new net/exabgp4 ports, do you confirm we could close this PR? Please see net/exabgp4 |
Created attachment 193707 [details] patch to upgrade exabgp to 4.0.6 Hi, here is a proposal for net/exabgp ugprade: With this upgrade, the package name is python-version dependent (become "py36-exabgp 4.0.6" as example).