Package: libupnp6 Version: 1:1.6.19.jfd1-1 Severity: normal Tags: ipv6 Dear Maintainer,
Newer versions of libupnp6 in Squeeze and later are configured with --enable- ipv6 The device part of such a library (miniserver) will not start if the running kernel does not contain ipv6 code. This is not the case for standard Debian kernel, but it happens with some derivative distributions, e.g. at least Raspbian. Raspberry Pis make nice multimedia devices, so Raspbian is an important platform for UPnP-related packages. I have no way to know if a future Raspbian based on Squeeze would still have ipv6-less default kernels, but if this proves to be the case, this problem becomes a major issue. It would of course possibly also affect people running Debian with custom ipv6-less kernels. A patch has been submitted to upstream to let the library start up in ipv4-only mode in this situation. http://sourceforge.net/p/pupnp/patches/60/ Two possible approaches to fix the problem would be to either reverse the --enable-ipv6 change (previous versions were built without it), or apply the correction. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.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/dash Versions of packages libupnp6 depends on: ii libc6 2.13-38+deb7u8 ii multiarch-support 2.13-38+deb7u8 libupnp6 recommends no packages. libupnp6 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
