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

restricting Flint version should be conditional on installing Singular #37838

Closed
2 tasks done
dimpase opened this issue Apr 20, 2024 · 1 comment · Fixed by #37203
Closed
2 tasks done

restricting Flint version should be conditional on installing Singular #37838

dimpase opened this issue Apr 20, 2024 · 1 comment · Fixed by #37203

Comments

@dimpase
Copy link
Member

dimpase commented Apr 20, 2024

Steps To Reproduce

the current 10.4.beta3 does not allow external Singular, because the external flint is too new. #37495 is placing an unconditional upper bound on flint's version, for no good reason.

Users complain, rightly: https://groups.google.com/g/sage-devel/c/7RKSyswB2VA/m/T-xbNnW5BAAJ
Developers waste time, too.

Expected Behavior

External Singular should be allowed even even Flint's version is too new to build Sage's Singular, these are different things.

Actual Behavior

external Singular rejected due to Flint too new.

Additional Information

No response

Environment

- **OS**: Ubuntu 22
- **Sage Version**: 10.4.beta3

Checklist

  • I have searched the existing issues for a bug report that matches the one I want to file, without success.
  • I have read the documentation and troubleshoot guide
@dimpase dimpase added the t: bug label Apr 20, 2024
@dimpase
Copy link
Member Author

dimpase commented Apr 20, 2024

@vbraun vbraun closed this as completed in 4a6edc3 May 25, 2024
@mkoeppe mkoeppe added this to the sage-10.4 milestone May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants