Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.java > #12888

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

From Emmanuel Bourg <ebourg@apache.org>
Newsgroups linux.debian.maint.java
Subject Re: New version of maven-resolver causes failures in autopkgtests and builds
Date 2025-01-16 17:20 +0100
Message-ID <K5AL8-9olh-7@gated-at.bofh.it> (permalink)
References <K5AL8-9olh-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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:

  ClassNotFoundException: 
org.eclipse.aether.named.providers.NoopNamedLockFactory

This class is in /usr/share/java/maven-resolver-named-locks.jar, which 
is a new jar in maven-resolver. So it's probably missing from a 
classpath somewhere.

Emmanuel Bourg


On 12/01/2025 21:16, Pierre Gruet wrote:
> Hi Emmanuel, and everyone,
> 
> I noticed that the new upstream version of maven-resolver, uploaded to 
> sid 27 days ago, failds to migrate because of two failing autopkgtests 
> in rdeps [0]. Also it is the root of #1091067 in scala, which would 
> cause its autoremoval in a few weeks.
> 
> Do you have any guess about the error messages that have been raised in 
> the various logs since the new maven-resolver got uploaded?
> 
> Thanks a lot for your help,
> 

Back to linux.debian.maint.java | Previous | NextNext in thread | Find similar


Thread

Re: New version of maven-resolver causes failures in autopkgtests and  builds Emmanuel Bourg <ebourg@apache.org> - 2025-01-16 17:20 +0100
  Re: New version of maven-resolver causes failures in autopkgtests and  builds Jérôme Charaoui <jerome@riseup.net> - 2025-01-16 17:30 +0100

csiph-web