Bug#680602: libav-dbg: bogusly Depends: libavcodec53 (= ${binary:Version})

[Reinhard Tartler]

On Sat, Jul 7, 2012 at 10:51 AM, Stepan Golosunov
<stepan at golosunov.pp.ru> wrote:
> Package: libav-dbg
> Version: 6:0.8.3-4
> Severity: important
>
> libav-dbg is not installable together with libavcodec-extra-53 due to
> bogus dependency on libavcodec53 (introduced in 6:0.8.3-2):

AFAIUI this was deliberate because libav-dbg ships symbols for
libavcodec53, which is not co-installable with libavcodec-extra-53.
>
> # apt-get install libav-dbg libavcodec-extra-53
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> libavcodec-extra-53 is already the newest version.
> libavcodec-extra-53 set to manually installed.
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  libav-dbg : Depends: libavcodec53 (= 6:0.8.3-4) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
>
>
> As libav-dbg does not provide debug data for libavcodec53, it should at
> most depend on
>  libav-regular-dbg (= ${binary:Version}) | libav-extra-dbg (= ${binary:Version})
> instead of
>  libavcodec53 (= ${binary:Version})
>
> By the way, is there any need for separate libav-regular-dbg and
> libav-extra-dbg to exist at all? Given that the packages use build IDs
> now, all their contents could be placed into libav-dbg.

I guess this is the right solution, just scratch libav-extra-dbg and
package both regular and -extra- package flavors into the same
libav-dbg.

Andres, since you have implemented libav-extra-dbg, can you have a look at this?

-- 
regards,
    Reinhard