-
Notifications
You must be signed in to change notification settings - Fork 416
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
meta.yaml
accepts negative build numbers
#5332
Labels
type::bug
describes erroneous operation, use severity::* to classify the type
Comments
jaimergp
added
the
type::bug
describes erroneous operation, use severity::* to classify the type
label
May 9, 2024
Note that if you patch build:
number: -1
string: h123456_1
If you look at the info metadata or the resulting repodata.json, you do see: ...
"conda-build-test-source-url-1.0-h123456_1.tar.bz2": {
"build": "h123456_1",
"build_number": -1,
"depends": [
"python_abi 3.9.* *_cp39"
],
"md5": "822e6e1724c4abbf8c83566dfbf4136e",
"name": "conda-build-test-source-url",
"sha256": "76d97bbde2bbfad7fb0babfa3064ae0d742b401d9bd2b96ac81220e0443e5c03",
"size": 4535,
"subdir": "osx-arm64",
"timestamp": 1715242322366,
"version": "1.0"
},
... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
What happened?
is accepted and fails later down the pipeline due to filename parsing errors, after running the build scripts.
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: