Closed aneeshnaik closed 2 months ago
Hi. Can you reproduce this issue locally?
No, the docs build if I try locally with the same conda environment.
Solution:
- python: "mambaforge-22.9"
+ python: "mambaforge-23.11"
I did some searching on the root error message which wasn't included in the issue description but you can see it in the build log that's linked:
critical libmamba Pathname can't be converted from UTF-8 to current locale.
Preparing transaction: ...working... done
Verifying transaction: ...working... failed
and came across https://github.com/conda-forge/python-libarchive-c-feedstock/issues/35#issuecomment-1623133587. This is a known bug in mamba versions <1.4.7. The mambaforge version used here, 22.9, bundles mamba 1.1.0. The next available mambaforge version, 23.11, bundles mamba 1.5.5.
@victorlin thanks for posting the solution here! 🙏🏼
@aneeshnaik can you try using mambaforge-23.11
and let us know if it solves the issue?
Just tested building the docs with mambaforge-23.11
and everything builds without error, even if I remove the sphinx version spec so that it uses the latest sphinx version (7.3.7).
In summary, @victorlin's solution works --- thank you for looking into this!
Great! Thanks for replying here. I'm going to close this issue then, since it's not an issue on Read the Docs and there isn't anything actionable from our side.
Details
My docs are built using mambaforge. If I list
sphinx
as a dependency (without a version number), then mambaforge tries to install the latest version (7.3.7), which leads to a long chain of error messages like below, and the build fails.However, if I list
sphinx=7.2
then the build works as expected.Here is my .readthedocs.yaml file:
And here is the version of the environment.yml file that does not work:
Here is an example of a failed build using this environment.yml file.