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
How to avoid superceding? #2898
Comments
Yeah, I'd say it's pretty bad to have That said, since conda 3.3.0, it has been possible to disable automatic updates to conda by adding |
And if you want to disable channel priority altogether, you can do |
If we're going to leave conda auto-updates in the code, I think we should probably make sure it doesn't downgrade. What do you think, @kalefranz? |
@mcg1969 thanks for your feedback. The immediate answer is for me to set I realize that complexity is a bad thing, so probably the behavior of Is there a command line flag for |
Do check out my PR #2900 and see what you think. |
@ijstokes The condarc flag is either |
I don't think conda should get a special hack. I think if we get finer-grained channel priority right, we won't need it. I think... |
Yes, we will have finer-grained control over this. And we'll think through thoroughly what user expectations are, and try to make conda "do what I expect it to do" as much as possible. May still take a couple iterations to get right. |
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 was trying to install a Conda package during a demo. I was surprised to see that the Conda package plan decided to use a Conda package I created end of 2015 and that is available in my channel. I understand why matching packages from explicitly listed channels might have preference, even if it results in a downgrade. But is there a way to say "don't do that?" I imagine if I had a "newer" version in an explicitly listed channel then I might expect different behavior than an older version, but maybe not.
And in the case of Conda (unsurprisingly) there are clearly dangers to having your own conda package in a channel. It isn't a dependency of the listed
genepattern
package, so this is just the "automatically update conda and conda-env" behavior that is then pulling in my custom Conda build. Which then totally breaks my Anaconda distribution (conda
is now gone from my installation -- I will have to hand-patch it back in, I think)The text was updated successfully, but these errors were encountered: