public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Quinn <gentoo@danielquinn.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] GTK+ circular dependency
Date: Wed, 12 Oct 2016 22:50:42 +0100	[thread overview]
Message-ID: <c7dde9ef-4dec-3490-2a03-2193e08df0d5@danielquinn.org> (raw)

Have any of you seen this before?  This is on a fresh install.  I can't
get anything GNOME-based to install as it looks like gnome-keyring is
bringing in an older version of gtk+ which somehow depends on
gtk-engines-adwaita which in turn depends on gtk+.

Details:
* ACCEPT_KEYWORDS="~amd64"
* Profile: gnome/systemd
* No additional USE flags.



# emerge -auDN --keep-going --with-bdeps=y @world

These are the packages that would be merged, in order:

Calculating dependencies... done!


[nomerge       ] app-crypt/libsecret-0.18.5::gentoo  USE="crypt
introspection -debug {-test} -vala"
[nomerge       ]  gnome-base/gnome-keyring-3.20.0::gentoo  USE="caps
filecaps pam ssh-agent (-selinux) {-test}"
[nomerge       ]   app-crypt/pinentry-0.9.7-r1::gentoo 
USE="gnome-keyring gtk ncurses -caps -emacs -qt4 -qt5 -static"
[nomerge       ]    x11-libs/gtk+-2.24.31-r1:2::gentoo
[3.20.9:3::gentoo] USE="introspection vim-syntax (-aqua) -cups -examples
{-test} -xinerama" ABI_X86="(64) -32 (-x32)"
[ebuild  N     ]     x11-themes/gtk-engines-adwaita-3.20.2::gentoo 
ABI_X86="(64) -32 (-x32)" 2,812 KiB
[ebuild  NS    ]      x11-libs/gtk+-2.24.31-r1:2::gentoo
[3.20.9:3::gentoo] USE="introspection vim-syntax (-aqua) -cups -examples
{-test} -xinerama" ABI_X86="(64) -32 (-x32)" 12,506 KiB
[ebuild  N     ]   app-crypt/gnupg-2.1.15::gentoo  USE="bzip2 gnutls nls
readline usb -doc -ldap (-selinux) -smartcard -tofu -tools" 5,590 KiB
[ebuild  N     ]    app-crypt/pinentry-0.9.7-r1::gentoo 
USE="gnome-keyring gtk ncurses -caps -emacs -qt4 -qt5 -static" 423 KiB
[ebuild  N     ]  gnome-base/gnome-keyring-3.20.0::gentoo  USE="caps
filecaps pam ssh-agent (-selinux) {-test}" 1,187 KiB
[nomerge       ] sys-apps/openrc-0.22.2::gentoo  USE="ncurses netifrc
pam unicode -audit -debug -newnet (-prefix) (-selinux) -static-libs -tools"
[ebuild   R    ]  sys-auth/pambase-20150213::gentoo  USE="cracklib
gnome-keyring* nullok sha512 systemd (-consolekit) -debug -minimal
-mktemp -pam_krb5 -pam_ssh -passwdqc -securetty (-selinux)" 4 KiB

Total: 6 packages (4 new, 1 in new slot, 1 reinstall), Size of
downloads: 22,519 KiB

 * Error: circular dependencies:

(x11-libs/gtk+-2.24.31-r1:2/2::gentoo, ebuild scheduled for merge)
depends on
 (x11-themes/gtk-engines-adwaita-3.20.2:0/0::gentoo, ebuild scheduled
for merge) (runtime)
  (x11-libs/gtk+-2.24.31-r1:2/2::gentoo, ebuild scheduled for merge)
(buildtime)

 * Note that circular dependencies can often be avoided by temporarily
 * disabling USE flags that trigger optional dependencies.



             reply	other threads:[~2016-10-12 21:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 21:50 Daniel Quinn [this message]
2016-10-13  1:36 ` [gentoo-user] GTK+ circular dependency wabe
2016-10-13 17:01   ` Daniel Quinn
2016-10-13 17:14     ` Neil Bothwick
2016-10-13 17:17       ` Daniel Quinn
2016-10-13 17:38         ` Neil Bothwick
2016-10-14  8:09     ` Stroller
2016-10-16 16:37 ` [gentoo-user] " Jonathan Callen

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=c7dde9ef-4dec-3490-2a03-2193e08df0d5@danielquinn.org \
    --to=gentoo@danielquinn.org \
    --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