Closed ijstokes closed 8 years ago
Ian, I am sorry this is happening to you. I know it's likely to be a big log, but can you send the full debug output?
I have two guesses as to what this could be. One is that one of the packages in your list has a dependency on conda. If that is the case, then we need to include that package in any error messages.
The other is that somehow Conda is fooled into thinking this is a root environment and is adding conda to the spec list because of its auto update functionality. If you would like to test this theory, add auto_update_conda: false
to your .condarc and try again.
constructor
is the offending package.
How about something like this:
0203-mgrant:conda mgrant$ conda install -n test constructor conda-build
Fetching package metadata .......
Solving package specifications: ..........
Error: the following specs depend on 'conda' and can only be installed
into the root environment: constructor conda-build
Resolved by #2956
FYI conda search --reverse-dependency conda
would have made this easier to find.
Ha ha! I had no idea that existed. And in fact I wrote r.depends_on
not knowing that existed.
@mcg1969 that is super, thanks so much. And @asmeurer thanks for the tip: that will be super useful. I also had no idea that option existed. It looks like this problem has been "solved" in the PR that provides better error information, but if necessary, I had already attached the full debug log to the original post (but you'll need to look at it in GH: it is linked inline in the middle of the OP, just before the conda info
output.
Hi there, thank you for your contribution to Conda!
This issue has been automatically locked since it has not had recent activity after it was closed.
Please open a new issue if needed.
I'm trying to create a "kitchen sink" environment. I copied the list of everything that we say is available for Python 3.5:
https://docs.continuum.io/anaconda/pkg-docs
I removed anything that wasn't available for Linux, then I removed the obvious "trouble" packages: anaconda, conda, and a few others that I thought might be problematic. I then had a list of 381 packages (~30 removed), and I tried to create an environment with them. No luck:
I'm happy to remove more packages, but this isn't giving me any good hints as to the source of the problem.
I can't figure out how to proceed. I mean, I could do a divide and conquer on the list to isolate the package(s) causing problem(s), but that seems like a lot of work and might not work.
This isn't me trying to be difficult: we have a client who has asked for "everything", so I'm trying to figure out how to give that to them.
Below are the
kitchensink.txt
file and also the output of the command when executed withconda --debug
.debug_log.txt kitchensink.txt
Here are the entries that stick out to me (not that I can interpret them):
Associated numbers:
309: no other instances
4:
7:
31:
32: