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

Package string substitution not working #156

Open
jchodera opened this issue Nov 3, 2018 · 2 comments
Open

Package string substitution not working #156

jchodera opened this issue Nov 3, 2018 · 2 comments

Comments

@jchodera
Copy link
Member

jchodera commented Nov 3, 2018

I've reworked this repo to

  • include the commit hash in the package build string so that old commit builds are retained
  • push to a new org, omnia-dev, to make it easier to test different commits without swamping production releases

Unfortunately, our cobbled-together conda-build-all won't substitute the git hash correctly in get_bldpkg_path(), leading to an omission in the package name defined in meta.yaml

  string: py{{ py }}_cuda{{ CUDA_SHORT_VERSION }}_{{ environ.get("GIT_DESCRIBE_HASH", "")[1:8] }}_1

which results in the error

Attempting to upload package to anaconda cloud as user omnia-dev...
ERROR: File does not exist: /opt/conda/conda-bld/linux-64/openmm-7.4.0-py37_cuda75__1.tar.bz2
@jchodera
Copy link
Member Author

jchodera commented Nov 3, 2018

@Lnaden: Maybe you have some insight here?

@jaimergp
Copy link
Collaborator

Just adding that this is still the case. I want to use GIT_BUILD_STR as part of the build string; this works at build time, but when it's time to upload the package to Anaconda, the filename gets rendered wrong: GIT_BUILD_STR seems to be blank.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants