libavcodec-extra-52 broken dependencies, fails to install

[Paul Sladen]

Binary package hint: xvidcap

"sudo apt-get install xvidcap" gives:

    xvidcap: Depends: libavcodec-extra-52 but it is not going to be installed

"sudo apt-get install libavcodec-extra-52" gives:

    libavcodec-extra-52: Depends: libavutil-extra-49 (>= 4:0.5+svn20090706) but it is not going to be installed
                         Depends: libavutil-extra-49 (< 4:0.5+svn20090706-99) but it is not going to be installed
                         Depends: libdirac0c2a but it is not going to be installed
                         Depends: libopenjpeg2 but it is not going to be installed
                         Conflicts: libavcodec52 but 4:0.5+svn20090706-2ubuntu1 is to be installed

dpkg -l | grep libavcodec:

  ii libavcodec52 4:0.5+svn20090706-2ubuntu1

[Reinhard Tartler (siretart)]

Paul Sladen <email address hidden> writes:

> Public bug reported:
>
> Binary package hint: xvidcap
>
> "sudo apt-get install xvidcap" gives:
>
> xvidcap: Depends: libavcodec-extra-52 but it is not going to be
> installed

On my up-to-date karmic system this works just fine with both
libavcodec-extra-52 and libavcodec52. Can you please be more specific
about your system?

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

[Martin Beltov (mbeltov)]

I get the same result in karmic 9.10

martin@Athens:~$ sudo apt-get install ffmpeg
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:
  ffmpeg: Depends: libavcodec52 (< 4:0.5+svn20090706-99) but it is not going to be installed or
                   libavcodec-extra-52 (< 4:0.5+svn20090706-99) but 4:0.5+svn20090926-0ubuntu3~tj~ppa1k is to be installed
          Depends: libavdevice52 (< 4:0.5+svn20090706-99) but it is not going to be installed or
                   libavdevice-extra-52 (< 4:0.5+svn20090706-99) but 4:0.5+svn20090926-0ubuntu3~tj~ppa1k is to be installed
          Depends: libavfilter0 (< 4:0.5+svn20090706-99) but it is not going to be installed or
                   libavfilter-extra-0 (< 4:0.5+svn20090706-99) but 4:0.5+svn20090926-0ubuntu3~tj~ppa1k is to be installed
          Depends: libavformat52 (< 4:0.5+svn20090706-99) but it is not going to be installed or
                   libavformat-extra-52 (< 4:0.5+svn20090706-99) but 4:0.5+svn20090926-0ubuntu3~tj~ppa1k is to be installed
          Depends: libswscale0 (< 4:0.5+svn20090706-99) but it is not going to be installed or
                   libswscale-extra-0 (< 4:0.5+svn20090706-99) but 4:0.5+svn20090926-0ubuntu3~tj~ppa1k is to be installed

[Lionel Le Folgoc (mrpouit)]

> but 4:0.5+svn20090926-0ubuntu3~tj~ppa1k is to be installed

This version doesn't seem to be available in the archive, rather in a PPA. Please disable it and retry.

[Martin Beltov (mbeltov)]

I disabled the ppa, but I get the same result .

[Maddmaxx (maddmaxx666)]

Likewise, after upgrading to the 9.10 beta, now I cannot play audio or video due to these broken dependencies, they cannot be repaired via the standard procedures. I have disabled the PPA's, tried fixing broken dependencies in Synaptic, and by command line... WOW... Guess that's what you get for using betas...

[Maddmaxx (maddmaxx666)]

I apologize for the double post, but I'm on to something... Open Synaptic and install libavcodec52, let it uninstall what it wants to, pay attention to what it uninstalled, and reinstall those packages after it finishes. Now on to my unrelated audio issue...

[Reinhard Tartler (siretart)]

this is not a general support forum, and we cannot support 3rd party packages.

To me, this looks like a transient problem that has been fixed in the mean time. Paul, do you agree?

[Reinhard Tartler (siretart)]

no answer since months, I conclude this was a transient issue that has been fixed in the mean time.