clojars

vemv 2023-07-04T21:18:23.239999Z

It seems that I'm getting a similar issue:

Failed to deploy metadata: Could not transfer metadata mx.cider:enrich-classpath/maven-metadata.xml from/to clojars (): Access denied to: 

2023-07-05T09:32:14.944079Z

My pleasure!

vemv 2023-07-04T21:19:57.201119Z

The same deploy script succeeded 4 days ago, and I can access https://repo.clojars.org/mx/cider/enrich-classpath/maven-metadata.xml from any browser Retrying CI didn't work

2023-07-04T22:36:56.375999Z

What version are you trying to deploy? I'm seeing edeploying non-snapshots is not allowed. See in the logs for attempts to deploy 1.11.0, which shows as deployed here: https://clojars.org/mx.cider/enrich-classpath

vemv 2023-07-04T22:42:56.058759Z

The artifact is mx.cider/lein-enrich-classpath (note the lein part). It's a new project - https://clojars.org/mx.cider/lein-enrich-classpath returns 404 I tried a second CI build which might explain the failure you point out. However: • That doesn't explain the original failure • less importantly, I don't see redeploying non-snapshots is not allowed. in either build These are the logs of the first build that failed: https://gist.githubusercontent.com/vemv/33efa4d6bc3d8b6e3db5a1e4126e7a55/raw/8dcd1beedf1c22d9878c63904191949036c3a73e/gistfile1.txt

vemv 2023-07-04T22:50:12.973949Z

I should clarify, the same CI build intends to build three artifacts: mx.cider/enrich-classpath mx.cider/tools.deps.enrich-classpath mx.cider/lein-enrich-classpath This has worked well for a long time (even 5 days ago)

vemv 2023-07-04T22:59:00.237199Z

I think I debugged it. In the logs it says /bin/sh: 1: cd: can't cd to ../lein-plugin which causes the re-deploy attempt in the root dir. The failure due to redeployment appears to be hidden behind a generic (): Access denied to: message - perhaps that can be improved? Can try to repro tomorrow if it's hard for you

2023-07-04T23:42:03.219989Z

I wish I could improve error messages, but we don't have much recourse there, since it's all handled by aether on the client side. Our only recourse is to change the reason phrase on responses. However, there was a period where aether removed showing of those status messages for a version. So if you are using tooling that is using that version of aether, you won't see error responses. See https://github.com/clojars/clojars-web/issues/774 for more details.

2023-07-04T23:44:18.542189Z

What version of lein are you using? The message should show unless you are using lein 2.9.4 - 2.9.6.

vemv 2023-07-04T23:45:49.295369Z

2.9.5 :) mistery solved Will upgrade Thanks!