conda --clone surprised me by downloading a stack of files
#145
Comments
|
From @ijstokes on September 12, 2017 16:9 I wonder if this is related to #4138 |
|
From @ijstokes on September 12, 2017 16:45 I am wondering if conda is somehow exactly tracking the source of packages in the environment I am cloning from, including the auth token that was used at that time to fetch the particular package. And then the In the event the auth token is expired or has been rescinded this is going to create problems (if it is how things work). In any case the |
|
This is actually an issue with constructor. It's maybe partially related to #138. But there's also probably more to it. I'm going to move this over to the constructor tracker now. |
|
Any update on the issue? Met the same problem today. |
|
Same here. I encountered this clone/downloading issue when using conda from Anaconda 5.1.0. I know that I did not have this issue when using Anaconda 5.0.1 because I wrote a detailed process for building a particular piece of software that involved the --clone procedure and worked without downloading any packages. So, I went back to Anaconda 5.0.1....and now it ALSO downloads packages. I cannot revert back to it working the way it used to it seems. Edit: Ok, I retract some of that. Basically, I'm switching back and forth between 5.0.1 and 5.1.0 usage while I try some things, and I have now found that if I remove 5.1.0, delete the ~/.conda dir, and (most importantly) close the shell and open a new one....then I can once again use conda from Anaconda 5.0.1 to create a new environment with --clone, and it does not download anything. In other words, it is working again like before. That is good. The issue remains with 5.1.0 that trying to clone the install directory for Anaconda 5.1.0 when making a new conda environment causes it to try to download everything. |
|
@robgics Do you face the same issue with Anaconda 5.2.0 ? |
|
Did a quick test: This is a |
|
xref: conda/conda#7398 |
Not entirely, apparently: |
|
Sorry, was away for the week. I just tried Anaconda 5.2.0 and saw the same issue....cloning caused downloading of all packages. @mbargull No, I know I didn't do that because I really have never run "conda clean". I typically just delete ~/.conda* before doing something new as a way to reset my system. Perhaps that's not a good idea...? I have confirmed that in the cloned dir pkgs there are all of the .tar.bz2 files that should be there. |
|
Not sure if it helps, but on a clean system, I don't see the problem when using conda 4.3.30, and I do when using conda 4.4.10. |
|
Is there a workaround for this? I am working on a fairly limited server without the ability to modify the |
|
To provide some update on this one, hope might help for the issue. I use the same conda version on both my work laptop and my PC at home. For my PC at home, conda didn't run into such problems. I'm pretty sure the configuration are the same, the differences might be that I don't have full admin access on my work laptop. |
|
Sorry for the form letter here—I'm doing some issue cleanup right now and closing out some stale issues. Constructor 3.x was a significant rewrite, and so many of the issues filed before its release would need to be re-tested / re-verified. If you have good reason to believe this still needs to be addressed in 3.x, please feel free to re-open or file a new issue with additional information on how to reproduce the issue on the latest versions of constructor. NOTE: Heck I don't even understand why this is a constructor issue and not a conda issue. |
|
Hi there, thank you for your contribution! This issue has been automatically locked because it has not had recent activity after being closed. Please open a new issue if needed. Thanks! |
From @ijstokes on September 12, 2017 15:57
TL;DR: I expect
conda --cloneto benefit from the fact that all the necessary files for the clone environment are already on my system, and nothing needs to be downloaded. But that does not seem to be the case.Details:
I'm trying to clone my base environment. Meaning I want an exact* clone of my base environment (* understanding some packages can, at this point, only exist in the base environment and so they won't be in the clone). Worst case scenario the clone will be a subset of what is in my base environment, which I would take to mean that all the bytes related to the clone are already on my system. So it is a surprise when this operation triggers a download of basically everything I have.
You get the idea!
Copied from original issue: conda/conda#5953
The text was updated successfully, but these errors were encountered: