Re: New version of maven-resolver causes failures in autopkgtests and builds

2025-01-16 Thread Emmanuel Bourg
Hi Pierre, That's unfortunate that two clojure packages with a near zero popcon block the transition of a core package of the Debian Java ecosystem. How can we avoid that and put the burden on updating the rdeps instead? Looking at the pomegranate-clojure failure, the error is: ClassNotFoun

Re: New version of maven-resolver causes failures in autopkgtests and builds

2025-01-16 Thread Jérôme Charaoui
Hello, We've discussed this bug on #debian-clojure recently. The package is actually being restructured and so is waiting on stuff currently in NEW. However, since I understand now that its blocking a transition, I can see if I can upload a quick fix today to unblock it. Thanks, -- Jérôme

Re: pomegranate-clojure: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1

2025-01-16 Thread Andreas Tille
Hi, I tried upstream version 1.2.24 but it fails as well. Sorry, I have no better idea how to fix this but I'm keeping Debian Java List in CC. Kind regards Andreas. -- https://fam-tille.de

JRuby FTBFS from missing Maven plugin

2025-01-16 Thread Jérôme Charaoui
Hello, I've been trying to figure out bug #1091127 [0] but I'm stumped: [ERROR] Plugin org.apache.maven.plugins:maven-assembly-plugin:3.7.1 or one of its dependencies could not be resolved There was no change to the source, so I believe this error might have been triggered by the Maven updat

Re: codenarc: new upstream version 3.5.0

2025-01-16 Thread Andreas Tille
Control: tags -1 help Thanks Hi, I injected the latest upstream version into Git. Unfortunately there are build errors as you can see in Salsa CI[1] Any help would be welcome Andreas. -- https://fam-tille.de