Re: jruby FTBFS with openjdk-9
Hi, On Tue, 26 Feb 2019 at 15:20, Emmanuel Bourg wrote: > Le 26/02/2019 à 15:05, Markus Koschany a écrit : > > The FTBFS bug got fixed yesterday. I should complain more often. Andrej > > uploaded version 9.1.17 to unstable. This is not the latest one but I > > guess better than nothing? The original bug has not been closed yet. > > Andrej, can we close it now and Debian bug #917702 too? > > Any hope to package JRuby 9.2.x? AFAIK it supports Java 11 better. I may look into it when I have time, but at the moment it’s lower on my todo list. We’re fighting with a lot of Java-related build failures in Apertis, so I’m basically doing what’s most important to unblock our further work. -- Cheers, Andrej
Re: [kotlin] Call for Help!
On Thu, 16 Jul 2020, at 14:04, Samyak Jain wrote: > Hi, > > This is a call for help for the kotlin package. > I have added a couple of sub-modules which was required to make kotlin > build for itself. The prime concern that we were facing was that it > wasn't able to build *kotlin-Gradle-plugin* and* > kotlin-sam-with-receiver* which is rectified now, as I was able to > compile it's submodules primarily the compiler-embeddable. > > But, while on the execution of the :kotlin-compiler-embeddable Task, it > fails to execute the :kotlin-compiler-embeddable:install task. > > Here's the full paste: https://paste.debian.net/1156641/ I think you missed this part: Caused by: org.gradle.api.artifacts.UnknownConfigurationException: Configuration with name 'runtimeJar' not found. at org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.createNotFoundException(DefaultConfigurationContainer.java:140) at org.gradle.api.internal.DefaultNamedDomainObjectCollection.getByName(DefaultNamedDomainObjectCollection.java:229) at org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.getByName(DefaultConfigurationContainer.java:130) at org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.getByName(DefaultConfigurationContainer.java:50) at org.gradle.api.publication.maven.internal.pom.DefaultPomDependenciesConverter.getTargetConfiguration(DefaultPomDependenciesConverter.java:122) at org.gradle.api.publication.maven.internal.pom.DefaultPomDependenciesConverter.addMavenDependencies(DefaultPomDependenciesConverter.java:134) at org.gradle.api.publication.maven.internal.pom.DefaultPomDependenciesConverter.addFromDependencyDescriptor(DefaultPomDependenciesConverter.java:113) at org.gradle.api.publication.maven.internal.pom.DefaultPomDependenciesConverter.convert(DefaultPomDependenciesConverter.java:55) at org.gradle.api.publication.maven.internal.pom.DefaultMavenPom.getGeneratedDependencies(DefaultMavenPom.java:170) at org.gradle.api.publication.maven.internal.pom.DefaultMavenPom.getEffectivePom(DefaultMavenPom.java:176) at org.gradle.api.publication.maven.internal.pom.DefaultMavenPom.writeTo(DefaultMavenPom.java:193) at org.gradle.api.publication.maven.internal.pom.DefaultMavenPom$2.execute(DefaultMavenPom.java:203) at org.gradle.api.publication.maven.internal.pom.DefaultMavenPom$2.execute(DefaultMavenPom.java:201) at org.gradle.internal.IoActions$TextFileWriterIoAction.execute(IoActions.java:145) ... 60 more -- Cheers, Andrej
Re: Bug#1004135: plantuml: please update to a newer upstream version
Hi, On Wed, 7 Feb 2024, at 00:51, Alejandro Rosso wrote: > Current version in Debian is close to be 4 years outdated and it seems > that updating it will fix some CVE bugs. You’re welcome to help packaging a newer upstream version or backporting the fixes :) -- Cheers, Andrej
