Bug#680613: libav: Multi-Arch: foreign libraries

[Reinhard Tartler]

On Sat, Jul 7, 2012 at 1:03 PM, Stepan Golosunov <stepan at golosunov.pp.ru> wrote:
> 07.07.2012 в 11:57:47 +0200 Reinhard Tartler написал:
>> On Sat, Jul 7, 2012 at 11:50 AM, Stepan Golosunov
>> <stepan at golosunov.pp.ru> wrote:
>> >
>> > libavutil-extra-51, libavdevice-extra-53, libavfilter-extra-2,
>> > libpostproc-extra-52, libavformat-extra-53 and libswscale-extra-2 are
>> > Multi-Arch: foreign transitional packages.
>> >
>> > This allows the packages to satisfy dependencies of
>> > foreign-architecture packages while providing only libraries for
>> > a native architecture, which is obviously incorrect.
>> >
>> > Transitional library packages should be Multi-Arch: same (but that
>> > would require making them Architecture: any). I guess these packages
>> > should just be removed, as the only non-transitional versions of the
>> > packages still existing in Debian are uninstallable 4:0.7.2.1~bpo60+1
>> > packages in backports and obsolete 4:0.7.2.1+b1 armhf on debports.
>>
>> Well, AFAIUI this is a good reason to defer this for after wheezy
>> release. Is there anything we can do about this issue for wheezy?
>
> What's "this"? Existence of the packages in backports?
> They became uninstallable when libav 0.8 was uploaded to backports
> months ago. (In any case, libav-extra source package probably needs
> be removed from backports.)

Yes, AFAIUI such removals happen on a regular basis without needing to
file a bug.

BTW, libavformat-extra-53 from bpo is perfectly installable for me.
Can you elaborate why they are not for you?

>
> If the transitional packages are to stay, the correct way to proceed
> is either to change them to Multi-Arch: same, Architecture: any or to
> remove their Multi-Arch headers.

Err, they (i.e., all but libavcodec-extra-53, and that's critical) are
already Arch: all, with Multi-arch: foreign. Do I understand you
correctly that they should rather by Multi-arch: same?



-- 
regards,
    Reinhard