Bug#808213: Info received (Bug#808213: libnl3: socket is unusable when portid generation fails)
Le 25/01/2016 09:45, Heiko Stübner a écrit : sorry about dropping the ball here, it somehow got pushed under in january- madness. Looks like I'm through now though, so expect packages today or tomorrow. No problem, thank you for the news. Regards, Nicolas
Bug#808213: Info received (Bug#808213: libnl3: socket is unusable when portid generation fails)
Hi, Am Mittwoch, 20. Januar 2016, 16:58:47 schrieben Sie: > Any news about the update to the libnl 3.2.27? > > It would be nice if the new package would be available for the next ubuntu > release (16.04). sorry about dropping the ball here, it somehow got pushed under in january- madness. Looks like I'm through now though, so expect packages today or tomorrow. Heiko > Le 17/12/2015 14:24, Debian Bug Tracking System a écrit : > > Thank you for the additional information you have supplied regarding > > this Bug report. > > > > This is an automatically generated reply to let you know your message > > has been received. > > > > Your message is being forwarded to the package maintainers and other > > interested parties for their attention; they will reply in due course. > > > > Your message has been sent to the package maintainer(s): > > Heiko Stuebner > > > > If you wish to submit further information on this problem, please > > send it to 808...@bugs.debian.org. > > > > Please do not send mail to ow...@bugs.debian.org unless you wish > > to report a problem with the Bug-tracking system.
Bug#808213: Info received (Bug#808213: libnl3: socket is unusable when portid generation fails)
Any news about the update to the libnl 3.2.27? It would be nice if the new package would be available for the next ubuntu release (16.04). Thank you, Nicolas Le 17/12/2015 14:24, Debian Bug Tracking System a écrit : Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Heiko Stuebner If you wish to submit further information on this problem, please send it to 808...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
Bug#808213: libnl3: socket is unusable when portid generation fails
Hi Heiko, Le 17/12/2015 13:32, Heiko Stübner a écrit : Hi Nicolas, thanks for your report Am Donnerstag, 17. Dezember 2015, 11:30:57 schrieben Sie: Package: libnl-3-200 Version: 3.2.24-2 not sure, but I guess you meant 3.2.26-1, right? Yes (it's the first time I use bugreport ;-)). Severity: important Tags: patch The following upstream patches are missing in libnl 3.2.26 (the unstable version): - f78c3e82398a socket: clear port when unable to generate local port https://github.com/thom311/libnl/commit/f78c3e82398a - 96e1e5bdc2e8 socket: add fallback for nl_connect() by trying to bind to unspecified local port https://github.com/thom311/libnl/commit/96e1e5bdc2e8 - eaa75b7c7d3e socket: fix assertion in nl_connect() when all ports are already in use https://github.com/thom311/libnl/commit/eaa75b7c7d3e These patches are included in libnl 3.2.27. so I guess we should just move to 3.2.27 then ;-) If possible, yes :) Regards, Nicolas
Bug#808213: libnl3: socket is unusable when portid generation fails
Hi Nicolas, thanks for your report Am Donnerstag, 17. Dezember 2015, 11:30:57 schrieben Sie: > Package: libnl-3-200 > Version: 3.2.24-2 not sure, but I guess you meant 3.2.26-1, right? > Severity: important > Tags: patch > > The following upstream patches are missing in libnl 3.2.26 (the unstable > version): > - f78c3e82398a socket: clear port when unable to generate local port > https://github.com/thom311/libnl/commit/f78c3e82398a > - 96e1e5bdc2e8 socket: add fallback for nl_connect() by trying to bind to > unspecified local port https://github.com/thom311/libnl/commit/96e1e5bdc2e8 > - eaa75b7c7d3e socket: fix assertion in nl_connect() when all ports are > already in use https://github.com/thom311/libnl/commit/eaa75b7c7d3e > > These patches are included in libnl 3.2.27. so I guess we should just move to 3.2.27 then ;-) Heiko
Bug#808213: libnl3: socket is unusable when portid generation fails
Package: libnl-3-200 Version: 3.2.24-2 Severity: important Tags: patch The following upstream patches are missing in libnl 3.2.26 (the unstable version): - f78c3e82398a socket: clear port when unable to generate local port https://github.com/thom311/libnl/commit/f78c3e82398a - 96e1e5bdc2e8 socket: add fallback for nl_connect() by trying to bind to unspecified local port https://github.com/thom311/libnl/commit/96e1e5bdc2e8 - eaa75b7c7d3e socket: fix assertion in nl_connect() when all ports are already in use https://github.com/thom311/libnl/commit/eaa75b7c7d3e These patches are included in libnl 3.2.27. They have been backported in ubuntu-14.04: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735 and redhat-7: https://bugzilla.redhat.com/show_bug.cgi?id=1249158 A test tool is provided in the ubuntu and redhat bugs tracker. Ubuntu maintainers ask us to open a debian bug report for this: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/comments/16 Regards, Nicolas -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libnl-3-200 depends on: ii libc6 2.19-18+deb8u1 ii multiarch-support 2.19-18+deb8u1 libnl-3-200 recommends no packages. libnl-3-200 suggests no packages. -- no debconf information
