Re: Debian packages
"Philip S. Hempel" <[email protected]> Sat, 19 Jul 2008 18:18:05 -0400
| Newsgroups | gmane.comp.video.dvdrip.user |
|---|---|
| Organization | Linux HardCore |
| Message-ID | <[email protected]> |
Philip S. Hempel wrote: > Christian Marillat wrote: >> "Philip S. Hempel" <[email protected]> writes: >> >> >>> Does anybody know when will dvd::rip in unstable at debianmultimedia.org >>> will get in sync with the new libraries? >>> >> >> Which new libraries ? >> >> >>> I understand that this will help fix the problems with the newest >>> versions of transcode that have kept dvd::rip unusable. >>> >> >> dvd::rip works fine for me right now. >> >> Christian >> >> > Because ffmpeg is dependent on libavcodeccvs and friends and not the > new libavcodec51 and friends, > > > storm:~# apt-get install ffmpeg dvdrip > Reading package lists... Done > Building dependency tree > Reading state information... Done > dvdrip is already the newest version. > 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: libavcodec51 (>= 3:20080706) but it is not going to > be installed > Depends: libavdevice52 (>= 3:20080706) but it is not going > to be installed > Depends: libavformat52 (>= 3:20080706) but it is not going > to be installed > Depends: libavutil49 (>= 3:20080706) but it is not going to > be installed > Depends: libswscale0 (>= 3:20080706) but it is not going to > be installed > E: Broken packages > > > I get this on machines that have already had dvdrip installed, for > some odd reason I can install this on a machine that does not have > dvdrip installed now. It has the same problem that mythtv has. > > This is also on amd64 and it looks like this is where the problem is. All of my i386 machines don't seem to have this problem after doing a little more testing.