-
Notifications
You must be signed in to change notification settings - Fork 14
Dulwich fails when there's no GCC #73
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
Comments
Looks like dulwich broke wheel build again 🙁 jelmer/dulwich#968 Thanks @dtrifiro for a quick fix. Looks like we need to set an upper bound on dulwich in scmrepo for now and think about how we can help dulwich releases not break so often. |
For the record: let's put an upper bound on dulwich and make sure when we test scmrepo we install using --bin-only(or whatever that pip flag is called) to make sure that all wheels are available. That will also help us catch such problems during dependabot's PRs for bumbing dulwich version. |
I am against putting any upper bound. This is a packaging issue, and these mistakes/bugs happen, which will automatically get fixed with time. Pinning the dependencies will make it painful for users if other packages also depend in dulwich. |
Basically, this issue is back again in DVC: iterative/dvc#2010
The text was updated successfully, but these errors were encountered: