Hi, why doesn't piave compile with libdv versions > 0.102 ? Every time I run emerge -uD world, libdv gets upgraded, and in the next run downgraded becaause of piave. What to do? Johnny
On my system libdv up/downgrades between 0.102 and 0.104, too, but under other circumstances (shortened Output of ecatmurs unofficial dep script): media-libs/libdv-0.102: media-video/transcode-0.6.11 <=media-libs/libdv-0.102 media-libs/libdv-0.104: media-libs/libquicktime-0.9.4 dv? media-libs/libdv media-video/mjpegtools-1.6.2-r3 dv? >=media-libs/libdv-0.99 media-video/mplayer-1.0_pre6-r1 encode? dv? >=media-libs/libdv-0.9.5 transcode wants libdv <=0.102 and others want it >=0.xyz. Seems to me like portage can't decide correctly whether to slot libdv or to keep it at 0.102. Hope this helps...
Created attachment 75766 [details] piave-0.2.4-r2.ebuild fixed ebuild
Created attachment 75767 [details, diff] files/piave-dv1394.patch patch to fix piave
PLEASE TEST
This patch/ebuild combo works for me. Piave compiles successfully and solved the libdv up/downgrade loop. (I'm on ~amd64). Not sure how well piave works as kdenlive still seems broken, but at least it does compile.
Piave is now masked as it's a dependency of one application: kdenlive-0.2.4 which has been masked too in favour of the newer version kdenlive-0.3.0. Please remove piave from your system. Thanks, Marc.