Bug#667000: Rebuilding objenesis from source makes mockito FTBFS
Hello Moritz, Thanks for your patch, I have improved it and applied it on objenesis. Ludovic On 03/04/2012 13:43, Moritz Mühlenhoff wrote: On Dienstag, 3. April 2012 12:06:38 Moritz Muehlenhoff wrote: Package: objenesis Version: 1.2+full-1 Severity: serious Diffing the file lists between the version in the archive and the rebuilt version shows that these files are missing after the rebuild: /usr/share/java/objenesis-1.2.jar /usr/share/java/objenesis.jar Attached patch fixes this, I'd appreciate some review from someone with more Java packaging foo, though. Cheers, Moritz __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587401: closed by Torsten Werner twer...@debian.org (Bug#587401: fixed in antlr3 3.2-3)
Julien, Can you open a new bug report for the POM issue and include the build logs? Thanks, Ludovic Le 28/06/2010 22:14, Julien BLACHE a écrit : ow...@bugs.debian.org (Debian Bug Tracking System) wrote: Hi, antlr3 (3.2-3) unstable; urgency=low . * Clean up build dependencies. (Closes: #587401) And, third time's the charm, indeed. Except for kfreebsd-* where the build fails with an XML exception - looks like the POM may be broken after patching. As 3.0.1 did have packages for kfreebsd-*, this will block the testing migration :( Thanks for your work on ANTLR! JB. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572048: I can confirm failure to start
Pier, this looks like a conflict on port 8005. Can you run this command: netstat -p -l | grep 8005 Thanks, Ludovic Pier Luigi Pau a écrit : Hello, I couldn't get tomcat6 6.0.24-2 to start, either, and so far I haven't found anything better to do than revert to a previous version (6.0.20-dfsg1-1). This is on amd64, for the record. Purging the packages and reinstalling 6.0.24-2 didn't help; nor did switching between openjdk-6 and sun-java6. I had lines similar to these in my /var/log/tomcat6/catalina.(date).log: 1-mar-2010 10.34.37 org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/jni:/lib:/usr/lib 1-mar-2010 10.34.37 org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 1-mar-2010 10.34.37 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 570 ms 1-mar-2010 10.34.37 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 1-mar-2010 10.34.37 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.24 1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor ROOT.xml 1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor docs.xml 1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor host-manager.xml 1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor manager.xml 1-mar-2010 10.34.37 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor examples.xml 1-mar-2010 10.34.38 org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 1-mar-2010 10.34.38 org.apache.catalina.startup.Catalina start INFO: Server startup in 591 ms 1-mar-2010 10.34.38 org.apache.catalina.core.StandardServer await GRAVE: StandardServer.await: create[8005]: java.net.SocketException: Invalid argument at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336) at java.net.ServerSocket.bind(ServerSocket.java:336) at java.net.ServerSocket.init(ServerSocket.java:202) at org.apache.catalina.core.StandardServer.await(StandardServer.java:373) at org.apache.catalina.startup.Catalina.await(Catalina.java:657) at org.apache.catalina.startup.Catalina.start(Catalina.java:617) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) An interesting behaviour I noticed: running /etc/init.d/tomcat6 start manually gave me an indication of failure; instead, if I rebooted my box altogether, it apparently worked, and I had a file with a process id at /var/run/tomcat6.pid, but by the time I could get into a shell, the process had somehow disappeared (died?). /etc/init.d/tomcat6 stop would answer that tomcat6 wasn't running, /etc/init.d/tomcat6 start would complain that there was a pid file and therefore nothing had to be done. Regards, Pier Luigi Pau ___ pkg-java-maintainers mailing list pkg-java-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572048: tomcat6: fails to start after upgrade to v6.0.24-2
Hello Teodor, The changes were motivated by the fact that jscv is unreliable (see #561559) and is hard to use when you need to setup Tomcat with ports 1024. Upstream maintains the catalina.sh script and recommends its use. We were kindly assisted by a Tomcat expert (Jason Brittain from MuleSoft) in this transition. With this script, it is now possible to use authbind easily if the ports are under 1024. Can you give me more details about your setup. It looks like an upgrade, so what other packages or webapps have you installed? Can you provide the Tomcat logs in /var/log/tomcat6. Thanks, Ludovic Teodor a écrit : Package: tomcat6 Version: 6.0.24-2 Severity: grave Justification: renders package unusable Hi, After todays upgrade to v6.0.24-2 due to migration to 'testing' the tomcat6 service doesn't start anymore. I've tried a fresh install and there is no difference. I see that 'jscv' is no longer used and 'authbind' is disabled by default, thus 'catalina.sh' upstream script is used instead. I believe this is a major regression since 'jsvc' is the only alternative for running a java-baser program as a service. The upstream 'catalina.sh' shell script doesn't make use of 'jsvc' because it is not available on all platforms, this script is meant to be portable on all Linux/ UNIX hosts. Another issue is that the execution of 'catalina.sh' should also be redirected to STDOUT/STDERR to avoid these informative lines: | Starting Tomcat servlet engine: tomcat6Using CATALINA_BASE: /var/lib/tomcat6 | Using CATALINA_HOME: /usr/share/tomcat6 | Using CATALINA_TMPDIR: /tmp/tomcat6-tmp | Using JRE_HOME:/usr/lib/jvm/java-6-openjdk | Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar | failed! | invoke-rc.d: initscript tomcat6, action start failed. Thanks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tomcat6 depends on: ii adduser 3.112 add and remove users and groups ii tomcat6-common6.0.24-2 Servlet and JSP engine -- common f Versions of packages tomcat6 recommends: ii authbind 1.2.0 Allows non-root programs to bind() Versions of packages tomcat6 suggests: pn tomcat6-admin none (no description available) pn tomcat6-docs none (no description available) pn tomcat6-examples none (no description available) pn tomcat6-user none (no description available) -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545674: tomcat6: Crashes when trying to run a web app, including admin
I will, but now I'm moving houses and I don't have much access to Internet and my dev box is in another country. This is in my todo list for November, there is a small issue to fix in maven-repo-helper, then I will fix tomcat. Ludovic Michael Koch a écrit : On Mon, Sep 28, 2009 at 10:26:07AM +0200, Jakub Skoczen wrote: On my machine all jars under /usr/share/maven-repo/javax are real files and not symlinks. That includes Servlet, JSP and Expression Language APIs so stuff definitely loaded by tomcat: |-- javax | |-- el | | `-- el-api | | `-- 2.1 | | |-- el-api-2.1.jar | | `-- el-api-2.1.pom | `-- servlet | |-- jsp | | `-- jsp-api | | `-- 2.1 | | |-- jsp-api-2.1.jar | | `-- jsp-api-2.1.pom | `-- servlet-api | `-- 2.5 | |-- servlet-api-2.5.jar | `-- servlet-api-2.5.pom Latest package (libservlet2.5-java) also has it this way: mk...@quadriga ~ dpkg -c /var/cache/apt/archives/libservlet2.5-java_6.0.20-6_all.deb | grep jar$ -rw-r--r-- root/root 27811 2009-09-25 07:20 ./usr/share/maven-repo/javax/el/el-api/2.1/el-api-2.1.jar -rw-r--r-- root/root 76591 2009-09-25 07:20 ./usr/share/maven-repo/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar -rw-r--r-- root/root 88191 2009-09-25 07:20 ./usr/share/maven-repo/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar lrwxrwxrwx root/root 0 2009-09-25 07:20 ./usr/share/java/jsp-api-2.1.jar - ../maven-repo/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar lrwxrwxrwx root/root 0 2009-09-25 07:20 ./usr/share/java/el-api-2.1.jar - ../maven-repo/javax/el/el-api/2.1/el-api-2.1.jar lrwxrwxrwx root/root 0 2009-09-25 07:20 ./usr/share/java/servlet-api-2.5.jar - ../maven-repo/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar Ludovic, can you please take a look at this? Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545674: tomcat6: Crashes when trying to run a web app, including admin
Hi Jakub, This was a temporary issue with the way I installed jars both to /usr/share/java and /usr/share/maven-repo. In an old version of maven-repo-helper, the script mh_installjar was copying the jars to /usr/share/maven-repo and a link was created in /usr/share/java. I'm doing now the opposite, as it respects more the way things were done before. So this situation is only temporary, if your package is rebuilt against the latest version of maven-repo-helper, then this problem should not appear. Ludovic Jakub Skoczen a écrit : Hi Ludovic, Enabling all security privileges to /usr/share/maven-repo/ did the trick. Still, I don't fully understand why this is needed - shouldn't the maven repository be only used for building stuff (like source packages)? Why does a running tomcat instance even know about it and tries to load jar files from there? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545674: tomcat6: Crashes when trying to run a web app, including admin
Yes, this version should fix this bug. It works for me, Jakub, can you confirm that the fix works for you as well? Ludovic Michael Koch a écrit : Hello, On Thu, Sep 24, 2009 at 12:29:11PM +0100, Ludovic Claude wrote: This was a temporary issue with the way I installed jars both to /usr/share/java and /usr/share/maven-repo. In an old version of maven-repo-helper, the script mh_installjar was copying the jars to /usr/share/maven-repo and a link was created in /usr/share/java. I'm doing now the opposite, as it respects more the way things were done before. So this situation is only temporary, if your package is rebuilt against the latest version of maven-repo-helper, then this problem should not appear. Does this mean we should upload 6.0.20-6 to the archive? Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545674: tomcat6: Crashes when trying to run a web app, including admin
Hello Heikki and Jakub,
Thanks for this detailed error report. I believe that I have fixed this
issue, by adding a grant on /usr/share/maven-repo/ in the file
02debian.policy. Can you check that it is working? If you need, I have
created a new .deb in my PPA
(https://launchpad.net/~ludovicc/+archive/ppa/), and I will add those
fixes shortly to Debian.
02debian.policy:
// These permissions apply to all JARs from Debian packages
grant codeBase file:/usr/share/java/- {
permission java.security.AllPermission;
};
grant codeBase file:/usr/share/maven-repo/- {
permission java.security.AllPermission;
};
grant codeBase file:/usr/share/ant/lib/- {
permission java.security.AllPermission;
};
Ludovic
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542550: maven2: Crash after upgrading to latest plexus libs
Hello Stefan, You need to upgrade Maven as well, the current version in the repository is 2.2.0. Maven is very sensitive to the version of its dependencies. Ludovic Stefan Hübner a écrit : Package: maven2 Version: 2.0.9-2 Severity: grave Justification: renders package unusable I upgraded to the latest plexus libraries this morning. Now maven2 is unusable, as it fails right on start: sthub...@sthubner-1:~$ mvn -v Exception in thread main java.lang.NoClassDefFoundError: org/codehaus/plexus/component/repository/exception/ComponentLifecycleException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.privateGetPublicMethods(Class.java:2547) at java.lang.Class.getMethods(Class.java:1410) at org.codehaus.classworlds.Launcher.getEnhancedMainMethod(Launcher.java:195) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:294) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.ClassNotFoundException: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 9 more These are the libraries I've upgraded to: libplexus-classworlds-java 1.2+svn5720-1 libplexus-component-api-java 1.0+svn6316-1 libplexus-container-default-java 1.0-alpha-9-stable-1-2 libplexus-interactivity-api-java 1.0-alpha-6-2 libplexus-interpolation-java 1.7-2 libplexus-utils-java 1:1.5.6-3 libplexus-velocity-java 1.1.6-1 libplexus-classworlds-java 1.5.0-2 libplexus-component-api-java 1.0.0~alpha22-2 libplexus-container-default-java 1.0-alpha-9-stable-1-4 libplexus-containers-java 1.0~beta2-2 libplexus-i18n-java 1.0-beta-7+svn6675-3 libplexus-interactivity-api-java 1.0-alpha-6-4 libplexus-interpolation-java 1.11-2 libplexus-utils-java 1:1.5.15-2 libplexus-velocity-java 1.1.7-2 Thanks, Stefan -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages maven2 depends on: ii libcommons-cli-java 1.2-2 API for working with the command l ii libdoxia-java1.1-3 a powerful content generation fram ii libjsch-java 0.1.41-2pure Java implementation of the SS ii libjtidy-java7+svn20070309-4 a Java port of HTML Tidy, a HTML s ii libplexus-interactivity- 1.0-alpha-6-4 interactivity API for the Plexus f ii libplexus-utils-java 1:1.5.15-2 utilities for the Plexus framework ii libwagon-java1.0-beta-2-4tools to manage Maven artifacts an ii libxalan2-java 2.7.1-2 XSL Transformations (XSLT) process maven2 recommends no packages. maven2 suggests no packages. -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542162: maven2: mvn command fail right after installing the package
Hello, Can you send me the contents of /etc/maven2/m2.conf? Also, have you tried a full removal of the package then reinstalling it? Ludovic Matthieu Baechler a écrit : Package: maven2 Version: 2.2.0-2 Severity: grave Justification: renders package unusable I just installed maven2 package, and the command returns an error when invoqued : matth...@matthieu-laptop:~$ mvn org.codehaus.classworlds.NoSuchRealmException: plexus.core at org.codehaus.classworlds.ClassWorld.getRealm(ClassWorld.java:128) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:434) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) It used to work 3 weeks ago, so I thing some recent changes breaks it. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages maven2 depends on: ii libmaven2-core-java 2.2.0-2Core libraries for Maven2 ii openjdk-6-jre [java2-runtime] 6b16-4 OpenJDK Java runtime, using Hotspo ii openjdk-6-jre-headless [java2 6b16-4 OpenJDK Java runtime, using Hotspo ii sun-java5-jre [java2-runtime- 1.5.0-20-1 Sun Java(TM) Runtime Environment ( ii sun-java6-jre [java2-runtime- 6-15-1 Sun Java(TM) Runtime Environment ( Versions of packages maven2 recommends: ii libmaven-clean-plugin-java2.3-3 Maven clean plugin ii libmaven-compiler-plugin-java 2.0.2-4Maven compiler plugin ii libmaven-install-plugin-java 2.3-2 Maven install plugin ii libmaven-jar-plugin-java 2.2-4 Maven Jar plugin ii libmaven-resources-plugin-jav 2.3-5 Maven resources plugin ii libmaven-shade-plugin-java1.2.1-2Maven shade plugin maven2 suggests no packages. -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518446: doxia-sitetools: FTBFS: java.lang.reflect.InvocationTargetException
Torsten, plexus-build-api is used only on modello 1.0+, so it looks like you where using the wrong version of the sources. There was a uscan --upstream-version 0 in debian/rules which always download the latest version of the sources, regardless of the version given in the changelog, so that may be what happened to you. I always use uscan --download-version $(DEB_UPSTREAM_VERSION) --force-download --rename as it's more reliable. Ludovic -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
