Skip to content

Add a conda-forge mirrored_channel#817

Merged
hmaarrfk merged 5 commits intoconda-forge:mainfrom
IsabelParedes:mirrored
Oct 14, 2025
Merged

Add a conda-forge mirrored_channel#817
hmaarrfk merged 5 commits intoconda-forge:mainfrom
IsabelParedes:mirrored

Conversation

@IsabelParedes
Copy link
Member

@IsabelParedes IsabelParedes commented Sep 11, 2025

This PR adds https://prefix.dev/conda-forge as a backup to the default conda-forge channel for a more robust installation.

@IsabelParedes IsabelParedes marked this pull request as ready for review September 11, 2025 12:44
@IsabelParedes IsabelParedes requested a review from a team as a code owner September 11, 2025 12:44
@hmaarrfk
Copy link
Contributor

I would like @wolfv 's thumbs up on this before I start to consider.


Here is the question I have:

Q: Does this change mean that I would be downloading TWO repo datas?

Backstory:

  • My general "annoyance" with conda/mamba is that they keep downloading 40MB of "repodata".
  • When I am in the office, that takes like 10 seconds.
  • When I am on a hotspot it is painfully slow to do this when my package is "already in my cache" or "less than 1MB in size".

@SylvainCorlay
Copy link
Member

Q: Does this change mean that I would be downloading TWO repo datas?

It only downloads one repodata. It fall backs to prefix.dev on a per-file basis.

@millsks
Copy link
Contributor

millsks commented Sep 12, 2025

Will this affect users that are on a corporate network that get blocked from public channels? Should they remove the mirrored_channels if they are replacing conda-forge under channels with their internal/private proxy remote? Or should they leave conda-forge as the primary and replace the anaconda and prefix mirrors with their internal/private proxy remotes?

@SylvainCorlay
Copy link
Member

Will this affect users that are on a corporate network that get blocked from public channels? Should they remove the mirrored_channels if they are replacing conda-forge under channels with their internal/private proxy remote? Or should they leave conda-forge as the primary and replace the anaconda and prefix mirrors with their internal/private proxy remotes?

This only impacts what it means to get things from "conda-forge".

@millsks
Copy link
Contributor

millsks commented Sep 12, 2025

Thanks @SylvainCorlay. We rebuild the installer with internal settings already in place so the end users don't have to update their condarc locally or on our build pipeline. Thank you for clearing that up!

Copy link
Contributor

@hmaarrfk hmaarrfk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx for answering my questions.

I would like to leave this open for like 2 weeks to ensure that others stakeholders have time to see it.

Copy link
Member

@xhochy xhochy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like a reasonable change

@wolfv
Copy link
Member

wolfv commented Sep 22, 2025

From prefix side, this is totally fine :)

@hmaarrfk
Copy link
Contributor

@isuruf @scopatz any thoughts?
https://github.com/orgs/conda-forge/teams/miniforge

(I'll probably wait an other 2 weeks)

Copy link
Member

@h-vetinari h-vetinari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hmaarrfk hmaarrfk merged commit 7f42264 into conda-forge:main Oct 14, 2025
8 checks passed
@IsabelParedes IsabelParedes deleted the mirrored branch October 14, 2025 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants