conda-forge / git-annex-feedstock

A conda-smithy repository for git-annex.
BSD 3-Clause "New" or "Revised" License
0 stars 6 forks source link

Update git-annex builds to 10.20230126 version #153

Closed yarikoptic closed 1 year ago

yarikoptic commented 1 year ago

Closes #152

Checklist

for the standalone I figured it was the 10.20221213-ge5b6b7b5e which is 10.20230126~5 and I left its version to be as of the released one although indeed comes 5 commits before:

❯ git diff 10.20230126~5..10.20230126 --stat
 CHANGELOG                         |  4 ++--
 doc/install/Linux_standalone.mdwn |  3 +--
 doc/news/version_10.20220822.mdwn | 27 ---------------------------
 doc/news/version_10.20230126.mdwn | 27 +++++++++++++++++++++++++++
 git-annex.cabal                   |  6 +++---
 5 files changed, 33 insertions(+), 34 deletions(-)
conda-forge-webservices[bot] commented 1 year ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

yarikoptic commented 1 year ago

it doesn't get to build really, errors out on

Booting .
Booting libraries/time/
sh: /home/conda/feedstock_root/build_artifacts/git-annex_1675367681942/_build_env/bin/autoreconf: /home/conda/feedstock_root/build_artifacts/autoconf_1675331365585/_build_env/b: bad interpreter: No such file or directory
Booting libraries/terminfo/
sh: /home/conda/feedstock_root/build_artifacts/git-annex_1675367681942/_build_env/bin/autoreconf: /home/conda/feedstock_root/build_artifacts/autoconf_1675331365585/_build_env/b: bad interpreter: No such file or directory
Booting libraries/integer-gmp/

so something about haskell stack. ... just for the sake of it, let's

@conda-forge-admin, please rerender

yarikoptic commented 1 year ago

good, green -- let's proceed!

yarikoptic commented 1 year ago

Here it was green, but I don't see build still listed for alldep in https://anaconda.org/conda-forge/git-annex/files . I will need to check wherever the build logs are to see what happened.