Clojurians Log v2

seems an authorization issue

Is that the full output? From looking at the logs, it looks like you trying to deploy a version that clojars thinks already exists, and that should give you a message like redeploying non-snapshots is not allowed (see ) , but it easily gets lost in the other noise from the client deploy machinery

@tcrawley Here’s the complete output:

lein do clean, deploy clojars
No credentials found for clojars
See `lein help deploying` for how to configure credentials to avoid prompts.
Username: kumarshantanu
Password:
Created /Users/shantanu/projects/oss/bract/bract.ring/target/bract.ring-0.6.2-0.2.0-beta1.jar
Wrote /Users/shantanu/projects/oss/bract/bract.ring/pom.xml
Need to sign 2 files with GPG
[1/2] Signing /Users/shantanu/projects/oss/bract/bract.ring/target/bract.ring-0.6.2-0.2.0-beta1.jar with GPG
gpg: using "E13B061A08D78F261752B1A90E6D91D347AB1843" as default secret key for signing
[2/2] Signing /Users/shantanu/projects/oss/bract/bract.ring/pom.xml with GPG
gpg: using "E13B061A08D78F261752B1A90E6D91D347AB1843" as default secret key for signing
Sending bract/bract.ring/0.6.2-0.2.0-beta1/bract.ring-0.6.2-0.2.0-beta1.jar (24k)
    to 
Sending bract/bract.ring/0.6.2-0.2.0-beta1/bract.ring-0.6.2-0.2.0-beta1.pom (4k)
    to 
Sending bract/bract.ring/0.6.2-0.2.0-beta1/bract.ring-0.6.2-0.2.0-beta1.jar.asc (1k)
    to 
Sending bract/bract.ring/0.6.2-0.2.0-beta1/bract.ring-0.6.2-0.2.0-beta1.pom.asc (1k)
    to 
Retrieving bract/bract.ring/maven-metadata.xml (1k)from 
Sending bract/bract.ring/maven-metadata.xml (1k)to 
Could not transfer metadata bract:bract.ring/maven-metadata.xml from/to clojars (): Access denied to: 
Failed to deploy metadata: Could not transfer metadata bract:bract.ring/maven-metadata.xml from/to clojars (): Access denied to: 

This particular (non-SNAPSHOT) version is not on Clojars.

Was that from the first deploy attempt or the subsequent ones? I can see the first deploy mostly succeeded, but then aborted due to a 500 error from S3. From looking at the code, it looks like that would leave it in a state where clojars thinks it is deployed, but it really isn't. Let me see what I can do.

The first deploy failed, then I retried few times that also failed.

That agrees with what I see in the logs. I would have expected all deploys after the first to tell you that you can't redeploy a non-snapshot. If it didn't show that, that's a bug.

I made a change on the server, can you try again now?

@tcrawley Succeeded this time, thanks!

Great! My pleasure!

And just to be clear - you didn't see the "redeploying non-snapshots is not allowed" message on any of the deploy attempts?

No, I didn’t.

Thanks for confirming, I'll create an issue for that and investigate it further.