On Sun, Apr 29, 2012 at 2:38 PM, Sven Joachim svenj...@gmx.de wrote:
Package: libavcodec53
Version: 6:0.8.1-5
Severity: grave
Your package is not installable, because it depends on both
libavutil51 (= 6:0.8.1-5) and libavutil51 ( 5:0.8.1-99) which cannot
possibly be both fulfilled.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.4.0-rc4-nouveau+ (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Offtopic here but,
I want to make sure we do not have anymore bugs like this in the next
release of Debian after wheezy. I am for having only one libavcodec
library that is GPLv3+ enabled.
I don't have specific stats but I imagine packages that cannot go with
a GPLv3+ enabled libav are few and are simply other (L)GPL packages.
In such a case, these packages should just be relicensed (LGPLv2.1+ or
GPLv2+ should be fine). A more extreme measure is that these packages
are simply dropped, but if that what it takes to stop this kind of
bug, I rather have the packages dropped.
--
~ Andres
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
