Skip to content

Add missing v-bounds for packages depending on core and base #28230

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

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

jmid
Copy link
Contributor

@jmid jmid commented Jul 22, 2025

This fixes a bunch of base and core bounds missing a v:

  • in logical's base lower bound
  • in catt's base lower bound
  • in opine's base lower bound
  • in reason-standard's base lower bound
  • in tensorflow's base lower bound
  • in torch.0.2-0.4's base lower bound
  • in packstream's core lower bound
  • in bitgenerator's core_bench lower bound

@jmid
Copy link
Contributor Author

jmid commented Jul 22, 2025

  • torch.0.2 and 0.3 fail everywhere with linking errors. Considering this and that they were released ~7 years ago, perhaps they should just be archived? (CC @hannesm)
  • torch.0.4 fail some lower bounds - and seems to not compile with newer gccs
  • tensorflow.0.0.11 is failing a lower bounds check
  • opam-2.0 fails on packstream.0.1 with The actions to process have cyclic dependencies
  • opine, packstream, and reason-standard fail on Windows (heading for a timeout)

None of these were caused by adding the missing vs in bounds.
As such this should be good to go.

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

Successfully merging this pull request may close these issues.

1 participant