Fork me on GitHub
#clojars
<
2020-06-04
>
pithyless17:06:29

Any ideas why this may be happening?

❯ clj -Sforce -Sdeps '{:deps {meander/epsilon {:mvn/version "0.0.421"}}}'
Error building classpath. Could not transfer artifact meander:epsilon:jar:0.0.421 from/to clojars (): Range Not Satisfiable (416)
I can fetch earlier versions:
❯ clj -Sforce -Sdeps '{:deps {meander/epsilon {:mvn/version "0.0.411"}}}'
Downloading: meander/epsilon/0.0.411/epsilon-0.0.411.pom from clojars
As far as I can tell, the version does exist and others can download it: https://clojars.org/meander/epsilon. I'm based out of Europe; any chance some cache or cdn is stale?

tcrawley17:06:17

I'll try to purge it from the CDN and see if that helps, one sec

tcrawley17:06:40

@pithyless I purged the jar and pom, can you try again?

tcrawley17:06:43

Is that the full output?

Alex Miller (Clojure team)17:06:25

you might need to rm -rf ~/.m2/repository/meander/epsilon - there is some repo metadata that gets cached

tcrawley17:06:53

Thanks @alexmiller! If that doesn't work, I can purge the signatures/checksums as well in case the issue is with one of them

pithyless17:06:06

That fixed it. Thanks @alexmiller and @tcrawley for the fast response!

tcrawley17:06:14

My pleasure!

pithyless17:06:48

"Have you tried turning it off and on again?" Clojars is such a solid and stable silent partner in everyday development, I never even considered it might be a caching issue until I ruled everything else out. 🙂