Your message dated Wed, 6 Mar 2013 09:48:00 +0100 with message-id <[email protected]> and subject line Re: Bug#702377: gstreamer1.0-libav 1.0.5-2 has a hard Depends on libavcodec-extra-54 has caused the Debian Bug report #702377, regarding gstreamer1.0-libav 1.0.5-2 has a hard Depends on libavcodec-extra-54 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 702377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702377 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gstreamer1.0-libav Version: 1.0.5-2 Severity: normal Hi, I wonder why gstreamer1.0-libav 1.0.5-2 has a hard Depends on libavcodec- extra-54. This means that the regular libavcodec54 package gets pushed out of the system. Is this intended? - Fabian -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (901, 'testing'), (501, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (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 Versions of packages gstreamer1.0-libav depends on: ii libavcodec-extra-54 6:9.3-1 ii libavformat54 6:9.3-1 ii libavutil52 6:9.3-1 ii libc6 2.17-0experimental2 ii libglib2.0-0 2.35.8-1 ii libgstreamer-plugins-base1.0-0 1.0.5-1 ii libgstreamer1.0-0 1.0.5-1 ii liborc-0.4-0 1:0.4.16-2 ii libswscale2 6:9.3-1 gstreamer1.0-libav recommends no packages. gstreamer1.0-libav suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---> That's indeed a good question, why does it? :) It only has > ${shlibs:Depends} and ${misc:Depends} for the binary package, so has to > get it from somewhere else. I think it's libav's fault. I just tried to reproduce this issue on my local system with a recent libavcodec-dev package and the Dependencies were right, i.e. gstreamer1.0-libav got the alternative dependencies as expected. The version of libavcodec-dev that gstreamer1.0-libav_1.0.5-2 was built against is 6:9~beta3-1. In the libav changelog I find the following entry for a later upload: libav (6:9.1-2) experimental; urgency=low [...] * Fix internal shlibs This and the corresponding changes in GIT, I believe, pretty much explain the issue. Maybe xou could raise the Build-Depends for libavcodec-dev to (>= 6:9.1-2~)? - Fabian
--- End Message ---
