-
-
Notifications
You must be signed in to change notification settings - Fork 405
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
.devcontainer/downstream-archlinux-latest
: Fix maxima
#36959
.devcontainer/downstream-archlinux-latest
: Fix maxima
#36959
Conversation
dff7996
to
966fb86
Compare
Documentation preview for this PR (built with commit 966fb86; changes) is ready! 🎉 |
This is for the case that a user works in vs code with Anyway I tried, and got
and did not even reach to the doc build stage... |
Apologies for neglecting to write a proper PR description, fixed now. Building Sage from source is not a goal in this container |
What I don't understand is this: "Removing the NoExtract directives before installing the package." Does installing the archlinux sage package fail because of the NoExtract directives? |
No, installation goes through, but it's broken at runtime. |
OK. This PR works well. The portability dev containers are very useful! |
Thanks! |
Dev container configurations
.devcontainer/downstream-*
give easy access to Sage as provided by downstream packagers (see https://doc.sagemath.org/html/en/developer/portability_testing.html#using-our-pre-built-docker-images-for-development-in-vs-code, bottom).Unfortunately maxima is defective when the archlinux sage package is installed in the official archlinux Docker container because of NoExtract directives that make the maxima help system inoperable.
Here we apply the same fix that we used in #36391 for the portability CI: Removing the NoExtract directives before installing the package.
📝 Checklist
⌛ Dependencies