2024-09-20 clojars | Clojure Slack Archive

clojars

hlship 2024-09-20T18:49:21.858829Z

I’m having a problem deploying com.walmartlabs/lacinia-pedestal 1.3 to clojars:

Deploying com.walmartlabs/lacinia-pedestal-1.3 to repository clojars as hlship
Sending com/walmartlabs/lacinia-pedestal/1.3/lacinia-pedestal-1.3.pom (2k)
    to 
Sending com/walmartlabs/lacinia-pedestal/1.3/lacinia-pedestal-1.3.jar (30k)
    to 
Sending com/walmartlabs/lacinia-pedestal/1.3/lacinia-pedestal-1.3.pom.asc (1k)
    to 
Sending com/walmartlabs/lacinia-pedestal/1.3/lacinia-pedestal-1.3.jar.asc (1k)
    to 
Retrieving com/walmartlabs/lacinia-pedestal/maven-metadata.xml (2k)
    from 
Sending com/walmartlabs/lacinia-pedestal/maven-metadata.xml (2k)
    to 
Could not transfer metadata com.walmartlabs:lacinia-pedestal/maven-metadata.xml from/to clojars (): Authorization failed for  403 Forbidden
Execution error (AuthorizationException) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon/put (AbstractHttpClientWagon.java:806).
Authorization failed for  403 Forbidden

I’m not sure what’s changed since I last did a deploy. I suspect that Clojars is requiring more authentication for the com.walmartlabs domain? As I don’t work there anymore, that could be a challenge.

2024-09-21T11:48:36.756759Z

Sorry for the trouble here! This has been a pretty frustrating issue. This works in tests, and works for some period of time after the production process is restarted, but then at some point the status message sending just stops working until the next process restart. None of that helps y'all; I'm just venting. I'll take another crack at figuring this out.

mkvlr 2024-09-20T18:53:21.968049Z

could be a missing license file https://clojureverse.org/t/ann-clojars-now-requires-a-license-in-the-pom-for-new-projects-or-projects-that-already-specify-a-license/10347

seancorfield 2024-09-20T19:47:46.777919Z

It looks like Howard's build-tools lib handles that (ASL is the license for Lacinia).

seancorfield 2024-09-20T19:48:31.302119Z

According to that CV post, you'd get "Forbidden - the POM file does not include a license" if the license info is missing.

hlship 2024-09-20T19:48:48.776319Z

This is the annoying kind of problem that you only hit every few months, and forget what you did to fix it last time.

seancorfield 2024-09-20T19:49:16.006639Z

Do you have the CLOJARS_* env vars setup correctly? Username and deploy token.

hlship 2024-09-20T19:50:59.192749Z

I just looked at the generated POM and no <licences>, so that's probably the root problem. I'll go pursue that, thanks!

👍 1

mkvlr 2024-09-20T19:51:16.709669Z

when I ran into the license issue I didn’t get the specific error message

seancorfield 2024-09-20T19:51:35.405779Z

Really? That's... unfortunate (and I'd consider that a bug).

mkvlr 2024-09-20T19:53:55.249179Z

yes, I thought I had posted it here but can’t find it now, will dig some more.

seancorfield 2024-09-20T19:54:35.131079Z

https://github.com/clojars/clojars-web/issues/889

seancorfield 2024-09-20T19:54:44.253379Z

(I just created that)

🙏 1

2024-09-22T12:48:00.231359Z

I've rewritten the status-message handling code to be more straightforward, but slightly hacky. It is working currently in production, and I have more confidence in this implementation: https://github.com/clojars/clojars-web/pull/890

Clojurians Log v2

clojars