Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On Tue, 14 Apr 2015 22:09:34 -0500, »Q« wrote: I don't want to advocate for *-. I don't recommend it to anybody. I don't particularly want to argue about how good/bad/ugly it is with anybody, but it's it's tough not to argue when people are telling me I'm causing myself problems and I'm not seeing any such problems. That's fair enough. I have no problem with your using -*, it's your system. Advocating it is another matter, but you're not doing that. -- Neil Bothwick Velilind's Laws of Experimentation: 1. If reproducibility may be a problem, conduct the test only once. 2. If a straight line fit is required, obtain only two data points. pgpaWbgXspQGV.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On Mon, 13 Apr 2015 22:51:58 -0500, »Q« wrote: How can I find out whether the profile is setting those variables? By removing USE=-*. At the moment it doesn't matter which profile you use or what it sets as you are then telling portage to ignore all its settings, even the critical ones. I'm getting conflicting info on this. Do profiles really only set USE flags or do they do something else as well? (Or does USE=-* affect things *other* than USE?) Things like PYTHON_TARGETS, X86_ABI and VIDEO_CARDS are implemented as USE variables, so yes, -* clobbers them too. As portage evolves and the devs update the profiles to keep in line, your system will be come gradually more broken, as happened when PYTHON_TARGET variables were introduced. Following this list and -dev seems to keep me up-to-date on the changes, as happened when the PYTHON_ variables were introduced. AFAICS, the only brokenness so far is that I'm complicating my life more than several people here think I should be. A lot more complicated if you have to follow a mailing list just to keep your system working. You have essentially put your system into a firefighting mode where you have to deal with each change as it breaks things. The real problems occur when the cause of the issue that you are suffering is not clear, and others cannot help because they use a profile so do not experience it. If you comment out your USE line and run emerge --changed-use -p @world (do not use -v!) you will see what you actually need to set. Then you can ad those to make.conf or package.use. It may take you half an hour, but you'll end up with a system that maintains itself to a greater extent. -- Neil Bothwick I just bought a microwave fireplace... You can spend an evening in front of it in only eight minutes... pgpIJvznjq9Fd.pgp Description: OpenPGP digital signature
[gentoo-user] Re: Machine completely broken; Ncursed!
On Tue, 14 Apr 2015 08:47:01 +0100 Neil Bothwick n...@digimed.co.uk wrote: On Mon, 13 Apr 2015 22:51:58 -0500, »Q« wrote: How can I find out whether the profile is setting those variables? By removing USE=-*. At the moment it doesn't matter which profile you use or what it sets as you are then telling portage to ignore all its settings, even the critical ones. I'm getting conflicting info on this. Do profiles really only set USE flags or do they do something else as well? (Or does USE=-* affect things *other* than USE?) Things like PYTHON_TARGETS, X86_ABI and VIDEO_CARDS are implemented as USE variables, so yes, -* clobbers them too. Thanks. A lot more complicated if you have to follow a mailing list just to keep your system working. You have essentially put your system into a firefighting mode where you have to deal with each change as it breaks things. I'd be reading this list anyway. The time I spend heading off and/or dealing with breakage due to *- is negligible, certainly nothing like being in constant firefighting mode. I guess I've spent more time in this thread, in which my system is neither broken nor in danger of breaking, than I've spent on problems due to *- over the past five years. I don't want to advocate for *-. I don't recommend it to anybody. I don't particularly want to argue about how good/bad/ugly it is with anybody, but it's it's tough not to argue when people are telling me I'm causing myself problems and I'm not seeing any such problems.
[gentoo-user] Re: Machine completely broken; Ncursed!
On Sun, 12 Apr 2015 21:52:07 -0400 Alec Ten Harmsel a...@alectenharmsel.com wrote: On 04/12/2015 09:38 PM, »Q« wrote: How can I find out whether the profile is setting those variables? ISTM the emerge errors I posted earlier, which happen if I get rid of those variables in make.conf, indicate that they are not being set at all. You can find all the defaults here: /usr/portage/profiles/base/make.defaults. I don't think the KDE profile overrides any of the python/ruby stuff, just USE. It's strange that you are getting that error from util-linux; I would recommend getting rid of the USE_PYTHON=2.7 line from make.conf and, personally, avoid having so many USE flags in make.conf. Thanks. My /usr/portage/profiles/base/make.defaults has PYTHON_TARGETS=python2_7 python3_3 PYTHON_SINGLE_TARGET=python2_7 The error message was 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 ) ) It looks to me like make.defaults sets exactly one of those. Is it possible my USE=-* wipes out use_expand things as well?
[gentoo-user] Re: Machine completely broken; Ncursed!
On Mon, 13 Apr 2015 07:48:25 +0200
Alan McKinnon alan.mckin...@gmail.com wrote:
On 13/04/2015 03:07, »Q« wrote:
On Sun, 12 Apr 2015 21:35:07 +0300
Matti Nykyri matti.nyk...@iki.fi wrote:
On Apr 12, 2015, at 20:23, »Q« boxc...@gmx.net wrote:
On Sun, 12 Apr 2015 11:12:38 +0200
J. Roeleveld jo...@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:
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 ) )
[snip]
This is because you have set the python use flag in your
make.conf (or package.use).
Remove the python useflag and the problem goes away. It is not set
by the profile but by you. Do you really need it?
I enabled it globally (in make.conf), but I think I only need it
for one or two packages. If I remove it from USE, I get portage
complaining about other things.
USE=python is one of those flags that has no accurate meaning in
real life, and the user needs to make an informed decision. It
doesn't work like USE=sse for example, which means packages that
can use the sse instruction set will compile for it. It's a fairly
exact meaning.
USE=python means use python to do stuff but stuff is not defined
and it's usually hard to find out what it is for a given package. For
some it means to build optional extra tools that run under python,
for some it means to create python language bindings, and for others
it could even mean some critical system function that is implemented
in python and eats your kittens if not enabled. (sort of like how
portage is implemented in python; there's no USE for it but you get
the idea).
Usually, USE=python should be set per-package if you need what it
does. I had it in make.conf myself in my early days and kept getting
into circular dependencies. Sorting that out took some effort.
Portage will almost certainly complain if you take something with
far-reaching effects as USE=python in make.conf and remove it.
So, take each thing it is complaining about and enable or disable it
based on what you need. Tweak as necessary to get the result you want.
Thanks -- that all makes sense. I'm pretty sure I have USE=python
because I thought something like I'm going to have python, so I might
as well let things use it, which I now see to be muddle-headed at
best.
Since it's not causing me any troubles for now, I'll wean myself off of
USE=python when there's some in which I can afford to fix whatever I
break during the process.
[gentoo-user] Re: Machine completely broken; Ncursed!
On Mon, 13 Apr 2015 08:51:57 +0100 Neil Bothwick n...@digimed.co.uk wrote: On Sun, 12 Apr 2015 20:38:17 -0500, »Q« wrote: It's not a bad idea to manage the PYTHON_TARGETS, PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a specific version of python or ruby. If you do not, I would say it is bad. These are set in the profile so that the maintainers can decide when to update to a new stable version. Since all of the various python and ruby libraries are installed from source, it's generally a good idea to wait for the maintainers to stabilize a certain version since that means the library support is also good. How can I find out whether the profile is setting those variables? By removing USE=-*. At the moment it doesn't matter which profile you use or what it sets as you are then telling portage to ignore all its settings, even the critical ones. I'm getting conflicting info on this. Do profiles really only set USE flags or do they do something else as well? (Or does USE=-* affect things *other* than USE?) As portage evolves and the devs update the profiles to keep in line, your system will be come gradually more broken, as happened when PYTHON_TARGET variables were introduced. Following this list and -dev seems to keep me up-to-date on the changes, as happened when the PYTHON_ variables were introduced. AFAICS, the only brokenness so far is that I'm complicating my life more than several people here think I should be.
[gentoo-user] Re: Machine completely broken; Ncursed!
On Mon, 13 Apr 2015 07:52:54 +0200 Alan McKinnon alan.mckin...@gmail.com wrote: On 13/04/2015 03:38, »Q« wrote: On Sun, 12 Apr 2015 21:24:48 -0400 Alec Ten Harmsel a...@alectenharmsel.com wrote: Also, using the KDE profile and having USE=-* seem contrary. One of the main reasons to use a profile is to get a relevant set of USE flags. I don't want the profile's USE flags, but I still thought it best to select the profile that matches what I use the machine for. A profile is indeed intended to match the intended use of the machine, and to do that it does two things: - enables or disables some software (the minor feature) - sets some sane default USE (the major feature) USE=-* essentially undoes the profile entirely rendering it useless. You'd be better off just setting your profile to default and doing all the heavy lifting yourself instead of going with the maintainers suggestions implemented in the profile. I rarely have to mess with changing USE flags as it is now, but setting them up from scratch (something I haven't done in many years) after clobbering the profile's defaults was heavy lifting, for me at least. If I ever have to do it again, I'll check out using a simpler profile without clobbering its USE.
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On Sun, 12 Apr 2015 20:38:17 -0500, »Q« wrote: It's not a bad idea to manage the PYTHON_TARGETS, PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a specific version of python or ruby. If you do not, I would say it is bad. These are set in the profile so that the maintainers can decide when to update to a new stable version. Since all of the various python and ruby libraries are installed from source, it's generally a good idea to wait for the maintainers to stabilize a certain version since that means the library support is also good. How can I find out whether the profile is setting those variables? By removing USE=-*. At the moment it doesn't matter which profile you use or what it sets as you are then telling portage to ignore all its settings, even the critical ones. As portage evolves and the devs update the profiles to keep in line, your system will be come gradually more broken, as happened when PYTHON_TARGET variables were introduced. -- Neil Bothwick The modem is the message. pgpq6lVqxRmXI.pgp Description: OpenPGP digital signature
[gentoo-user] Re: Machine completely broken; Ncursed!
On Sun, 12 Apr 2015 22:07:20 +0200
J. Roeleveld jo...@antarean.org wrote:
On Sunday, April 12, 2015 12:23:56 PM »Q« wrote:
On Sun, 12 Apr 2015 11:12:38 +0200
J. Roeleveld jo...@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:
[snip]
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 ) )
I have never set them and don't remember having an issue.
From the above, it looks like they are all unset when you remove that
line.
I think that's right.
Which profile are you using?
default/linux/amd64/13.0/desktop/kde
And what is the rest of your make.conf?
Before you pore through it, I guess I should point out that it's not
causing me any problems -- I was just curious about why it would be a
bad idea for me to manage those PYTHON_* variables myself. I guess the
most notable thing about my make.conf is that I'm one of those crazy
USE=-* people.
$ cat /etc/portage/make.conf
# Please consult /usr/share/portage/config/make.conf.example for a detailed
example.
CFLAGS=-march=native -O2 -pipe
CXXFLAGS=${CFLAGS}
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST=x86_64-pc-linux-gnu
# weird load averages, maybe this will help
# 7.2 used to be right
MAKEOPTS=--jobs=8 --load-average=11.2
PORTDIR=/usr/portage
DISTDIR=${PORTDIR}/distfiles
PKGDIR=${PORTDIR}/packages
PORT_LOGDIR=/var/log/portage
# layman expands and empty variable, then we postpend
# the main tree to it. This should give the main tree
# precendence.
PORTDIR_OVERLAY=
source /var/lib/layman/make.conf
PORTDIR_OVERLAY=$PORTDIR_OVERLAY $PORTDIR
PORTAGE_ELOG_CLASSES=info warn error
PORTAGE_ELOG_SYSTEM=echo:warn,error save
PORTAGE_SYNC_STALE=10
FEATURES=binpkg-logs buildsyspkg collision-protect downgrade-backup
fail-clean fixlafiles news parallel-fetch parallel-install
preserve-libs sandbox strict unknown-features-warn userfetch
userpriv usersandbox usersync
# see note above about MAKEOPTS
EMERGE_DEFAULT_OPTS=--ask-enter-invalid --jobs=8 --load-average 11.2
--with-bdeps y
LINGUAS=en_US en
ABI_X86=64
CPU_FLAGS_X86=aes avx avx2 fma3 mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2
ssse3
GRUB_PLATFORMS=efi-64
PYTHON_TARGETS=python2_7 python3_4
USE_PYTHON=2.7
PYTHON_SINGLE_TARGET=python2_7
RUBY_TARGETS=ruby20
CURL_SSL=openssl
CALLIGRA_FEATURES=author braindump flow karbon kexi krita plan sheets stage
words
INPUT_DEVICES=evdev mouse keyboard synaptics
# need to add the intel card
VIDEO_CARDS=intel i965 v4l vesa
#VIDEO_CARDS=nvidia v4l vesa
# without this, grub:0 ebuilds mess with /boot
DONT_MOUNT_BOOT=1
USE=-* 64bit X a52 aac aalib accessibility acl acpi additions agg alsa apng
archive asf aspell audio aura avahi avcodec avformat avx bash-completion
bluetooth bookmarks boost branding bzip2 cairo calendar canlock cdda cddb
cdio cdparanoia cdr center-tilde chatzilla chert city classic clucene
color colordiff consolekit cover cracklib crypt cryptsetup css cups curl
cxx dbus declarative dga dillo distinct-l dri dts dvd dvdr edit eigen
encode exif expat extensions extra-cardsets extraengine fam fbcon ffmpeg
filters flac fluidsynth fontconfig fontforge foomatic foomaticdb fortran
ftp gdbm gif glew glib gmp gnutls gost gpl gpm graphviz gstreamer gudev
handbook hbci hddtemp holidays hwdb iconv icu id3tag idn imagemagick imap
inotify input_uvc int-quality ipc ipv6 isag javascript jit joystick jpeg
json kde kdenlive kdepim kerberos kipi kmod ladspa lame lcms libass libev
libkms libnotify libsecret libvisual lm_sensors lzma mad magic matroska
mdnsresponder-compat melt midi mikmod minizip mjpeg mmx mmxext mng mod
modplug mouse mp3 mp4 mpd mpeg mplayer mudflap musepack musicbrainz mysql
nano-syntax natspec ncurses netifrc nls nntp nptl nsplugin ntfsprogs
offensive offlinehelp ofx ogg okular opengl openmp openrc openssl opus
orc output_autofocus output_file output_http output_rtsp output_udp pam
pcf pci pcre pdf perl pm-utils png policykit portmon postproc psf ptpax
pyqt4 python2 qt3support qt4 quicktime raptor readline recursion-limit
redland rss rtc sasl script scripts sdk sdl sdl-image sdl-sound
secure-delete security semantic-desktop sensord session
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On 04/12/2015 09:15 PM, »Q« wrote: Before you pore through it, I guess I should point out that it's not causing me any problems -- I was just curious about why it would be a bad idea for me to manage those PYTHON_* variables myself. I guess the most notable thing about my make.conf is that I'm one of those crazy USE=-* people. It's not a bad idea to manage the PYTHON_TARGETS, PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a specific version of python or ruby. If you do not, I would say it is bad. These are set in the profile so that the maintainers can decide when to update to a new stable version. Since all of the various python and ruby libraries are installed from source, it's generally a good idea to wait for the maintainers to stabilize a certain version since that means the library support is also good. Also, using the KDE profile and having USE=-* seem contrary. One of the main reasons to use a profile is to get a relevant set of USE flags. Alec
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On 04/12/2015 09:38 PM, »Q« wrote: On Sun, 12 Apr 2015 21:24:48 -0400 Alec Ten Harmsel a...@alectenharmsel.com wrote: On 04/12/2015 09:15 PM, »Q« wrote: Before you pore through it, I guess I should point out that it's not causing me any problems -- I was just curious about why it would be a bad idea for me to manage those PYTHON_* variables myself. I guess the most notable thing about my make.conf is that I'm one of those crazy USE=-* people. It's not a bad idea to manage the PYTHON_TARGETS, PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a specific version of python or ruby. If you do not, I would say it is bad. These are set in the profile so that the maintainers can decide when to update to a new stable version. Since all of the various python and ruby libraries are installed from source, it's generally a good idea to wait for the maintainers to stabilize a certain version since that means the library support is also good. How can I find out whether the profile is setting those variables? ISTM the emerge errors I posted earlier, which happen if I get rid of those variables in make.conf, indicate that they are not being set at all. You can find all the defaults here: /usr/portage/profiles/base/make.defaults. I don't think the KDE profile overrides any of the python/ruby stuff, just USE. It's strange that you are getting that error from util-linux; I would recommend getting rid of the USE_PYTHON=2.7 line from make.conf and, personally, avoid having so many USE flags in make.conf. Alec
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On 13/04/2015 03:38, »Q« wrote: On Sun, 12 Apr 2015 21:24:48 -0400 Alec Ten Harmsel a...@alectenharmsel.com wrote: On 04/12/2015 09:15 PM, »Q« wrote: Before you pore through it, I guess I should point out that it's not causing me any problems -- I was just curious about why it would be a bad idea for me to manage those PYTHON_* variables myself. I guess the most notable thing about my make.conf is that I'm one of those crazy USE=-* people. It's not a bad idea to manage the PYTHON_TARGETS, PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a specific version of python or ruby. If you do not, I would say it is bad. These are set in the profile so that the maintainers can decide when to update to a new stable version. Since all of the various python and ruby libraries are installed from source, it's generally a good idea to wait for the maintainers to stabilize a certain version since that means the library support is also good. How can I find out whether the profile is setting those variables? ISTM the emerge errors I posted earlier, which happen if I get rid of those variables in make.conf, indicate that they are not being set at all. When a new version of python (or ruby, I guess) is stabilized, I do have to spend some time making sure those variables are sanely set, and I'd rather just leave it up to the devs. Also, using the KDE profile and having USE=-* seem contrary. One of the main reasons to use a profile is to get a relevant set of USE flags. I don't want the profile's USE flags, but I still thought it best to select the profile that matches what I use the machine for. A profile is indeed intended to match the intended use of the machine, and to do that it does two things: - enables or disables some software (the minor feature) - sets some sane default USE (the major feature) USE=-* essentially undoes the profile entirely rendering it useless. You'd be better off just setting your profile to default and doing all the heavy lifting yourself instead of going with the maintainers suggestions implemented in the profile. -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Re: Machine completely broken; Ncursed!
On Sun, 12 Apr 2015 21:35:07 +0300
Matti Nykyri matti.nyk...@iki.fi wrote:
On Apr 12, 2015, at 20:23, »Q« boxc...@gmx.net wrote:
On Sun, 12 Apr 2015 11:12:38 +0200
J. Roeleveld jo...@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:
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 ) )
[snip]
This is because you have set the python use flag in your make.conf
(or package.use).
Remove the python useflag and the problem goes away. It is not set by
the profile but by you. Do you really need it?
I enabled it globally (in make.conf), but I think I only need it for one
or two packages. If I remove it from USE, I get portage complaining
about other things.
[gentoo-user] Re: Machine completely broken; Ncursed!
On Sun, 12 Apr 2015 21:24:48 -0400 Alec Ten Harmsel a...@alectenharmsel.com wrote: On 04/12/2015 09:15 PM, »Q« wrote: Before you pore through it, I guess I should point out that it's not causing me any problems -- I was just curious about why it would be a bad idea for me to manage those PYTHON_* variables myself. I guess the most notable thing about my make.conf is that I'm one of those crazy USE=-* people. It's not a bad idea to manage the PYTHON_TARGETS, PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a specific version of python or ruby. If you do not, I would say it is bad. These are set in the profile so that the maintainers can decide when to update to a new stable version. Since all of the various python and ruby libraries are installed from source, it's generally a good idea to wait for the maintainers to stabilize a certain version since that means the library support is also good. How can I find out whether the profile is setting those variables? ISTM the emerge errors I posted earlier, which happen if I get rid of those variables in make.conf, indicate that they are not being set at all. When a new version of python (or ruby, I guess) is stabilized, I do have to spend some time making sure those variables are sanely set, and I'd rather just leave it up to the devs. Also, using the KDE profile and having USE=-* seem contrary. One of the main reasons to use a profile is to get a relevant set of USE flags. I don't want the profile's USE flags, but I still thought it best to select the profile that matches what I use the machine for.
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On 13/04/2015 03:07, »Q« wrote:
On Sun, 12 Apr 2015 21:35:07 +0300
Matti Nykyri matti.nyk...@iki.fi wrote:
On Apr 12, 2015, at 20:23, »Q« boxc...@gmx.net wrote:
On Sun, 12 Apr 2015 11:12:38 +0200
J. Roeleveld jo...@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:
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 ) )
[snip]
This is because you have set the python use flag in your make.conf
(or package.use).
Remove the python useflag and the problem goes away. It is not set by
the profile but by you. Do you really need it?
I enabled it globally (in make.conf), but I think I only need it for one
or two packages. If I remove it from USE, I get portage complaining
about other things.
USE=python is one of those flags that has no accurate meaning in real
life, and the user needs to make an informed decision. It doesn't work
like USE=sse for example, which means packages that can use the sse
instruction set will compile for it. It's a fairly exact meaning.
USE=python means use python to do stuff but stuff is not defined and
it's usually hard to find out what it is for a given package. For some
it means to build optional extra tools that run under python, for some
it means to create python language bindings, and for others it could
even mean some critical system function that is implemented in python
and eats your kittens if not enabled. (sort of like how portage is
implemented in python; there's no USE for it but you get the idea).
Usually, USE=python should be set per-package if you need what it
does. I had it in make.conf myself in my early days and kept getting
into circular dependencies. Sorting that out took some effort.
Portage will almost certainly complain if you take something with
far-reaching effects as USE=python in make.conf and remove it.
So, take each thing it is complaining about and enable or disable it
based on what you need. Tweak as necessary to get the result you want.
--
Alan McKinnon
alan.mckin...@gmail.com
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On Sunday, April 12, 2015 12:23:56 PM »Q« wrote:
On Sun, 12 Apr 2015 11:12:38 +0200
J. Roeleveld jo...@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])
I have never set them and don't remember having an issue.
From the above, it looks like they are all unset when you remove that line.
Which profile are you using?
And what is the rest of your make.conf?
--
Joost
[gentoo-user] Re: Machine completely broken; Ncursed!
On Sun, 12 Apr 2015 11:12:38 +0200
J. Roeleveld jo...@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])
Re: [gentoo-user] Re: Machine completely broken; Ncursed!
On Apr 12, 2015, at 20:23, »Q« boxc...@gmx.net wrote:
On Sun, 12 Apr 2015 11:12:38 +0200
J. Roeleveld jo...@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])
This is because you have set the python use flag in your make.conf (or
package.use).
Remove the python useflag and the problem goes away. It is not set by the
profile but by you. Do you really need it?
--
-Matti
[gentoo-user] Re: Machine completely broken; Ncursed!
On 04/11/2015 05:42 PM, Alan Grimes wrote: Byte me. Linux is crap, it takes all the talent I have to keep this piece of junk running. I'll see your grumpy, and raise you two grumpies :p
