On Wed, May 28, 2014 at 8:28 AM, Reinhard Tartler wrote:
> That is correct, and I'm not arguing with that. It makes only sense
> for packages that only execute avconv, and do link against directly
> against libavcodec. This was the case for #748546.
Sorry, that meant to be read as ... and do NOT
On Mon, May 26, 2014 at 2:04 PM, Jakub Wilk wrote:
> Thanks for the bug report.
>
> * Reinhard Tartler , 2014-05-18, 13:43:
>>
>> The libav package provides two flavors of libavcodec: libavcodecNN and
>> libavcodec-extra-NN, with NN being the current soname (the current
>> transition changes NN fr
Thanks for the bug report.
* Reinhard Tartler , 2014-05-18, 13:43:
The libav package provides two flavors of libavcodec: libavcodecNN and
libavcodec-extra-NN, with NN being the current soname (the current
transition changes NN from -54 -> 55).
It is not a good idea for packages to depend on l
Package: lintian
Hi,
The libav package provides two flavors of libavcodec: libavcodecNN
and libavcodec-extra-NN, with NN being the current soname (the current
transition changes NN from -54 -> 55).
It is not a good idea for packages to depend on libavcodec-extra-NN in
any case. Instead, packages
4 matches
Mail list logo