Update nextstrain/auspice to 2.38.0 #36997
Conversation
|
@BiocondaBot please merge |
|
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
|
I received an error uploading the build artifacts or merging the PR! |
|
@BiocondaBot please merge |
|
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
|
I received an error uploading the build artifacts or merging the PR! |
|
@BiocondaBot please fetch artifacts |
|
No artifacts found on the most recent Azure build. Either the build failed, the artifacts have were removed due to age, or the recipe was blacklisted/skipped. |
|
@BiocondaBot please update |
|
@BiocondaBot please fetch artifacts |
|
@BiocondaBot please merge |
|
No artifacts found on the most recent Azure build. Either the build failed, the artifacts have were removed due to age, or the recipe was blacklisted/skipped. |
|
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
|
I received an error uploading the build artifacts or merging the PR! |
|
Looks like it got blacklisted during the last migration. I've removed it so we can debug that here. nextstrain itself also appears to be in there, so we'll want to get that removed quickly too (different PR though). |
|
Thanks @dpryan79! Is there a changelog explaining what happened with the migration? I noticed there is now osx-64 etc, but would love to have a detailed discussion. Is that available somewhere? Was it blacklisted because it didn't work after migration to get the migration done? Would be nice if there were issues for each blacklisted recipe, with the maintainers of that recipe pinged! |
|
There are thousands of packages, so no changelog other than with git. The last migration was for python 3.10. |
|
I didn't mean put blacklist in changelog, but infra changes, and big
changes like adding subchannels.
Git is too much with the many packages. A brief note when major things
change, once a week or month would be great.
Did Auspice get blacklisted during the Python 3.10 migration - what did
that migration entail? Simply adding Python 3.10? Would it then be enough
to pin python to <3.10 for now? Or do I misunderstand?
…On Fri, Sep 16, 2022, 14:19 Devon Ryan ***@***.***> wrote:
There are thousands of packages, so no changelog other than with git. The
last migration was for python 3.10.
—
Reply to this email directly, view it on GitHub
<#36997 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF77AQI4ONYUFCD74KGYJMDV6RQVDANCNFSM6AAAAAAQN3JVKU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Most likely there were other pinning changes that came along with python 3.10, I unfortunately don't have the full list (we share those with conda-forge, which is doing almost daily updates to their pinnings...so I don't think they even bother keeping track). |
|
I see, sounds complicated - so the best would maybe be to ping maintainers
if their package gets blacklisted.
It was quite confusing to get the build to succeed but merge to fail.
Is it possible to fail the build instead to be more transparent to
maintainers?
…On Fri, Sep 16, 2022, 14:37 Devon Ryan ***@***.***> wrote:
Most likely there were other pinning changes that came along with python
3.10, I unfortunately don't have the full list (we share those with
conda-forge, which is doing almost daily updates to their pinnings...so I
don't think they even bother keeping track).
—
Reply to this email directly, view it on GitHub
<#36997 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF77AQPOU75WXK74K7SHVTDV6RSY7ANCNFSM6AAAAAAQN3JVKU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Yeah, I think there's an issue open on bioconda-utils to have the linting step fail in such cases. It'd be much nicer that way. |
|
The error on OSX is |
|
Looks like we can put in a |
|
@BiocondaBot please merge |
|
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
|
Thanks a lot for debugging!
…On Sat, Sep 17, 2022, 15:44 Bioconda Bot ***@***.***> wrote:
Merged #36997 <#36997>
into master.
—
Reply to this email directly, view it on GitHub
<#36997 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF77AQMEXZKYWEU5SSGDOETV6XDL7ANCNFSM6AAAAAAQN3JVKU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
GitHub release notes: https://github.com/nextstrain/auspice/releases/tag/v2.38.0
Describe your pull request here
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
@BiocondaBot please add labelcommand.@bioconda/corein 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 labelplease review & mergelabel.@BiocondaBot please fetch artifactsYou can use this to test packages locally.
For members of the Bioconda project, the following command is also available:
@BiocondaBot please mergeSomeone 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>.