Fix conda environments after build was removed from conda-forge in favor of python-build

[rburing]

• Fixes Conda environment files are outdated after build was removed from conda-forge in favor of python-build #38550

📝 Checklist

• The title is concise and informative.
• The description explains in detail what this PR is about.
• I have linked a relevant issue or discussion.
• I have created tests covering the changes.
• I have updated the documentation and checked the documentation preview.

⌛ Dependencies

None.

[rburing]

All the tests passing the Setup Conda environment step (in contrast with other recent PRs) shows that the change works.

[mkoeppe]

The correct way to do this is to first update build/pkgs/python_build/distros/conda.txt (and then to run tox -e update_conda_lock)

[github-actions]

Documentation preview for this PR (built with commit b130474; changes) is ready! 🎉
This preview will update shortly after each push to this PR.

[rburing]

@mkoeppe Should all the unrelated changes resulting from that command be included here as well, or not?

[mkoeppe]

The scope of the PR is up to you, but a general update would certainly be welcome. In any case, it would be a good idea to run the full conda platform test by manually invoking the "CI Conda" GH Actions workflow in your fork.

[rburing]

@mkoeppe I'll give it a try. The workflow is running.

[rburing]

On second thought (build failures), I would prefer to keep it simple here.

[mkoeppe]

No problem, a whole bunch of updates are coming in anyway soon that will require us to update the conda-lock files again.

[mkoeppe]

In any case, it would be a good idea to run the full conda platform test by manually invoking the "CI Conda" GH Actions workflow in your fork.

When there's a successful run, please post a link

[rburing]

Here's the current run: https://github.com/rburing/sage/actions/runs/10529188299

I don't see what I can do in this PR to make it succeed, the errors all look unrelated.

[tobiasdiez]

Thanks, LGTM.

The version check fail already since 95428a1 by @mkoeppe. Would be awesome if you could fix it Matthias!

[mkoeppe]

It's a downstream problem.

[tobiasdiez]

It's a downstream problem.

Sure, an unnecessarily strict version constraint is a downstream issue 😄. Let me help you: #38556

[mkoeppe]

I'll explain it to you again: The flaw lies in the design of the conda setup, which insists on having suitable conda packages available - which is outside of the scope of the Sage project.

[mkoeppe]

What you need to do is work with downstream to package the current version of the package.