View previous topic :: View next topic |
Author |
Message |
urcindalo l33t
Joined: 08 Feb 2005 Posts: 623 Location: Almeria, Spain
|
Posted: Thu Jan 10, 2013 10:00 am Post subject: Why --tree is broken with --nodeps. Disabling...? |
|
|
Hi!
When I try to run the emwrap emerge wrapper on one of my machines to rebuid the system packages I find this error: Code: | Running emwrap.sh 4.0.8 with gcc-config-r4 Mon Oct 15 21:41:56 PDT 2007
If emwrap.sh is run and it detects a "failed' or "build" file
then it will offer to build them. You can ignor this by not doing
anything and what you wanted todo will start after automaticlly.
work_dir is
1329 build to emerge 1 of 1329 build * --tree is broken with --nodeps. Disabling...
These are the packages that would be merged, in order:
[ebuild R ~] media-gfx/darktable-9999::local USE="gphoto2 kde openmp -facebook -flickr -gnome-keyring" 0 kB |
I googled and found that the --tree is broken with --nodeps. Disabling... warning comes from the file /usr/lib64/portage/pym/_emerge/actions.py from portage. I then rebuilt portage, to no avail.
Also, you can see that the script is not able to distinguish between system or world packages, and even it tries to start with darktable!! I manage an almost twin machine where the script works perfectly (I just ran it), so the problem does not come from it.
What can I try? What should I rebuild? Right now I'm running an "emerge -1 -avt --emptytree system" for the shake of trying.
Any help is welcome.
Just in case, I followed the Intel Compiler Guide in the Gentoo Wiki and recompiled python 2.7 and 3.2 with icc. However, I repeat I manage an almost twin machine where this has also been done but there are no problems at all. Every step taken regarding icc on the failing machine has also been taken on the working one (to the best of my knowledge and memory). |
|
Back to top |
|
|
Veldrin Veteran
Joined: 27 Jul 2004 Posts: 1945 Location: Zurich, Switzerland
|
Posted: Thu Jan 10, 2013 11:43 am Post subject: |
|
|
something is calling emerge with the options -t (--tree) and -O (--nodeps), which cannot work, as -O omits the dependencies, and therefore portage cannot built a tree.
what command are you actually using? Which Version of the script?
did you change any of the emerge opts? (grep EMERGE /etc/{portage/,}make.conf)
V. _________________ read the portage output!
If my answer is too concise, ask for an explanation. |
|
Back to top |
|
|
urcindalo l33t
Joined: 08 Feb 2005 Posts: 623 Location: Almeria, Spain
|
Posted: Fri Jan 11, 2013 9:24 am Post subject: |
|
|
Veldrin wrote: | something is calling emerge with the options -t (--tree) and -O (--nodeps), which cannot work, as -O omits the dependencies, and therefore portage cannot built a tree.
what command are you actually using? Which Version of the script?
did you change any of the emerge opts? (grep EMERGE /etc/{portage/,}make.conf)
V. |
You were right. I had EMERGE_DEFAULT_OPTS="-vt --with-bdeps y" on my failing machine. After removing -vt it now works.
Thanks very much. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|