Skip to content

Commit 1405263

Browse files
committed
don't pin build number of libtorch in pytorch (for non-megabuild)
otherwise conda breaks ``` conda_build.exceptions.RecipeError: Mismatching hashes in recipe. Exact pins in dependencies that contribute to the hash often cause this. Can you change one or more exact pins to version bound constraints? Involved packages were: Mismatching package: libtorch (id cpu_generic_habf3c96_0); dep: libtorch 2.6.0.rc7 *0; consumer package: pytorch ```
1 parent 7cd981d commit 1405263

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

recipe/meta.yaml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -292,8 +292,9 @@ outputs:
292292
- {{ pin_subpackage('libtorch', exact=True) }}
293293
run:
294294
- {{ pin_subpackage('libtorch', exact=True) }} # [megabuild]
295-
# for non-megabuild, allow libtorch from any python version
296-
- libtorch {{ version }}.* *_{{ build }} # [not megabuild]
295+
# for non-megabuild, allow libtorch from any python version;
296+
# pinning build number would be nice but breaks conda
297+
- libtorch {{ version }}.* # [not megabuild]
297298
- llvm-openmp # [osx]
298299
- intel-openmp {{ mkl }} # [win]
299300
- libblas * *{{ blas_impl }} # [blas_impl == "mkl"]

0 commit comments

Comments
 (0)