public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Dependency conflict.  openjpeg  ffmpeg
Date: Sat, 14 Jun 2014 16:23:44 -0500	[thread overview]
Message-ID: <539CBD60.6000401@gmail.com> (raw)

Howdy,

I can't figure out a way around this one.  Usually keywording, maybe
that should be unkeywording, a newer version works but doesn't seem to
in this case.   This started as part of a emerge -uvaDN world. 

Error I get:

WARNING: One or more updates/rebuilds have been skipped due to a
dependency conflict:

media-libs/openjpeg:0

  (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
conflicts with
    >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
(media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, ebuild scheduled for merge)

Little more info:

root@fireball / # equery list -p openjpeg ffmpeg
 * Searching for openjpeg ...
[IP-] [  ] media-libs/openjpeg-1.4-r1:0
[-P-] [  ] media-libs/openjpeg-1.5.0:0
[-P-] [  ] media-libs/openjpeg-1.5.1:0
[-P-] [ ~] media-libs/openjpeg-1.5.1-r1:0
[IP-] [  ] media-libs/openjpeg-2.0.0:2
[-P-] [ -] media-libs/openjpeg-9999:2

 * Searching for ffmpeg ...
[-P-] [  ] media-video/ffmpeg-0.10.12:0.10
[-P-] [  ] media-video/ffmpeg-1.0.8:0
[-P-] [  ] media-video/ffmpeg-1.0.9:0
[-P-] [  ] media-video/ffmpeg-1.2.6:0
[-P-] [  ] media-video/ffmpeg-2.2.2:0/52.55.55
[-P-] [  ] media-video/ffmpeg-2.2.3:0/52.55.55
[IP-] [  ] media-video/ffmpeg-2.2.3-r1:0/52.55.55
[-P-] [ -] media-video/ffmpeg-9999:0/52.55.55
root@fireball / #

I try not to use the 9999 versions.  I don't think I ever have.  I tried
unmerging openjpeg and ffmpeg, doing the preserved-rebuild thing and I
still get this error when I try to update again.  I have also synced
twice just in case I got a mixed version of the tree.  I also tried to
do a emerge -e system as well but it spits that error out first thing.

Anyone shed some light on this? 

Thanks.

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!



             reply	other threads:[~2014-06-14 21:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 21:23 Dale [this message]
2014-06-14 23:00 ` [gentoo-user] Dependency conflict. openjpeg ffmpeg Alan McKinnon
2014-06-15  0:12   ` Dale
     [not found]   ` <EQDB1o00e1kktTk01QDC7q>
2014-06-15  1:20     ` John Campbell
2014-06-15  2:10       ` Dale
     [not found]       ` <ESAJ1o00S1kktTk01SAKbb>
2014-06-15  2:31         ` John Campbell
2014-06-15  5:10           ` Dale
2014-06-15  8:46             ` Neil Bothwick
2014-06-15  8:59               ` Dale
2014-06-15  9:09                 ` Neil Bothwick
2014-06-15 10:29                   ` Dale
     [not found]           ` <EVAt1o00G1kktTk01VAu3p>
2014-06-15  6:13             ` John Campbell
2014-06-15  6:40               ` wraeth
2014-06-15  6:56                 ` wraeth
2014-06-15  8:47               ` Dale
2014-06-16  7:43                 ` [gentoo-user] " Jonathan Callen
2014-06-17 23:43       ` [gentoo-user] " Dale
2014-06-19 22:03         ` Dale
2014-06-17 15:56 ` thegeezer
2014-06-17 21:10   ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=539CBD60.6000401@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox