[SCM] KTorrent library Debian packaging branch, master, updated. debian/1.0.0-1

[Modestas Vainius]

The following commit has been merged in the master branch:
commit da22aecc9a133729664d88981e5fd7ddfae6c5a5
Author: Modestas Vainius <modestas at vainius.eu>
Date:   Fri May 28 21:03:16 2010 +0300

    Debian kFreeBSD supports IPv4-mapped addresses, just does not default to them.
---
 debian/changelog                             |    5 +++--
 debian/patches/debian_disable_ipv6_only.diff |    9 ++++-----
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 3557705..a359598 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,9 @@
 libktorrent (1.0.0-0r1) UNRELEASED; urgency=low
 
   * New upstream release.
-  * Add a workaround for #581896 on Linux (patch
-    debian_disable_ipv6_only.diff). The bug remains open on kFreeBSD.
+  * Explicitly disable IPV6_V6ONLY for tcp/udp server sockets
+    (Closes: #581896). The proper solution (2 sockets) will be in the next
+    major upstream release.
   * License files are in upstream tarball now, remove the respective note from
     debian/copyright.
   * Add debian/README.source.
diff --git a/debian/patches/debian_disable_ipv6_only.diff b/debian/patches/debian_disable_ipv6_only.diff
index 3132697..75d3d22 100644
--- a/debian/patches/debian_disable_ipv6_only.diff
+++ b/debian/patches/debian_disable_ipv6_only.diff
@@ -8,11 +8,10 @@ Description: Always bind IPv6 sockets to IPv4 as well
  .
  Unfortunately, this fix is just a workaround and my attempt at damage control.
  According to [1], not all IPv6 stacks support IPv4-mapped addresses (Windows,
- OpenBSD, Debian kFreeBSD do not support them). What is more, as far as I can
- tell, net.ipv6.bindv6only=1 like behaviour is default on *BSD. So KTorrent
- without IPV6_V6ONLY explicitly set to 0 used to bind to IPv6-only addresses on
- these systems. Only Linux and OSX default to net.ipv6.bindv6only=0 like
- behaviour.
+ OpenBSD do not support them). What is more, as far as I can tell,
+ net.ipv6.bindv6only=1 like behaviour is default on *BSD. So KTorrent without
+ IPV6_V6ONLY explicitly set to 0 used to bind to IPv6-only addresses on these
+ systems. Only Linux and OSX default to net.ipv6.bindv6only=0 like behaviour.
  .
  The proper fix would be to open two sockets: one AF_INET6 with IPV6_V6ONLY and
  another AF_INET one. I recommend you to read the thread [2] about bindv6only=1

-- 
KTorrent library Debian packaging