-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"conda list" has multiple entries for a package after "conda env update" #4210
Comments
The revision history for the test-env shows that the pyqt and sip packages were not updated, but rather added to the environment by the
|
I attempted to reproduce the same sequence of environment changes with First, I created an environment with
Then, I updated the pyqt package to the newer build 7:
This sequence produces an environment as expected, i.e.,
And the revision history shows that those two packages were upgraded (in rev 1) and not added a second time:
|
Hi there, thank you for your contribution to Conda! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment and we will gladly reopen the issue. In case this issue was originally about a project that is covered by the Anaconda issue tracker (e.g. Anaconda, Miniconda, packages built by Anaconda, Inc. like Anaconda Navigator etc), please reopen the issue there again. Thanks! |
Hi again! This issue has been closed since it has not had recent activity. Thank you for your contribution. |
We've uncovered an interesting behavior with
conda env update
that results in an environment with multiple entries for a couple packages inconda list
output.Background
We use a environment specifiation file to create a conda environment for our Python software (using
conda env create -f ...
). When users install a new release (i.e., an update) of our software, our updater runs aconda env update
with the specification file to update the environment. We've discovered that some of our users have multiple entries for two packages in their environments.Steps to reproduce it
Here's a trimmed down version of our specification file that installs Python 3.4 and PyQt 4.11.4:
NOTE: our original file does not specify the build for the pyqt package (i.e., it only has
pyqt=4.11.1
). When our users first installed our software, build 4 was the latest build available for Windows. Therefore, we include the build above to reproduce those conditions.The environment is created successfully as expected:
Later on, we released a newer version of our Python software. There was no change in our conda environment specification. However, at that time, build 7 of the windows package of pyqt 4.11.4
was available. So when our updater ran
conda env update
with our spec file on a user's system, that build was installed.To reproduce that situation, we use a variation of the first file that now specifies build 7:
Everything appears to work OK when
conda env update
is executed:However,
conda list
now shows two entries for both the pyqt and sip packages:conda info
The text was updated successfully, but these errors were encountered: