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

2025-01-23 Thread Paul Gevers
Hi, On 23-01-2025 09:26, Julien Plissonneau Duquène wrote: These issues are currently being discussed on debian-java [1]. Would a britney hint or something be appropriate here? We believe that these reverse dependencies should not block these migrations. If RC bugs have been filed for all re

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

2025-01-23 Thread Julien Plissonneau Duquène
Hi Paul, These issues are currently being discussed on debian-java [1]. Would a britney hint or something be appropriate here? We believe that these reverse dependencies should not block these migrations. Cheers, [1]: https://lists.debian.org/debian-java/2025/01/msg00012.html -- Julien Pli

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: 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

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

2025-01-12 Thread Pierre Gruet
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 g