Bug#788716: listening_ip option causing parsing error

Hi Michael, This is a duplicate of (fixed) bug #756169, upstream dropped those options. Maybe the existing bug for the -i flag is a better place to discuss the security implications and/or state of that feature. (Maybe it works as designed, but connections on the "lo" interface are always accepte

Bug#747813: Fixed upstream: FTBFS against libav10

tags 747813 fixed-upstream thanks Hi Benoit, minidlna 1.1.3 claims support for libav10, so the patch is no longer needed. Upgrading to the latest upstream release should fix this. Cheers, Florian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscrib

Bug#747813: minidlna: FTBFS against libav10

17 00:00:00 2001 From: Florian Will Date: Thu, 15 May 2014 11:18:57 +0200 Subject: [PATCH] Fix FTBFS with libav10 Two upstream commits squashed into one: 361bc3: metadata: add libavcodec > 54 compatibility 05cde8: metadata: more libav10 compatibility changes --- libav.h

Bug#747813: [PATCH] Fix FTBFS with libav10

This is only tested to compile using libav10 from sid. While it fixes the FTFBS for me, I haven't tested to see if it breaks any functionality. --- metadata.c | 44 ++-- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/metadata.c b/metadata.c

Bug#674728: #674728 chromium: FTBFS on armel and armhf

Hi, about the "undefined reference to `vpx_codec_destroy'" and similar vpx* linker errors on armel and armhf: The builds have "use_system_vpx=1" defined for gyp. However, upstream probably dropped support for that flag, or never supported it -- there's no appearance of that "use_system_vpx" strin