-
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 revbayes to v1.1.0 #38524
Update revbayes to v1.1.0 #38524
Conversation
Note that while there are references to v1.0.14 in the git history, this was not tagged so identifying the exact commit is non trivial. Note also that the v1.1 tag was premature and the code at that point still reported version v1.0.14, which was rectified a few days later with the v1.1.0 tag which is used here.
c0e3a81
to
cf0ea0b
Compare
Hmm, failing here:
This is in the cmake based build script, which calls https://github.com/revbayes/revbayes/blob/master/projects/cmake/generate_version_number.sh or previously https://github.com/revbayes/revbayes/blob/master/projects/cmake/generate_version_number.sh |
The git version thing may not be critical, next the build script does this:
That seems to fail, and the
|
Any thoughts @brisk022 on what needs changing since your original revbayes recipe? |
@peterjc maybe try the following:
(and yes, I tried to push this before realising the branch is in your fork, not the upstream repo. sorry if you got any strange mail/pr there!) |
Suggestion from @kdm9
Worth a try, thanks. |
Same cmake message:
I wonder if |
Closing in favor of #52069; |
Note that while the current recipe pointed to git tag v1.0.13,
that is no longer in the upstream repository.that is in the archive repository https://github.com/revbayes/revbayes.archiveWhile there are references to v1.0.14 in the git history, again this has no tag, so identifying the exact commit is non trivial.
Note also that the v1.1 tag was premature and the code at that point still reported version v1.0.14, which was rectified a few days later with the v1.1.0 tag which is used here.
If this works, we can next do v1.1.1 (which had changes to the random number seed behaviour), v1.2.0 and v1.2.1 (which all have git tags).
See https://github.com/revbayes/revbayes/blob/master/NEWS.md
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>
.