Bug#922618: Any plan to package bird 2.0 as a separate package?
Hello Ondřej, Thank you for your quick response! I'm sorry that I only searched on packages.debian.org but forget to search through any staging area, so I missed your recent great efforts. Would you please help me close this issue? I am not familiar with this bug tracker. On Mon, Feb 18, 2019 at 10:19 PM Ondřej Surý wrote: > > https://salsa.debian.org/debian/bird2/ > > > On 18 Feb 2019, at 14:31, StarBrilliant wrote: > > > > Package: bird > > Version: 1.6.5-1 > > Severity: wishlist > > > > Hello Debian packager! > > > > It has been a year since the release of bird 2.0, which has better > > dual-stack integration, better RPKI support, better MPLS support, etc. > > > > However the new version is incompatible to the old branch, similar to > > the situation between Qt4 and Qt5. Do you have any plan to package > > bird 2.0 as a separate package (e.g. bird2)? > > > > > > Best regards, > > StarBrilliant >
Bug#922618: Any plan to package bird 2.0 as a separate package?
Package: bird Version: 1.6.5-1 Severity: wishlist Hello Debian packager! It has been a year since the release of bird 2.0, which has better dual-stack integration, better RPKI support, better MPLS support, etc. However the new version is incompatible to the old branch, similar to the situation between Qt4 and Qt5. Do you have any plan to package bird 2.0 as a separate package (e.g. bird2)? Best regards, StarBrilliant
Bug#814927: [Pkg-swan-devel] Bug#814927: strongSwan misses ChaCha/POLY support
On Tue, 16 Feb 2016 17:15:46 +0100, Alessandro Guido wrote: > > strongSwan supports the ChaCha20/Poly1305 algorithm since version 5.3.3. > Such algo is supposedly faster than AES on machines w/o hardware > acceleration. > I suggest to include --enable-chapoly [1] when running the configure script. I just checked the sid and experimental repo, still not fixed. This patch has been submitted for over 2 years, and is actually working. I recommend merging the patch now. Benefit for the fix: strongSwan has a certain problem that does not warn you if you configure ChaCha20Poly1305 with this plugin missing, but stops working with weird errors if any client tries to negotiate this cipher, making system administrators puzzled troubleshooting this problem. By merging the patch can we solve the problem. Best regards, StarBrilliant
