-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Update Dashing to 0.5.3; WIP #24230
Update Dashing to 0.5.3; WIP #24230
Conversation
@SilasK Would you be willing to give me a hand? I find that Do you have a recommendation for moving forward? Daniel |
Sorry, this is too complicated for me. Can someone else from @bioconda/core help? |
@@ -11,21 +11,21 @@ build: | |||
source: | |||
git_url: https://github.com/dnbaker/dashing | |||
git_rev: v{{ version }} | |||
sha256: {{sha256}} | |||
# sha256: {{sha256}} How is this found? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# sha256: {{sha256}} How is this found? | |
sha256: unused |
I have not used git_url
for packages in the past, but it seems like it is what most other contributors do. You may also need to add - missing_hash
to your skip-lints:
section.
The old version of one of our tools faced a similar issue when building on the bioconda containers. We were able to get successful linking by using the |
Fantastic. Thank you for the response! This should be the guidance I need to get the new package up and running. I'll come back if I have any more questions. |
Now available in version 1.0 |
I'm trying to update Dashing from 0.4.0 to 0.5.2. I don't know how to calculate the sha256 digest of a package being built from a git tag; this might break things, unfortunately. For this package, we're building from source so as to use the right vectorized instructions for a given machine.
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
@BiocondaBot please add label
command.@bioconda/core
in a comment.Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update
@BiocondaBot please add label
please review & merge
label.@BiocondaBot please fetch artifacts
You can use this to test packages locally.
For members of the Bioconda project, the following command is also available:
@BiocondaBot please merge
Someone must approve a PR first!
This reduces CI build time by reusing built artifacts.
Also, the bot watches for comments from non-members that include
@bioconda/<team>
and will automatically re-post them to notify the addressed<team>
.