Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Emmanuel Bourg Newsgroups: linux.debian.maint.java Subject: Re: New version of maven-resolver causes failures in autopkgtests and builds Date: Thu, 16 Jan 2025 17:20:02 +0100 Message-ID: References: X-Original-To: Pierre Gruet , Debian Java List X-Mailbox-Line: From debian-java-request@lists.debian.org Thu Jan 16 16:17:28 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-9.299 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 Authentication-Results: apache.org; auth=none MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/23596 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/a06f6ba6-e90f-4dcc-b845-555ed25d8993@apache.org Approved: robomod@news.nic.it Lines: 31 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 16 Jan 2025 17:17:07 +0100 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.java:12888 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, >