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

Remove BasicTools feedstock. Change name of lib to Muscat #1396

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

fbordeu
Copy link
Contributor

@fbordeu fbordeu commented Feb 19, 2025

Guidelines for marking packages as broken:

  • We prefer to patch the repo data (see here)
    instead of marking packages as broken. This alternative workflow makes environments more reproducible.
  • Packages with requirements/metadata that are too strict but otherwise work are
    not technically broken and should not be marked as such.
  • Packages with missing metadata can be marked as broken on a temporary basis
    but should be patched in the repo data and be marked unbroken later.
  • In some cases where the number of users of a package is small or it is used by
    the maintainers only, we can allow packages to be marked broken more liberally.
  • We (conda-forge/core) try to make a decision on these requests within 24 hours.

What will happen when a package is marked broken?

  • Our bots will add the broken label to the package. The main label will remain on the package and this is normal.
  • Our bots will rebuild our repodata patches to remove this package from the repodata.
  • In a few hours after the anaconda.org CDN picks up the new patches, you will no longer be able to install the package from the main channel.

Checklist:

  • I want to archive a feedstock:
    • Pinged the team for that feedstock for their input.
    • Make sure you have opened an issue on the feedstock explaining why it was archived.
    • Linked that issue in this PR description.
    • Added links to any other relevant issues/PRs in the PR description.

@fbordeu fbordeu requested a review from a team as a code owner February 19, 2025 10:21
@fbordeu
Copy link
Contributor Author

fbordeu commented Feb 19, 2025

Pinged the team for that feedstock for their input. -> I'm the maintainer.

@fbordeu
Copy link
Contributor Author

fbordeu commented Feb 19, 2025

Make sure you have opened an issue on the feedstock explaining why it was archived.

conda-forge/basictools-feedstock#55

@jaimergp
Copy link
Member

By archiving it, the 1.x series won't be rebuilt for newer libraries like boost, so it might become increasingly difficult to install in the future. Just confirming you are ok with that.

@fbordeu
Copy link
Contributor Author

fbordeu commented Feb 24, 2025

Yes I confirm

@jaimergp jaimergp merged commit 1f9a3d2 into conda-forge:main Feb 24, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants