Hi Andreas, On 09/09/2021 14:21, Andreas Tille wrote:
Hi Pierre, thanks a lot for your educated answer. On Thu, Sep 09, 2021 at 12:48:33PM +0200, Pierre Gruet wrote:Any hint how to fix this?Well, /maybe/ we could patch this last pilon version to use Scala 2.11 with it... but I see there were quite a lot of changed in pilon seemingly related to newer Scala [3,4], so I am unsure we would succeed.Regarding pilon we are not in a hurry. Its just one of the packages with broken watch file I'm touching step by step.
I have just uploaded latest upstream version of pilon to unstable, together with a fix for the scala issues showing up. Normally we would have had to update scala from 2.11 to 2.13, but here the fix was very short to write.
Sorry, I mixed up the changelog entries a bit because I forgot to pull from Salsa before working on the package, but now on Salsa everything is right.
Anyway, for sure the right thing would be to upgrade Scala.Yep. We need this anyway.
Right!This email is the opportunity to ask you a question: I saw you were the initial sponsor of sbt, the Scala Build Tool. The source package was accepted with a lot of embedded jars inside. Do you remember if you had some discussion with FTP Masters about it before they accepted the package? Arguably this is costly to avoid in such a setting, where we need Scala dependencies to build a tool that builds Scala programs...
I am interested in this, because I regularly give some time to improving the state of the Scala ecosystem in Debian, and sbt if central in it.
This is one thing I would like to do and discuss with the Java team, will try to do it quite soon...This would be cool. Please do not waste time with patching pilon meanwhile. Kind regards Andreas.
Warm regards, -- Pierre