Hi, I’m trying to install v3.4.3 to python 3.10.0 on Debian, and getting a failure with:Download The FreeType Project from SourceForge.net ’, ‘https://download.savannah.gnu.org/releases/freetype/freetype-2.6.1.tar.gz ’]
Problem is, I don’t see either of those downloads.
Does this need updating ? Or is there another solution?
It should be attempting to download from SourceForge first, but sometimes that fails. It should be fine to download from either.
The Savannah downloads were moved and there is a PR in to fix it:
matplotlib:v3.5.x ← ryahern:v3.5.x
opened 02:31PM - 20 Oct 21 UTC
Versions prior to 2.7.1 cannot be accessed without indexing the 'freetype-old' f… older on the savannah site. Pypi installs for Matplotlib can request earlier versions (e.g. 2.6.1) and thus cause some builds to fail where sourceforge access is blocked.
## PR Summary
## PR Checklist
- [N/A] Has pytest style unit tests (and `pytest` passes).
- [N/A] Is [Flake 8](https://flake8.pycqa.org/en/latest/) compliant (run `flake8` on changed files to check).
- [N/A] New features are documented, with examples if plot related.
- [N/A] Documentation is sphinx and numpydoc compliant (the docs should [build](https://matplotlib.org/devel/documenting_mpl.html#building-the-docs) without error).
- [N/A] Conforms to Matplotlib style conventions (install `flake8-docstrings` and run `flake8 --docstring-convention=all`).
- [N/A] New features have an entry in `doc/users/next_whats_new/` (follow instructions in README.rst there).
- [N/A] API changes documented in `doc/api/next_api_changes/` (follow instructions in README.rst there).
<!--
Thank you so much for your PR! To help us review your contribution, please
consider the following points:
- A development guide is available at https://matplotlib.org/devdocs/devel/index.html.
- Help with git and github is available at
https://matplotlib.org/devel/gitwash/development_workflow.html.
- Do not create the PR out of master, but out of a separate branch.
- The PR title should summarize the changes, for example "Raise ValueError on
non-numeric input to set_xlim". Avoid non-descriptive titles such as
"Addresses issue #8576".
- The summary should provide at least 1-2 sentences describing the pull request
in detail (Why is this change required? What problem does it solve?) and
link to any relevant issues.
- If you are contributing fixes to docstrings, please pay attention to
http://matplotlib.org/devel/documenting_mpl.html#formatting. In particular,
note the difference between using single backquotes, double backquotes, and
asterisks in the markup.
We understand that PRs can sometimes be overwhelming, especially as the
reviews start coming in. Please let us know if the reviews are unclear or
the recommended next step seems overly demanding, if you would like help in
addressing a reviewer's comments, or if you have been waiting too long to hear
back on your PR.
-->