Final Package Has Additional Constraints Not Specified in meta.yaml
#5002
Labels
source::community
catch-all for issues filed by community members
stale::closed
[bot] closed after being marked as stale
stale
[bot] marked as stale due to inactivity
type::bug
describes erroneous operation, use severity::* to classify the type
Checklist
What happened?
I have a conda package I build using
conda-build
, where I specify the following dependencies in ourmeta.yaml
file (somewhat simplified):But the output package has the following dependency version constraints (for Python 3.10 and Linux x86):
There are 3 inconsistencies between the specification and actual constraints:
meta.yaml
but is constrained to>=8.2.1,<9.0a0
in the final output>=1.23.5,<2.0a0
in the final output but should be>=1.18,<1.24
Any ideas what might be causing these issues?
Conda Info
No response
Conda Config
Conda list
Additional Context
I build this package for 3 Python versions (3.8, 3.9, 3.10) and a couple of environments, but the issue appears in all builds. I'm generally happy to modify the dependency constraints around, but would like to confirm if this is a bug or expected behavior first.
The text was updated successfully, but these errors were encountered: