Skip to content
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

Bundled conda-standalone will inherit settings from existing .condarc files #542

Open
2 tasks done
jaimergp opened this issue Aug 12, 2022 · 2 comments · May be fixed by #863
Open
2 tasks done

Bundled conda-standalone will inherit settings from existing .condarc files #542

jaimergp opened this issue Aug 12, 2022 · 2 comments · May be fixed by #863
Labels
stale::recovered [bot] recovered after being marked as stale type::bug describes erroneous operation, use severity::* to classify the type

Comments

@jaimergp
Copy link
Contributor

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

Our bundled conda-standalone.exe will read and load existing .condarc configurations, which might break the solver behavior and possibly others. For example, we built the installer with specs from different channels with channel_priority: flexible (default) but the user running the installer has a .condarc file with channel_priority: strict -- potential problems.

The solution is to add a flag or environment variable to upstream conda to disable the search path for .condarc files.

Conda Info

N/A

Conda Config

N/A

Conda list

N/A

Additional Context

This could go to conda/conda-standalone too, but I'll leave it here as a reminder to enable once available, since we are the primary users of that tool.

@jaimergp jaimergp added the type::bug describes erroneous operation, use severity::* to classify the type label Aug 12, 2022
@github-actions
Copy link

Hi there, thank you for your contribution!

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:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Aug 13, 2023
@jaimergp
Copy link
Contributor Author

Still an issue.

@github-actions github-actions bot added stale::recovered [bot] recovered after being marked as stale and removed stale [bot] marked as stale due to inactivity labels Aug 15, 2023
@marcoesters marcoesters linked a pull request Sep 19, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale::recovered [bot] recovered after being marked as stale type::bug describes erroneous operation, use severity::* to classify the type
Projects
Status: No status
1 participant