public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] openjpeg dependency conflict
Date: Sat, 8 Nov 2014 18:46:27 +0200	[thread overview]
Message-ID: <545e4924.c28a700a.6892.ffffdd2f@mx.google.com> (raw)
In-Reply-To: <545DF24B.4010500@gmail.com>

On Sat, 08 Nov 2014 18:36:59 +0800 Lin Xiao <xiaoliniess@gmail.com> wrote:

> 
> On 11/08/2014 04:43 PM, Gevisz wrote:
> > Yesterday, during my system update,
> > I have got the following warning:
> >
> >   WARNING: One or more updates have been skipped due to a dependency conflict:
> >
> >   media-libs/openjpeg:2
> >
> >     (media-libs/openjpeg-2.1.0::gentoo, ebuild scheduled for merge) conflicts with
> >       <media-libs/openjpeg-2.1:2 required by (app-text/mupdf-1.3_p20140118::gentoo, installed)
> >
> > Here is more global view:
> >
> >   # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
> >
> >   These are the packages that would be merged, in order:
> >
> >   Calculating dependencies... done!
> >   [ebuild     U  ] media-sound/pulseaudio-5.0-r4 [5.0-r2]
> >
> >   WARNING: One or more updates have been skipped due to a dependency conflict:
> >
> >   media-libs/openjpeg:2
> >
> >     (media-libs/openjpeg-2.1.0::gentoo, ebuild scheduled for merge) conflicts with
> >       <media-libs/openjpeg-2.1:2 required by (app-text/mupdf-1.3_p20140118::gentoo, installed)
> >
> >   Would you like to merge these packages? [Yes/No] n
> >
> > After that I tryed to depclean mupdf package so that to emerge it later
> > but it did not work as mupdf actually was needed for llpp...
> >
> > So, I depcleaned llpp and then mupdf and all the other related packages.
> >
> > After that, I did system update that this time released no warning.
> >
> > Then I tried to emerge llpp back but once again got the following:
> >
> >
> >   # emerge --ask llpp
> >
> >   These are the packages that would be merged, in order:
> >
> >   Calculating dependencies... done!
> >   [ebuild  N     ] media-libs/openjpeg-2.0.0  USE="-doc -static-libs {-test}" 
> >   [ebuild  N     ] x11-misc/xsel-1.2.0 
> >   [ebuild  N     ] dev-lang/ocaml-3.12.1  USE="X gdbm ncurses ocamlopt -emacs -latex -tk -xemacs" 
> >   [ebuild  N     ] app-text/mupdf-1.3_p20140118  USE="X -static -static-libs -vanilla" 
> >   [ebuild  N     ] dev-ml/lablgl-1.05  USE="glut ocamlopt -doc -tk" 
> >   [ebuild  N     ] app-text/llpp-17_p20140112  USE="ocamlopt -static" 
> >
> >   WARNING: One or more updates have been skipped due to a dependency conflict:
> >
> >   media-libs/openjpeg:2
> >
> >     (media-libs/openjpeg-2.1.0::gentoo, ebuild scheduled for merge) conflicts with
> >       <media-libs/openjpeg-2.1:2 required by (app-text/mupdf-1.3_p20140118::gentoo, ebuild scheduled for merge)
> >
> >
> >   Would you like to merge these packages? [Yes/No] n
> >
> >   Quitting.
> >
> > Is this a bug?
> >
> > What shall I do to keep my system clean?
> > (except for not installing llpp, of course :)
> >
> >
> >
> That's just a WARNING. You can safely press 'y' to merge those packages.
> Mupdf expect <media-libs/openjpeg-2.1:2. But the latest stable version
> of openjpeg is 2.1.0.
> So the warning just telling you that update to latest openjpeg is skipped.
> Mupdf-1.5-r1 doesn't have this restriction. So when it's stabilized the
> warning will gone.

Ok, thank you for explanation.


      reply	other threads:[~2014-11-08 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08  8:43 [gentoo-user] openjpeg dependency conflict Gevisz
2014-11-08 10:36 ` Lin Xiao
2014-11-08 16:46   ` Gevisz [this message]

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=545e4924.c28a700a.6892.ffffdd2f@mx.google.com \
    --to=gevisz@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