Control: tags -1 moreinfo

Hi,

On 20/07/18 23:14, Dirk Lehmann wrote:
> Package: libavcodec-extra57
> Version: 7:3.4.3-1
> Severity: normal
> Tags: d-i
> 
> Dear Maintainer,
> 
> I try to install a backport package which is depending on package
> 'libavcodec57'.  But I have installed the package libavcodec-extra57
> on my machine.  If I try to install it, I get the following error:
> 
> ----------------------------------------------------------------------
> root$> apt-get install jitsi
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> 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:
>  jitsi : Depends: libavcodec57 but it is not going to be installed or
>                   libavcodec-ffmpeg56 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> ----------------------------------------------------------------------

Where is this package from? There is no "jitsi" in Debian (anymore) so
it must be unofficial. When packages are built against ffmpeg they
should get a dependency like this which should work with libavcodec-extra:
 libavcodec57 (>= 7:3.4.3) | libavcodec-extra57 (>= 7:3.4.3)

Probably the jitsi packages itself is at fault, or something else is
preventing the installation.

> I'm not really familiar with DPKG, but I think it could be solved if
> the manifest of dpkg-archive from 'libavcodec-extra57' includes a
> 
> ----------------------------------------------------------------------
> [...]
> Provides: libavcodec57
> [...]
> ----------------------------------------------------------------------

Unfortunately this won't work because it won't satisfy versioned
dependencies. If versioned provides was working properly everywhere then
possibly it could be used, but I don't think it does yet (although I'm
happy to be corrected!).

James

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to