python-spams gets incorrect PR updates

[jakirkham]

We have had a few update PRs at python-spams that have been completely incorrect. For example they show major version bumps (with minor and patch release bumps included) that have not happened. Not entirely sure why this is, but am raising it here.

xref: conda-forge/python-spams-feedstock#27
xref: conda-forge/python-spams-feedstock#28
xref: conda-forge/python-spams-feedstock#38

[CJ-Wright]

Hmm that is odd, maybe this is one of those places where it will respond affirmatively to any version number we ask for?

[jakirkham]

Maybe. Though how do we decide to request something like 4.1.2 instead of say 4.0.0?

[CJ-Wright]

I think the code for that is here: https://github.com/regro/cf-scripts/blob/master/conda_forge_tick/update_upstream_versions.py#L32

My understanding of this is that we keep asking for version numbers until we either hit a null or have asked for 10 things.

[jakirkham]

Would it be possible to simply remove python-spams from the auto-tick bot? It seems to be getting this wrong more often than right unfortunately.

ref: conda-forge/python-spams-feedstock#40
ref: conda-forge/python-spams-feedstock#41
ref: conda-forge/python-spams-feedstock#42
ref: conda-forge/python-spams-feedstock#43
ref: conda-forge/python-spams-feedstock#44
ref: conda-forge/python-spams-feedstock#45
ref: conda-forge/python-spams-feedstock#46
ref: conda-forge/python-spams-feedstock#47

[scopatz]

There was talk of being able to have packages blacklist themselves. I am not sure we ever implemented it, though

[jakirkham]

Do you know where that discussion was?

[scopatz]

It was just between @CJ-Wright and myself. I don't think we wrote anything semi-formal down