search

conda-forge / pymc-feedstock

A conda-smithy repository for pymc.
BSD 3-Clause "New" or "Revised" License
1 stars 12 forks source link

pymc v3.11.4 #23

Closed regro-cf-autotick-bot closed 2 years ago

regro-cf-autotick-bot commented 3 years ago

It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version. Checklist before merging this PR:
    • [ ] Dependencies have been updated if changed: see upstream
    • [ ] Tests have passed
    • [ ] Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1270450887, please use this URL for debugging

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows a discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

Packages found by inspection but not in the meta.yaml:

conda-forge-linter commented 3 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

twiecki commented 3 years ago

DO NOT MERGE, PLEASE CLOSE.

ocefpaf commented 3 years ago

DO NOT MERGE, PLEASE CLOSE.

We are probably not going to merge a PR that is failing :smile:

But it would be nice to know why the all CAPS message. Some context for future maintainers passing by would be nice.

twiecki commented 3 years ago

@ocefpaf Just didn't want to mess up this feedstock. We're in the process of renaming pymc3 to pymc, and this was triggered during that rename, but the feedstock is not adjusted.

ocefpaf commented 3 years ago

@ocefpaf Just didn't want to mess up this feedstock. We're in the process of renaming pymc3 to pymc, and this was triggered during that rename, but the feedstock is not adjusted.

Note that we don't need to change the name of the feedstock per-se, just the package in the meta.yaml. See the proj pkg that was named proj.4 a while back: https://github.com/conda-forge/proj.4-feedstock/blob/master/recipe/meta.yaml#L4 However, if you want, we can archive this and re-submit a new package with the new name to staged-recipes.

twiecki commented 3 years ago

Ideally we'd rename this repo to feedstock for pymc2.

ocefpaf commented 3 years ago

Ideally we'd rename this repo to feedstock for pymc2.

Renaming the repo will break a lot of our automation. We should archive and re-submit the packages with the new names then.

twiecki commented 3 years ago

@ocefpaf We can go ahead and archive this then and create a new one where we start with a copy of the pymc3 feedstock. Is that something you can help with?

ocefpaf commented 3 years ago

@ocefpaf We can go ahead and archive this then and create a new one where we start with a copy of the pymc3 feedstock. Is that something you can help with?

Sure. I'd like to have an OK from @fonnesbeck who is also listed here as a maintainer. Then I can archive it.

Regarding re-submitting to stage-recipes, I can help you if you send a PR or do that myself. I confess I prefer the former b/c my plate is quite full lately and I'm working "part time" only.

fonnesbeck commented 3 years ago

@ocefpaf please go ahead. Thanks!

regro-cf-autotick-bot commented 2 years ago

I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by https://github.com/regro/autotick-bot/actions/runs/1587530897