Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-10-07

Channels

#clojars
<
2022-10-07
>
hlship23:10:56

I'm in the middle of converting io.pedestal to use deps.end for its build and deploy; I'm having a couple of hiccups w.r.t. deployment. 

{:in io.pedestal.deploy/deploy-artifact,
 :line 90,
 :thread "nREPL-session-514d1213-b00b-4c82-a979-b3ae2ebd9fe1",
 :upload-artifacts
 {[:extension "jar" :classifier nil]
  "log/target/pedestal.log-0.5.11-SNAPSHOT.jar",
  [:extension "pom" :classifier nil]
  "target/pedestal.log-0.5.11-SNAPSHOT.pom",
  [:extension "jar.asc" :classifier nil]
  "log/target/pedestal.log-0.5.11-SNAPSHOT.jar.asc",
  [:extension "pom.asc" :classifier nil]
  "target/pedestal.log-0.5.11-SNAPSHOT.pom.asc"},
 :coords [io.pedestal/pedestal.log "0.5.11-SNAPSHOT"]}
Could not find metadata io.pedestal:pedestal.log:0.5.11-SNAPSHOT/maven-metadata.xml in clojars ()
Sending io/pedestal/pedestal.log/0.5.11-SNAPSHOT/pedestal.log-0.5.11-20221007.232659-1.jar (11k)
    to 
Sending io/pedestal/pedestal.log/0.5.11-SNAPSHOT/pedestal.log-0.5.11-20221007.232659-1.pom (2k)
    to 
Sending io/pedestal/pedestal.log/0.5.11-SNAPSHOT/pedestal.log-0.5.11-20221007.232659-1.jar.asc (1k)
    to 
Sending io/pedestal/pedestal.log/0.5.11-SNAPSHOT/pedestal.log-0.5.11-20221007.232659-1.pom.asc (1k)
    to 
Retrieving io/pedestal/pedestal.log/maven-metadata.xml (1k)
    from 
Sending io/pedestal/pedestal.log/0.5.11-SNAPSHOT/maven-metadata.xml (1k)
    to 
Sending io/pedestal/pedestal.log/maven-metadata.xml (1k)
    to 
Could not transfer metadata io.pedestal:pedestal.log/maven-metadata.xml from/to clojars (): Authorization failed for  403 Forbidden - redeploying non-snapshots is not allowed. See 
Execution error (AuthorizationException) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon/put (AbstractHttpClientWagon.java:806).
Authorization failed for  403 Forbidden - redeploying non-snapshots is not allowed. See
It may be because I previously uploaded a "0.5.11-snapshot-1" version?

phronmophobic23:10:52

> It may be because I previously uploaded a "0.5.11-snapshot-1" version? It doesn't say exactly what qualifies as a snapshot version, but I believe the version is required to end with "-SNAPSHOT" to qualify as a snapshot and allow reuploads https://github.com/clojars/clojars-web/wiki/About#why-cant-i-redeploy-a-non-snapshot-version

hlship23:10:21

Thanks; I read that and changed my version number to "0.5.11-SNAPSHOT", but something about the existing "0,5.11-snapshot-1" might be gumming up the works.

phronmophobic23:10:35

not really sure though

tcrawley13:10:03

Sorry you are having issues @U04VDKC4G! This is odd - you are definitely deploying a snapshot (@U7RJTCH6J is correct - a snapshot is a version that ends in -SNAPSHOT), and the client is treating it as such (you can see that by it uploading a timestamped version). The clojars code to give you the "redeploying non-snapshots is not allowed" is pretty simple, and short circuits if the version is a snapshot version, which is clearly is, so I'm not sure why that is failing in this case. I was able to deploy a snapshot of a test project just now. I'm going to check out pedestal and try deploying the snapshot to a test group. having a -snapshot-1 version should make no difference here.

tcrawley13:10:02

I checked out your branch from https://github.com/pedestal/pedestal/pull/723, but I don't know how to actually trigger a snapshot build & release.

tcrawley13:10:39

Oh! I think I see what it is, maybe. Digging a bit more to confirm; but it actually may be related to the -snapshot-1 release, indirectly. There may be a bug in how we find the tmp repo when finalizing a deploy, and it may be finding and using the tmp repo for the -snapshot-1 release at finalization time.

tcrawley13:10:46

Did you deploy -snapshot-1 and -SNAPSHOT from the same repl session? This bug should only trigger when a session cookie is shared between two different versions, which doesn't happen across command-line invocations (of lein at least). I still need to fix this, but I'm just trying to better understand how it could happen.

hlship19:10:59

I can look into this later. Yes, about the REPL session, most likely, I was keeping a session going while I experimented. There you go, global state f-s you again!

hlship15:10:50

Thanks again, I just re-ran this in my REPL and it worked. Thanks for you quick support!

tcrawley12:10:37

My pleasure!