Re: RFS: gradle/3.1-1
Hi Emmanuel, libnative-platform-java is now built on all official architectures and most debian-ports ones [1]. I'll let the porters deal with the FTBFS on those architectures. I also fixed the FTBFS of bnd against Gradle 3.1 [2], and I also confirmed Gradle 3.1 is buildable with (Gradle 2.13) or (Gradle 3.1 + the fixed bnd). Cheers, Kai-Chung Yan [1]: https://buildd.debian.org/status/package.php?p=libnative-platform-java [2]: https://gitlab.com/seamlik/debianpkg_bnd/compare/master...gradle-3.1 2016-11-04 23:34 GMT+08:00 Emmanuel Bourg : > Le 4/11/2016 à 16:00, 殷啟聰 a écrit : > >> Gradle itself is also one of the reverse-build-dependencies, so of >> course I checked and it worked. > > Great, thanks for confirming. > > >> This is strange, even if gradle-debian-helper FTBFS with Gradle 3.1, >> it still works fine with Gradle 3.1 on all packages that I checked, >> including libspring-java. I am putting the transitional code in [1]. > > That's weird indeed, I would expect a NoClassDefFoundError at runtime. > I'd like to double check that before you upload Gradle 3.1. > > Emmanuel Bourg >
Re: Scala 2.10
# Adding debian-mentors Hi everyone, On Sat, 2016-11-05 at 16:06 -0600, Marko Dimjašević wrote: > BUILD FAILED > /build/scala-2.10.5/build.xml:59: The following error occurred while > executing this line: > /build/scala-2.10.5/build.xml:88: The following error occurred while > executing this line: > /build/scala-2.10.5/build.xml:218: Directory /nonexistent/.m2/repository > creation was not successful for an unknown reason > > Total time: 0 seconds > debian/rules:12: recipe for target 'override_dh_auto_build' failed > make[1]: *** [override_dh_auto_build] Error 1 > make[1]: Leaving directory '/build/scala-2.10.5' > debian/rules:9: recipe for target 'build' failed > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > I: copying local configuration > E: Failed autobuilding of package > I: unmounting dev/pts filesystem > I: unmounting run/shm filesystem > I: unmounting proc filesystem > I: unmounting sys filesystem > -> Cleaning COW directory > forking: rm -rf /var/cache/pbuilder/build/cow.17246 > > > > Any clue why this is happening? Can someone help me with this one? I'm eager to get as much of Scala software packaged for Debian, but I need your help with these baby steps. I'm a complete rookie when it comes to creating and building packages for Debian so I could use a hand here. If anyone from debian-mentors that is not on debian-java would like to help, but is missing my original message, you can find it here: https://lists.debian.org/debian-java/2016/11/msg00016.html -- Regards, Marko Dimjašević https://dimjasevic.net/marko PGP key ID: 1503F0AA Learn email self-defense! https://emailselfdefense.fsf.org signature.asc Description: This is a digitally signed message part
Re: Scala 2.10
On 11/11/2016 03:08 AM, Marko Dimjašević wrote: > # Adding debian-mentors >> /build/scala-2.10.5/build.xml:218: Directory /nonexistent/.m2/repository >> creation was not successful for an unknown reason pbuilder sets the home directory of the pbuilder user to /nonexistent to make sure that builds don't modify files in the home directory, which is forbidden by Debian Policy (for good reason builds are not supposed to change things outside the build directory). In your case the build process does try create the directory $HOME/.m2/repository, and that fails because of this. So in this case pbuilder caught the problem very early. I'm not in the Java packaging community, but from a little searching .m2 appears to be created by the Maven build system, and I know for sure there is software packaged in Debian that uses Maven, so maybe you'd want to take a look at those packages how they do their build. Hope that helps. Regards, Christian
Re: Scala 2.10
Hi >I'm not in the Java packaging community, but from a little searching >.m2 appears to be created by the Maven build system, and I know for >sure there is software packaged in Debian that uses Maven, so maybe >you'd want to take a look at those packages how they do their build. I'm far from being a java expert, but IIRC maven tries to download from internet or create such directories when a dependency is not available. Solution: package it, and add it to control file, and try again. G.
