Mark all build packages as broken; use python-build instead #1048
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Guidelines for marking packages as broken:
instead of marking packages as broken. This alternative workflow makes environments more reproducible.
not technically broken and should not be marked as such.
but should be patched in the repo data and be marked unbroken later.
the maintainers only, we can allow packages to be marked broken more liberally.
conda-forge/core
) try to make a decision on these requests within 24 hours.What will happen when a package is marked broken?
broken
label to the package. Themain
label will remain on the package and this is normal.anaconda.org
CDN picks up the new patches, you will no longer be able to install the package from themain
channel.Checklist:
There is a bit of a lingering issue with the
build
packages. This was discussed in the conda-forge core meeting on 2024-08-21. Here is an excerpt from the notes.Marking the
build
packages as broken and directing users to the python-build packages is the agreed-upon strategy.python-build
andbuild
packages, but thebuild
packages are horribly outdatedbuild
, find it outdated and run around confused until they come uponpython-build
.build
topython-build
so both names work with current versions?build
packagesbroken
to force people to migrate?build
and then the bot will send a PR.build
backping @conda-forge/build, @conda-forge/python-build, @conda-forge/core.