On Thu, Apr 29, 2010 at 9:32 PM, Ajai Khattri <a...@bway.net> wrote:
>
> I have unmerged ffmpeg, libraw1394 and libdc1394 and I still can't resolve
> this block:
>
> [nomerge      ] media-video/ffmpeg-0.5_p20373  USE="X alsa amr encode
> hardcoded-tables ieee1394 ipv6 network theora threads vorbis x264 zlib
> (-3dnow) (-3dnowext) -altivec -bindist -cpudetection -custom-cflags -debug
> -dirac -doc -faac -faad -gsm -jack -jpeg2k (-mmx) (-mmxext) -mp3 -oss -pic
> -schroedinger -sdl -speex (-ssse3) -test -v4l -v4l2 -vdpau -xvid"
> VIDEO_CARDS="(-nvidia)"  [0]
> [ebuild  N    ]  media-libs/opencore-amr-0.1.2  849 kB [0]
> [ebuild  N    ]  sys-libs/libraw1394-2.0.4  368 kB [0]
> [nomerge      ] x11-libs/gtk+-2.18.7 [2.16.6] USE="cups jpeg tiff (-aqua)
> -debug -doc -jpeg2k -test -vim-syntax -xinerama (-X%*)"  [0]
> [ebuild  N    ]  media-libs/tiff-3.9.2-r1  USE="cxx jpeg zlib -jbig" 1,387
> kB [0]
> [ebuild  N    ]   media-libs/jpeg-8a  951 kB [0]
> [blocks B     ] <media-libs/libdc1394-1.2.2 ("<media-libs/libdc1394-1.2.2"
> is blocking sys-libs/libraw1394-2.0.4)
>
> Total: 79 packages (68 upgrades, 10 new, 1 in new slot, 6 uninstalls), Size
> of downloads: 174,892 kB
> Conflict: 13 blocks (1 unsatisfied)
> Portage tree and overlays:
>  [0] /usr/portage
>  [?] indicates that the source repository could not be determined
>
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
>
>  ('ebuild', '/', 'media-libs/libdc1394-1.2.1', 'merge') pulled in by
>    media-libs/libdc1394 required by ('ebuild', '/',
> 'media-video/ffmpeg-0.5_p20373', 'merge')
>
>  ('ebuild', '/', 'sys-libs/libraw1394-2.0.4', 'merge') pulled in by
>    sys-libs/libraw1394 required by ('ebuild', '/',
> 'media-video/ffmpeg-0.5_p20373', 'merge')
>    >=sys-libs/libraw1394-0.9.0 required by ('ebuild', '/',
> 'media-libs/libdc1394-1.2.1', 'merge')

Use the --tree option in your emerge commandline so it will show which
packages are trying to pull in these. It looks like you're using
stable, I'm on ~amd64 and don't have these blocks so maybe it's
something worked out by newer versions. On the other hand, if you have
unmasked any unstable packages maybe they're trying to pull in the
conflictiong versions?

Reply via email to