Source: kronosnet Version: 1.8-2 Severity: important X-Debbugs-CC: wf...@debian.org
Ben Tullis <ben.tul...@opencorporates.com> 于2019年12月5日周四 上午7:12写道： > There have been some significant fixes implemented between the buster > and bullseye versions of libknet1 > > (Kronosnet is the new corosync communication protocol for HA clustering. > The version in Buster suffers from dropped connections and segfaults > when there is moderate network load.) > > There is an extensive discussion about the issue on the Proxmox forum: > https://forum.proxmox.com/threads/pve-5-4-11-corosync-3-x-major-issues.56124/ > > ...but I'm not aware of any current Debian bugs regarding this issue. > > Would it be appropriate to request a new backport of this version of the > library to buster-backports, or is there some other mechanism by which > it could be made available to stable-updates? I understand that > backports is only supposed to be used for new features, rather than > fixes, so I'm simply enquiring what the best method of getting this > update into buster. I guess uploading onto buster-backports is okay while the best solution is to fix it in Debian Stable. I am converting the previous email on debian-backports mailing list into a bug report so that the original package maintainers are able to be aware of this issue. (They are more familiar with this software and should be contacted first.) Dear kronosnet maintainers: please evaluate this bug and see whether a stable update is possible. Otherwise it's always okay to make a backport. -- Regards, Boyuan Yang
