From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Machine completely broken; Ncursed!
Date: Sun, 12 Apr 2015 12:23:56 -0500 [thread overview]
Message-ID: <20150412122356.5cadb5d4@sepulchrave.remarqs> (raw)
In-Reply-To: 2227740.m4amG7ENkq@andromeda
On Sun, 12 Apr 2015 11:12:38 +0200
"J. Roeleveld" <joost@antarean.org> wrote:
> On Saturday, April 11, 2015 08:42:20 PM Alan Grimes wrote:
> > PYTHON_TARGETS="${PYTHON_TARGETS} python2_7 python3_4"
> > PYTHON_SINGLE_TARGET="python2_7"
>
> These are set in your profile, please do not override this.
> In other words, please remove these 2 lines.
I'm not the OP. (I spend less time than him on maintaining my system.)
Should those variables really not be set in make.conf? I added them to
make.conf some time back because portage complained about them, and if I
comment them out, it complains again, like so:
$ emerge -puDv --changed-use @world
These are the packages that would be merged, in order:
Calculating dependencies |
!!! Problem resolving dependencies for sys-apps/util-linux from @system
... done!
!!! The ebuild selected to satisfy "sys-apps/util-linux" has unmet requirements.
- sys-apps/util-linux-2.25.2-r2::gentoo USE="ncurses nls pam (policykit) python suid tty-helpers udev unicode -caps -cramfs -fdformat (-selinux) -slang -static-libs -systemd -test" ABI_X86="64 -32 -x32" PYTHON_SINGLE_TARGET="-python2_7 -python3_3 -python3_4" PYTHON_TARGETS="-python2_7 -python3_3 -python3_4"
The following REQUIRED_USE flag constraints are unsatisfied:
python? ( exactly-one-of ( python_single_target_python3_3 python_single_target_python3_4 python_single_target_python2_7 ) )
The above constraints are a subset of the following complete expression:
python? ( exactly-one-of ( python_single_target_python3_3 python_single_target_python3_4 python_single_target_python2_7 ) python_single_target_python3_3? ( python_targets_python3_3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python2_7? ( python_targets_python2_7 ) )
(dependency required by "@system" [set])
(dependency required by "@world" [argument])
next prev parent reply other threads:[~2015-04-12 17:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 14:22 [gentoo-user] Machine completely broken; Ncursed! Alan Grimes
2015-04-11 14:34 ` Neil Bothwick
2015-04-11 17:22 ` Mick
2015-04-11 19:41 ` Alan Grimes
2015-04-11 21:27 ` Neil Bothwick
2015-04-11 20:04 ` Andreas K. Huettel
2015-04-12 0:42 ` Alan Grimes
2015-04-12 0:58 ` [gentoo-user] " walt
2015-04-12 1:02 ` [gentoo-user] " Peter Humphrey
2015-04-12 1:58 ` Dale
2015-04-12 9:12 ` J. Roeleveld
2015-04-12 17:23 ` »Q« [this message]
2015-04-12 18:35 ` [gentoo-user] " Matti Nykyri
2015-04-13 1:07 ` »Q«
2015-04-13 5:48 ` Alan McKinnon
2015-04-14 2:08 ` »Q«
2015-04-12 20:07 ` J. Roeleveld
2015-04-13 1:15 ` »Q«
2015-04-13 1:24 ` Alec Ten Harmsel
2015-04-13 1:38 ` »Q«
2015-04-13 1:52 ` Alec Ten Harmsel
2015-04-14 1:55 ` »Q«
2015-04-13 5:52 ` Alan McKinnon
2015-04-14 3:38 ` »Q«
2015-04-13 7:51 ` Neil Bothwick
2015-04-14 3:51 ` »Q«
2015-04-14 7:47 ` Neil Bothwick
2015-04-15 3:09 ` »Q«
2015-04-15 8:24 ` Neil Bothwick
2015-04-12 9:31 ` [gentoo-user] " Neil Bothwick
2015-04-12 14:13 ` Andreas K. Huettel
2015-04-11 23:23 ` Fernando Rodriguez
2015-04-12 1:25 ` Alan Grimes
2015-04-12 0:06 ` Peter Humphrey
2015-04-12 1:27 ` Alan Grimes
2015-04-12 14:52 ` Peter Humphrey
2015-04-16 2:40 ` Fernando Rodriguez
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=20150412122356.5cadb5d4@sepulchrave.remarqs \
--to=boxcars@gmx.net \
--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