Closed mgrover1 closed 3 months ago
@tomvothecoder – I was able to reproduce this on an M2 Mac. Do you think we can drop the pandoc
dependency for xcdat-dev
(maybe we could have a separate maintainer
env for repo administration/documentation and xcdat-dev
could be purely for contributing to xcdat functionality)?
@tomvothecoder – I was able to reproduce this on an M2 Mac. Do you think we can drop the
pandoc
dependency forxcdat-dev
(maybe we could have a separatemaintainer
env for repo administration/documentation andxcdat-dev
could be purely for contributing to xcdat functionality)?
I was also able to reproduce this issue on my M2 Mac, but resolved it in #622 by dropping the pins for documentation dependencies. pandoc>=3.12
supports osx-arm64
. Can you check out this PR branch and try it out too?
We should keep pandoc
and other doc dependencies in the dev env so there is single env for dev, which is easier to use and maintain compared to multiple dev envs (e.g., one for code dev, one for doc).
This worked for me.
@pochedls Thanks for confirming. I merged PR #622 to fix this issue.
@mgrover1 Can you try to building the dev env on your M1 Mac using the latest main
dev env?
@tomvothecoder - this issue is resolved!! Thanks for the fix here!
What happened?
I tried creating the conda environment for this project (https://github.com/xCDAT/xcdat/blob/main/conda-env/dev.yml) on an M1 macbook (arm architecture) and ran into issues with the pandoc installation. This is also related to
What did you expect to happen? Are there are possible answers you came across?
I expected to be able to run
but ran into the following issue
Minimal Complete Verifiable Example (MVCE)
Relevant log output
Anything else we need to know?
It should be possible to build a development environment on a recent Mac machine.
Environment
Unable to do this here as the environment will not build.