This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-13
Channels
- # announcements (1)
- # babashka (12)
- # beginners (10)
- # biff (9)
- # calva (2)
- # cherry (21)
- # cider (14)
- # clj-commons (76)
- # clj-kondo (8)
- # clj-on-windows (34)
- # cljs-dev (5)
- # clojure (48)
- # clojure-austin (7)
- # clojure-europe (97)
- # clojure-nl (1)
- # clojure-norway (14)
- # clojure-uk (22)
- # clojurescript (137)
- # conjure (33)
- # cursive (4)
- # datalevin (1)
- # deps-new (4)
- # devcards (2)
- # duct (3)
- # events (1)
- # fulcro (12)
- # graphql (9)
- # hyperfiddle (16)
- # jobs (8)
- # kaocha (1)
- # leiningen (6)
- # lsp (39)
- # malli (38)
- # membrane (20)
- # nbb (68)
- # observability (7)
- # off-topic (49)
- # pathom (11)
- # polylith (8)
- # portal (22)
- # re-frame (6)
- # releases (1)
- # remote-jobs (2)
- # shadow-cljs (24)
- # spacemacs (2)
- # squint (6)
- # xtdb (7)
I https://github.com/clojure/tools.deps.alpha/wiki/clj-on-Windows#install but I get an error for any deps that use :git/url
and :git/sha
. I also tried with https://github.com/borkdude/deps.cljhttps://github.com/borkdude/deps.clj but I get the same error.
Error building classpath. Commit not found for babashka/babashka.core in repo at 52a6037bd4b632bffffb04394fb4efd0cdab6b1e
or
Error building classpath. Commit not found for com.taoensso/timbre in repo at 4223bac204669d9a98bf8b6db17f57d5f3e206e2
What can I do to debug this?if you set the system property GITLIBS_DEBUG=true you'll see the exact git commands being run
Thank you!
PS C:\Users\richie\clerk-debug> clojure
git --git-dir C:\Users\richie\.gitlibs\_repos\https\\babashka\babashka.core rev-parse 52a6037bd4b632bffffb04394fb4efd0cdab6b1e^{commit}
fatal: ambiguous argument '52a6037bd4b632bffffb04394fb4efd0cdab6b1e^commit': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
git --git-dir C:\Users\richie\.gitlibs\_repos\https\\babashka\babashka.core fetch --quiet --all --tags --prune
git --git-dir C:\Users\richie\.gitlibs\_repos\https\\babashka\babashka.core rev-parse 52a6037bd4b632bffffb04394fb4efd0cdab6b1e^{commit}
fatal: ambiguous argument '52a6037bd4b632bffffb04394fb4efd0cdab6b1e^commit': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Error building classpath. Commit not found for babashka/babashka.core in repo at 52a6037bd4b632bffffb04394fb4efd0cdab6b1e
Hmm...what version did you install?
and what version of git do you have?
It looks like it's the git from msys2.
PS C:\Users\richie\clerk-debug> whereis git
git: /usr/bin/git.exe /usr/share/git /usr/share/man/man1/git.1.gz
Idk if that's an issue. I can try installing git another way.nah, that should be fine I think
It looks like 52a6037bd4b632bffffb04394fb4efd0cdab6b1e^{commit}
got turned into 52a6037bd4b632bffffb04394fb4efd0cdab6b1e^commit
and that's not valid...
do you have the git coord handy?
oh, yeah that's definitely it - I should have noticed that
babashka/babashka.core
{:git/url "",
:git/sha "52a6037bd4b632bffffb04394fb4efd0cdab6b1e"}
so probably a quoting issue in tools.gitlibs
https://stackoverflow.com/questions/51625659/how-to-escape-curly-braces-u-of-upstream-in-git-alias-git-bash-on-windows seems like this same issue
the one comment on the answer there indicates some fix in git (not sure if those version numbers relate to yours)
From the comments:
> After update to git version 2.18.0.windows.1
I discovered they fixed the issue, so we don't need escaping any more
yeah that one
what shell are you using?
Although, I have the same problem on msys2 with GITLIBS_DEBUG=true powershell -command clojure
Yay, thanks. I installed git for windows 2.37.3.windows.1 and put it on my path. That fixed it.
might help to run one outside clj and see what you get
I will say that neither of those commits seem to exist in those repos on github though so maybe those errors are correct
oh wait, they do nvm, was looking at the wrong results