Re: Bug#784162: jenkins: FTBFS due to error with jsr305 missing maven artifact
On Sun, May 03, 2015 at 10:12:19PM +, Potter, Tim (Cloud Services) wrote: [...] I’m unable to build some other packages because of this error as well. It’s happened enough that I think it might be a problem with the jsr305 package (or combination of other packages) that’s currently in testing. Does anyone else think this is likely? Hi Tim, Maybe it could be my fault. libjsr305-java/0.1~+svn49-5 was in experimental for almost three years and in the last week I just uploaded that to sid. If you have time to review what's wrong, please go ahead. If not, I'll take a look at it later. Thanks, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Re: Bug#784162: jenkins: FTBFS due to error with jsr305 missing maven artifact
On 4 May 2015, at 3:18 am, Miguel Landaeta nomad...@debian.org wrote: Package: src:jenkins Version: 1.565.3-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Missing: -- 1) org.jsr-305:jsr305:jar:0.x Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.jsr-305 -DartifactId=jsr305 -Dversion=0.x -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.jsr-305 -DartifactId=jsr305 -Dversion=0.x -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.17 2) org.kohsuke.stapler:stapler:jar:debian 3) org.jsr-305:jsr305:jar:0.x I’m unable to build some other packages because of this error as well. It’s happened enough that I think it might be a problem with the jsr305 package (or combination of other packages) that’s currently in testing. Does anyone else think this is likely? Tim. smime.p7s Description: S/MIME cryptographic signature
Re: Bug#784162: jenkins: FTBFS due to error with jsr305 missing maven artifact
If you have time to review what's wrong, please go ahead. If not, I'll take a look at it later. This is caused by a change in the Maven coordinates. Installing the artifacts under /usr/share/maven-repo/org/jsr-305/jsr305/0.x/ should fix the issue. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5546af80.2030...@apache.org
Re: Bug#780703: closed by Markus Koschany a...@gambaru.de (eclipse-pydev fails to build from source)
On 05/03/2015 06:58 AM, tony mancill wrote: On 05/03/2015 02:44 AM, Markus Koschany wrote: On 03.05.2015 04:26, Miguel Landaeta wrote: libjnr-constants-java : Conflicts: libconstantine-java but 0.7-6 is to be installed. Unable to resolve dependencies! Giving up... The package build fine during the freeze and tony could successfully upload eclipse-pydev. My guess is that we probably need a build-dependency on python to make sure that all dependency resolvers pull in the right packages. But the current error is different from this. Yes, we need to execute on the jnr transition. I have a local branch of eclipse-pydev where I started on this, but need to return to it. I'm not sure why libjnr-constatnts-java doesn't get pulled in - perhaps there is an explicit build-dep on libconstantine-java somewhere in the build-dependency graph. Sorry - I need to not send emails *before* my morning coffee. I'm pretty sure that we just need a source upload of jnr-constants that includes a transitional package (see [1]). Miguel and Tim, I'm planning on using libconstantine-java 0.7-6 for the versioned dependency - does this cause any issues with the upload of 0.8.5 to experimental in January? Thank you, tony [1] https://wiki.debian.org/Renaming_a_Package signature.asc Description: OpenPGP digital signature
jboss-logging
On 30.04.2015 18:13, Markus Koschany wrote: On 30.04.2015 18:02, Emmanuel Bourg wrote: Thank you Markus, I just uploaded them and they are now in the NEW queue. Thank you. I'll take care of jboss-logging at the weekend and get back to you. I have uploaded my current work to https://anonscm.debian.org/cgit/pkg-java/jboss-logging.git/ It takes a while to become visible. It's not finished yet because the package still FTBFS. I see two error messages, it is either a packaging error (wrong maven rules?) or apache-log4j2 needs an update. [ERROR] /tmp/buildd/jboss-logging-3.2.1/src/main/java/org/jboss/logging/Log4j2Logger.java:[54,27] error: cannot find symbol [ERROR] symbol: method logMessage(String,Level,null,Message,Throwable) location: variable logger of type AbstractLogger /tmp/buildd/jboss-logging-3.2.1/src/main/java/org/jboss/logging/Log4j2Logger.java:[66,27] error: cannot find symbol [INFO] 2 errors~ Regards, Markus signature.asc Description: OpenPGP digital signature
