Create tsid-broken.yml #1679
Merged
Create tsid-broken.yml #1679
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello, any update on this issue? @conda-forge/core |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pinged the team for the package for their input.(I am maintainer of this feedstock)Ping @conda-forge/tsid
Hello,
We wanted to add a compilation flag to the TSID feedstock to enable some feature that is now almost always used by the users (see conda-forge/tsid-feedstock#49 ).
The plan was to enable the feature before the release of 1.9.0 so that requiring version 1.9.0 or higher would always guarantee having this feature.
However, the auto-merge bot was faster than us and the release got merge before merging the feature flag in the recipe (see conda-forge/tsid-feedstock#50 ).
Thus, the first build of TSID 1.9.0 doesn't contain this flag, but the second and all the one to come will.
In order to have something more consistent, would it be possible to remove this first build from the channel (files listed in this PR). This would ensure the flag is always on for any build/version above 1.9.0 .
Thank you