Clojurians Log v2

Hi, I have published a library in Clojar (https://clojars.org/org.graphqlize/graphqlize) 12 hours ago but when I try to refer it via deps I am getting the following error

Error building classpath. Could not find artifact org.graphqlize:graphlize:jar:0.1.0-alpha1 in central (<https://repo1.maven.org/maven2/>)

may be the following will be of some help. iiuc, the reason clojars gets consulted via clj is usually(?) because there is some deps.edn file that has a section like:

:mvn/repos {
    "central" {:url "<https://repo1.maven.org/maven2/>"}
    "clojars" {:url "<https://repo.clojars.org/>"}
  }

Thanks @sogaiu. But it didn’t help. I even put :mvn/repos in deps file but still it didn’t work

Oops. It was a typo. Renamed graphlize to graphqlize and it got fixed

is clojars down? or is it just me?

@darwin It looks like it should be back up now - it may have had an OOM and restarted

@tcrawley thanks, it seems to be up now, but my release seems to be borked, the problem is that it accepted incomplete and I cannot re-deploy, https://clojars.org/binaryage/dirac

Failed to deploy metadata: Could not transfer metadata binaryage:dirac/maven-metadata.xml from/to clojars (https://clojars.org/repo/): Access denied to: https://clojars.org/repo/binaryage/dirac/maven-metadata.xml, ReasonPhrase: Forbidden - redeploying non-snapshots is not allowed (see https://git.io/v1IAs).

previously the deploy failed with multiple “Could not transfer artifact binaryage:dirac:pom:1.5.4 from/to clojars (https://clojars.org/repo/): Read timed out”

used lein for that

I see 1.5.4 at https://repo.clojars.org/binaryage/dirac/1.5.4/ and 1.5.4 mentioned in https://repo.clojars.org/binaryage/dirac/maven-metadata.xml. so it may have completed correctly. Can you paste the full log you got on the failed deploy?

the dependencies definitely don’t look ok (but it might be my mistake I tinkered with them for 1.5.4 release)

here is the pom.xml which should be associated with that release: https://gist.github.com/darwin/ada7a7199dc9c67b80cbd2aca01b2682

should I wait for some kind of removal/fix of 1.5.4 or should I go ahead and mark 1.5.4 as broken and release 1.5.5 instead?

Sorry, in a meeting. The quickest fix would be to release 1.5.5 - I won't have time to look in to how to fix 1.5.4 in the next 8 hours or so at least.

ok, don’t worry about it, I will simply release a new one, only few people use this anyways

thanks

My pleasure! Sorry for the trouble.