On 06/06/07, Kam Leo <kam.leo@xxxxxxxxx> wrote:
On 6/6/07, Michael Schwendt <mschwendt@xxxxxxxxx> wrote: > On 06/06/07, Kam Leo <kam.leo@xxxxxxxxx> wrote: > > On 6/6/07, John Lagrue <jlagrue@xxxxxxxxx> wrote: > > > Thanks for the advice Tom, butI'm not sure that this is the same problem > > > > > > Running package-cleanup --problems gives me nothing. There don't > > > appear to be any problems - until I try to apply the new updates. > > > > > > FWIW, the updares are: > > > > > > Updated faad2 packages > > > Updated libdca packages > > > Updated selinux-policy packages > > > Updated vcdimager packages > > > Updated x264 packages > > > > > > > > > JDL > > > > > > [snip] > > > > The packages come from Livna. Bug Livna or wait for the updates to bubble up. > > Not so fast, don't jump to conclusions. Livna's libdca for F7 is as > old as Dec 2006: > http://rpm.livna.org/fedora/7/x86_64/ > > The yum dep failures can also mean that another repository upgrades > libdca to an incompatible version. > That goes with the territory when using 3rd-party repositories. The applications/packages that the OP desires comes from Livna. He can either choose/find another 3rd-party repository that offers those packages or submit a bug report to Livna.
Where do you take your wisdom from? It freshrpms.net I see a libdca package that removes the shared libdts.so.0 offered by Livna and replaces it with static-only libraries. This breaks compatibility, because libdca-0.0.2-4.fc7.x86_64.rpm from freshrpms is seen as an update to libdca-0.0.2-3.lvn7.x86_64.rpm -- any program that requires the shared libdts.so.0 will be broken.
I would recommend patience.
That would be wrong in this case. Action is needed to fix this.
As I recall, Livna encountered hardware problems. They may be a little slow in getting updates out.
Updates for what? Livna's libdca from end of last years provides the needed libraries. Btw, to read up on the h/w problems and what is affected: http://livna.org/mailman/listinfo/freeworld
