Skip to content
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

Conda package has requirements/host dependency on conda-verify #43

Open
jakirkham opened this issue Feb 5, 2025 · 9 comments
Open

Conda package has requirements/host dependency on conda-verify #43

jakirkham opened this issue Feb 5, 2025 · 9 comments
Labels
question Further information is requested

Comments

@jakirkham
Copy link
Member

Noticed that the Conda recipe depends on conda-verify in requirements/host

Though not seeing other uses of it in the library

Is conda-verify needed by rapids-metadata? If so, how is it used?

@jakirkham jakirkham added the question Further information is requested label Feb 5, 2025
@jameslamb
Copy link
Member

I strongly suspect (though don't have evidence), that it was added to silence this warning from conda-build:

Importing conda-verify failed. Please be sure to test your packages. conda install conda-verify to make this message go away.

https://github.com/conda/conda-build/blob/e5b060efd18665b2810ecabac48a89e322943266/conda_build/build.py#L1931-L1934

@jakirkham
Copy link
Member Author

Thanks James! 🙏

That makes sense

In that case, we should drop this from the requirements and add it to the CI images

Started this in PR: rapidsai/ci-imgs#237

@jakirkham
Copy link
Member Author

Should add we already get this warning on CI:

WARNING: Importing conda-verify failed.  Please be sure to test your packages.  conda install conda-verify to make this message go away.

So having this in requirements/host isn't fixing that

@jameslamb
Copy link
Member

welp 🙃

Then either there's some other reason we added that that I don't remember (looks like there wasn't any commentary on it in #8), or it's just not working as intended anyway and we can safely remove it.

@jakirkham
Copy link
Member Author

It seems this pattern shows up in other places. It would be good to get more clarity on its usage elsewhere

@KyleFromNVIDIA
Copy link
Contributor

I honestly don't remember even adding the conda-verify dependency. It's likely that I cargo-culted it from elsewhere :)

@KyleFromNVIDIA
Copy link
Contributor

Looks like it was added in a076a31, which indicates that it was modeled after https://github.com/rapidsai/rapids-build-backend.

@vyasr
Copy link

vyasr commented Feb 8, 2025

I added it to rapids-build-backend in hopes of silencing the warning, and when it didn't work I guess I just forgot to remove it. I'd have liked to have figured out how to fix the warning, but at this stage it's probably a moot point since we're rewriting all our recipes to use rattler anyway. I say drop the dependency and move on, it'll be obsoleted by the migration even if we could fix it.

@jakirkham
Copy link
Member Author

Thanks all! 🙏

Agree we can remove it then

Have raised this in issue: rapidsai/build-planning#150

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants