Bug#325255: Reassigning to classpath-tools
reassign 325255 classpath-tools thanks classpath-tools is at fault. It registers the alternatives with a different name than during removal: XXX-cp vs. cp-XXX (see prerm/postinst) Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Away for a week
Hi all, just to inform you: I am on a business trip till 3rd april and most probably won't have internet access. If kaffe really releases its second rc this week I won't be able to prepare a package. There are some fixes on my local disk for the kaffe package. If anyone wants to upload the rc go ahead and I will incorporate all the fixes and some other stuff I planned in a later upload. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#358237: make-jpkg should create two .deb files instead of one
Daniel Gimpelevich wrote: Package: java-package Version: 0.27 Severity: wishlist I would be very interested in any arguments against making java-package enable this to happen. Thank you. The simplest argument against it is: Its just not possible to use the non-free runtime classlibraries with a free runtime. AFAIK, for interaction between a runtime and the class library a VM interface is needed. And thats not the same between the non-free and GNU classpath derived runtimes. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#358237: make-jpkg should create two .deb files instead of one
Daniel Gimpelevich wrote: On Mar 22, 2006, at 12:13 AM, Wolfgang Baer wrote: Daniel Gimpelevich wrote: Package: java-package Version: 0.27 Severity: wishlist I would be very interested in any arguments against making java-package enable this to happen. Thank you. The simplest argument against it is: Its just not possible to use the non-free runtime classlibraries with a free runtime. AFAIK, for interaction between a runtime and the class library a VM interface is needed. And thats not the same between the non-free and GNU classpath derived runtimes. Wolfgang Hmm. I was under the impression that the VM interface had become sufficiently compatible for a full compatibility layer to be straightforward. Class libraries consist of classes, and since there are classes that work with both runtimes separately from any class library, I thought that differences in functionality between the free and non-free environments was primarily due to differences between the class libraries, with the VM interfaces being relatively equal. If I was mistaken, I am sorry. The jni interface (and the newer jawt interface) should be compatible with the non-free implementations. The interface VM/Classlib can't be as it is AFAIK not defined anywhere by SUN. For information about the VM interface of GNU classpath see: http://www.gnu.org/software/classpath/docs/vmintegration.html Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#358356: cacao: crash when using Cairo backend
Egon Willighagen wrote: Package: cacao Version: 0.95-1 Severity: normal I tried to use the cairo backend using 'cacao -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D' as described in /usr/share/doc/classpath/README.Debian but it crashes like this: [EMAIL PROTECTED]: ~/var/Projects/SourceForge/Jmol/trunk/Jmol $ cacao -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D -jar Jmol.jar English: no need for gettext wrapper [EMAIL PROTECTED] *** glibc detected *** free(): invalid pointer: 0x096bd878 *** Aborted Might be related to the new glib in unstable: http://lists.debian.org/debian-devel/2006/03/msg00941.html Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#354601: eclipse: Project names umlaut (special chars) problem
Raphael Fuchs wrote: Package: eclipse Version: 3.1.2-1 Severity: normal When a project is created with umlauts in its name, no files can be added to the project. More precisely, they get created in the workspace folder but disappear from the Navigator. In the source code editor view, the following message gets displayed: Resource foobar.java does not exist. There was a bug in kaffe which exists more or less equally in all runtimes. The kaffe fixes are described in http://www.kaffe.org/pipermail/kaffe/2006-February/103981.html The first classpath specific fix is already committed in GNU classpath. The other one is pending as RFC. We need to check if these are applicable for gcj and if there exists maybe more problems in there file implementation. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#342200: argouml: Please advise
Hi Arnaud, Arnaud Vandyck wrote: Wolfgang Baer wrote: Hi all, Yo Wolfgang, Well, I am basically interested in argouml so I did a little research on the new upstream some time ago. The main problem is that they - don't ask me why - they started to use netbeans stuff for the uml model implementation. Because ocl is no more maintained for many years now and they are stick in UML 1.x. They still target UML 1.4 with the MDL stuff. The problem is that netbeans stuff is licensed under the SPL alone which with a quick google search is likely to be undistributable by debian. Strange, the SPL license is an official Open Source Initiative open license. That doesn't mean that it is DFSG free at all. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#338287: DSSI entered debian
Hi Michael, just found dssi in incoming. It has already build on all architectures, so you can try to build against with your next upload. http://packages.qa.debian.org/d/dssi.html Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#342200: argouml: Please advise
Hi all, Michael Koch wrote: Hello, On Wed, Feb 08, 2006 at 10:44:08PM -0300, Javier Kohen wrote: Could you please share with us the reasons for not closing this bug, in other words, why we don't yet have the latest version of ArgoUML in Debian? Namely, is it because of personal reasons, lack of motivation, etc., or because said version has known fatal bugs? Arccording to http://wiki.debian.org/Java/ShouldGoToMain argouml doesnt run with free Java runtimes yet. This lowers the motivation for working it a lot. We want to move all Java packages to the Debian main section. this can only be done when a package can be built and run with purely free software. To help with this you can e.g. test argouml with free runtimes and report bugs to upstream so they can fix it. then when these fixes enter Debian we can reconsider argouml and update it. Well, I am basically interested in argouml so I did a little research on the new upstream some time ago. The main problem is that they - don't ask me why - they started to use netbeans stuff for the uml model implementation. The problem is that netbeans stuff is licensed under the SPL alone which with a quick google search is likely to be undistributable by debian. So the first thing before a new upstream version will enter debian is to check if there is a clear status for the SPL with debian-legal. Thats something which still has to be done. And I have currently no time for some legal discussions. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#350700: ecj-bootstrap: Fails to build xml-crimson
tags 350700 + pending thanks Matthias Klose wrote: looks more like some problem in the build file, passing all source files directly to ecj lets the build succeed. Patch ready. Will prepare a new upload. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#351076: ant: Java illegalAccess exception with the kaffee compiled version
Hi, FROHNER Akos wrote: On Tue, 2006-02-07 09:56:16 +0100, Arnaud Vandyck wrote: http://snapshot.debian.net/archive/2005/10/02/debian/pool/main/a/ant/ Thanks! 1.6.2-2 works 1.6.5-3 works Build with jikes 1.6.5-4 fails: build.xml:7: java.lang.IllegalAccessError: tried to access field org.apache.tools.ant.taskdefs.Concat.fileUtils from class org.apache.tools.ant.taskdefs.Concat$TextElement 1.6.5-5 fails: build.xml:7: java.lang.IllegalAccessError: tried to access field org.apache.tools.ant.taskdefs.Concat.fileUtils from class org.apache.tools.ant.taskdefs.Concat$TextElement Both build with ecj Thanks for testing. So it really looks like ecj produces wrong bytecode here. I will retry with ecj 3.1.2 (fixed some compiler stuff) as I think ecj at the time of the ant build was 3.1.1. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#351053: ftbfs: /bin/bash: -c: line 1: syntax error: unexpected end of file
Max Kellermann wrote: On 2006/02/02 17:57, Wolfgang Baer [EMAIL PROTECTED] wrote: this is completely unreproducible here and on other machines. Please retry and if it still fails provide information about your system and versions of packages involved in the build (version of make ...) It is perfectly reproducible here. However, when I remove the comments in the for loop in debian/rules, it builds. ii bash 3.1-1 ii make 3.80-9 OK, you are running a stable/testing mixture. I'm not sure about comment syntax in lines concatenated with backslashes... might be a difference in how make passes this multiline command to bash. Yes, there were quite some discussions about changed behaviour of make 3.81 on d-devel. Maybe this is also related. If the comments are a problem I will remove them with next upload to ease stable backports after 1.1.7 is released. Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#351053: ftbfs: /bin/bash: -c: line 1: syntax error: unexpected end of file
tags 351053 + unreproducible thanks Hi Max, this is completely unreproducible here and on other machines. Please retry and if it still fails provide information about your system and versions of packages involved in the build (version of make ...) Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#351076: ant: Java illegalAccess exception with the kaffee compiled version
severity 351076 normal thanks Hi Akos, this is not grave if it fails for one type of build file, therefore lowered severity to normal. ant is used here in almost all the package builds and no build failed because of the new upload. Frohner Akos wrote: The example build.xml file reports the following error with 1.6.5-4, 1.6.5-5, but worked up to 1.6.5-3 (explicitly checked with 1.6.2): Have you explicitly checked with 1.6.5-3 ? Checking with 1.6.2 does not mean it worked up to 1.6.5-3. build.xml:3: java.lang.IllegalAccessError: tried to access field org.apache.tools.ant.taskdefs.Concat.fileUtils from class org.apache.tools.ant.taskdefs.Concat$TextElement project default=concattest target name=concattest concat headershall work/header fileset file=build.xml/ /concat concat header file=build.xml/ fileset file=build.xml/ /concat /target /project The only difference, according to the changelog, is that from 1.6.5-4 ant is compiled with kaffee. The difference is its compiled with ecj - it was already compiled with kaffe a longer time (just with jikes). Maybe ecj produces for this special case wrong bytecode. This needs to be investigated. I will rebuild with jikes to see what happens. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#350694: velocity: FTBFS: -Dbuild.compiler=jikes without Build-Depends on jikes
tags 350694 + pending thanks Daniel Schepler wrote: Package: velocity Version: 1.4-3 Severity: serious The package is ready for upload since some time. However my sponsor is currently quite busy. Will be resolved soon. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#350091: kaffe: /usr/lib/kaffe/bin/javac is broken
clone 350091 -1 reassign -1 ecj-bootstrap retitle -1 ecj-bootstrap fails if java-gcj-compat is not installed thanks Hi Daniel, Daniel Schepler wrote: Package: kaffe Version: 2:1.1.6.91-2 Severity: important Several java packages are now failing to build with messages like this one from my build log for cup: I am already aware of this problem. Only java packages which are not build via ant are affected - thats the minority. ... make[1]: Entering directory `/tmp/buildd/cup-0.10k' /usr/lib/kaffe/bin/javac -nowarn -d classes java_cup/*.java java_cup/*/*.java incorrect classpath: /usr/share/kaffe -- 1. ERROR in java_cup/Main.java (at line 1) package java_cup; ^ The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files -- 1 problem (1 error)make[1]: *** [cup.jar] Error 255 make[1]: Leaving directory `/tmp/buildd/cup-0.10k' make: *** [build] Error 2 If this is intentional, and all packages need to specify a classpath or bootclasspath explicitly, let me know so I can file bug reports against the affected packages. No, its not intentional and no package needs to specify anything unless I have filed a bug report against them. The problem is that kaffe now uses ecj-bootstrap as its compiler. Using kaffe via ant directly uses a programming interface and compiles against kaffes runtime classes. Compiling with the javac command is (currently) a link to /usr/bin/ecj. The problem is that ecj-bootstrap is the source of the failure. It somehow needs some setup from java-gcj-compat to fullfill its job. You can easily verify this by installing java-gcj-compat and compiling a simple HelloWorld.java with /usr/bin/ecj-bootstrap which will work. Removing java-gcj-compat and it will fail. However, where the problem is is still to be investigated. The other (upcoming) fix will be that kaffe uses its own wrapper script against ecj-bootstrap to compile against its runtime classes. This will be added in the next uploads and fixes the problems regardless of ecj-bootstrap. I will therefore clone this bug report and reassign to ecj-bootstrap. I will let it open against kaffe until the new wrapper script is added. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: CVS to SVN transition
Hi Philipp, Philipp Meier wrote: Hi all, I was wondering what is the state of the CVS to SVN transition. The CVS commit mailing list says that there were some imports from CVS into SVN. I was unable to find information about the SVN repository location and the transition state of the jetty package. The transition is already complete and the CVS repository should no longer be used. Details can be found here: http://lists.debian.org/debian-java/2006/01/msg00057.html Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#348647: ftbfs: /usr/bin/ecj: No such file or directory
Max Kellermann wrote: Package: ant Version: 1.6.5-4 Tags: FTBFS Severity: minor missing build dependency? No, missing versioned build-dependency to kaffe (= 2:1.1.6.91-1) Missed that the bootstrap is not via ant, so its directly impacted by the kaffe transition and needs (as only package) versioned build dependency on kaffe. Will do it in the next upload. Thanks for noticing. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Kaffe compiler transition
Hi all, you get this mail because your package(s) build-depend on kaffe. Today a new kaffe release will be uploaded with several changes which might break your packages build. The noticable change is the change of the build compiler to ecj (eclipse compiler for java). I have opened a wiki page to track the transition under: http://wiki.debian.org/Java/KaffeTransition I tested every package (excluding pkg-java maintainers packages where I will take care of) against this new kaffe package for breakage and commented on it on this wiki page. There is also a section with the most common problems and how to fix them. The good news are that only 5 packages (excluding pkg-java maintainers packages) FTBFS and need a little care. In the next days I will file bugs against the packages which FTBFS together with a patch. If you have any questions don't hesitate to contact us under the debian-java mailinglist or on #debian-java. Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Kaffe compiler transition
[Sorry if you get this mail twice. I resend it because it didn't reach pkg-java maintainers list until now. And therefore maybe failed for other also.] Hi all, you get this mail because your package(s) build-depend on kaffe. A new kaffe release will be uploaded soon with several changes which might break your packages build. The most noticable change is the change of the build compiler to ecj (eclipse compiler for java). I have opened a wiki page to track the transition under: http://wiki.debian.org/Java/KaffeTransition I tested every package (excluding pkg-java maintainers packages where I will take care of) against this new kaffe package for breakage and commented on it on this wiki page. There is also a section with the most common problems and how to fix them. The good news are that only 5 packages (excluding pkg-java maintainers packages) FTBFS and need a little care. In the next days I will file bugs against the packages which FTBFS together with a patch. If you have any questions don't hesitate to contact us under the debian-java mailinglist or on #debian-java. Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: libgnujaxp-java needed ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, Chris Burdess wrote: No, GNU JAXP is not being maintained any more as a separate project. It's not terribly useful as a 3rd-party library anyway, as the older Sun VMs packaged incompatible W3C DOM versions, so getting it to work involved patching the bootclasspath and lots of other headaches. Chris, thanks for the update. So we should work for removal of this package for etch. Shouldn't be much work only a few packages - I will have a look. Only point is sablevm depends on it - however they should just provide it in their class library if they going to update the debian package. I hope this will be done before edge :-) @Arnaud, as Chris already said its not so easy to use it together with non-free JDKs. Also keep in mind that using different XML libraries would at least need some setting of properties which is not what you can expect from an user using a non-free JDK - they are ok with what ships with the JDK, IMHO. Regards, Wolfgang -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDqWfaj1oFdKryxgoRAlcUAJ0Zk0LeJYE6g5kLYOrKXQD9UH1OUQCeLrQc 1drFipvnIY1H9/fPF+5iRSs= =WWLU -END PGP SIGNATURE- ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#344327: jmp: hello world fails, cairo-surface.c:658
Hi Timo,
Timo Juhani Lindfors wrote:
Package: jmp
Version: 0.47-1
Severity: normal
Steps to reproduce:
1) cat Hello.java EOF
public class Hello {
public static void main(String[] args) {
System.out.println(Hello World);
}
}
EOF
2) javac Hello.java
3) kaffe -Xrunjmp Hello
Expected results:
3) jmp window should open, show information and then close.
For non-gui apps you need to stop termination of program by
reqeusting some input. Put a System.in.read() before the
end of the main method. Thats the normal usage - see the
jmp user guide.
Actual results:
3) jmp window opens, shows information (possibly, it's too fast to
see) and then closes. However, kaffe prints the following error
message:
jmp/0.47 initializing: ():...
tracing objects: true
tracing methods: true
tracing monitors: true
showing gui: true
dump/reset by signal allowed: false
jmp: Enabling localization.
jmp: Loaded and registered correctly.
Hello World
failed to find thread that ended: 0x8073018
jvm_shut_down.
c_class_load: 135
c_class_unload: 0
c_object_alloc: 1717
c_object_move: 0
c_object_free: 0
c_thread_start: 0
c_thread_end: 1
c_method_entry: 15054
c_method_exit: 15054
teardown called, freeing jmp-data..
kaffe-bin: cairo-surface.c:658: _cairo_surface_release_dest_image: Assertion
`!surface-finished' failed.
Aborted
Yes, its known that kaffe has problem with jmp _only_ during
shutdown.
This might be a bug in kaffe and/or cairo and not jmp but since I'm
not sure I'm first reporting it against 'jmp'. Please reassign as
necessary.
I will leave it here as I already reassigned/forwared one to kaffe and
people looking for bugs on jmp before reporting. So it might be better
to let it stay here.
Regards,
Wolfgang
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
libgnujaxp-java needed ?
Hi all, we got two bug reports against libgnujaxp-java today. As they are clearly upstream things I wondered if its still developed as an external package. As far as I know its fully merged into gnu classpath. Following cp-patches list it seems further development is only done there. As the jaxp stuff should be now provided by all free runtimes its maybe time to work towards removal of this package. Comments ? Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#344187: libgnujaxp-java: Doesn't accept relative URI as SystemID in entities
Hi Jiri, Jiri Palecek wrote: There is a MalformedURLException when using relative URI for entity's SystemID. The relative URI indeed isn't valid URL, however the XML 1.0 standard allows URI refernces as SystemIDs. Do you have or can make a simple testcase we can use to forward the problem upstream ? Same would be nice for the other bug you reported (#344183). GnuJaxp is now fully merged into GNU classpath so we currently check if there will be separate releases as external package in the future. If you can provide testcases I would like to test against GNU classpath CVS to see if it might be fixed already. Thanks for using debian, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: tomcat5 policy changes suggestion
Hi Michael, Michael Jenik wrote: Hi, I have installed tomcat5 pro apt-get install tomcat5 unstable.- I heve had many problems discovering that there were missing permissions in the policy files. There are no missing permissions at all - Everything required to run tomcat5 (with its bundled applications) is there. The setting of policies for web applications is in the responsibility of the administrator. The package maintainers cannot know what will be installed on tomcat in the end. catalina wasn't able to deploy use a jsf aplication in a war file. I solved the problem adding this lines to 04webapps.policy. How this stuff could be workarrounded ? Seems you have already workaround it by adding your needed stuff in 04webapps.policy. However I would suggest using a per webapp file for the new permissions and let the existing file only be used for the tomcat bundled policy. permission java.io.FilePermission /var/lib/tomcat5/temp/-, read,write,delete; permission java.io.FilePermission /var/lib/tomcat5/conf/Catalina/-, read,write,delete; permission java.net.SocketPermission java.sun.com:80, connect,resolve; You didn't say what application you are trying to deploy. However giving complete permissions to the configuration directory is not a good thing imho. Also I wonder why an application needs to connect to java.sun.com ? Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#341777: Support Mysql for WebApps deployed to Tomcat
tags 341777 + wontfix thanks Hi Andreas, Andreas Schildbach wrote: Package: tomcat5 Severity: wishlist If I have both packages tomcat5 and libmysql-java installed, I'd like to have the Connector/J driver availble for web applications installed into Tomcat, just as if I had copied the driver to common/lib. Why don't you symlink from /usr/share/tomcat5/common/lib/mysql.jar to /usr/share/java/mysql.jar? You would have a dangling symlink if libmysql-java is not installed or removed after some time. Also if you need stuff in your webapps you should put it in or link it from the webapps libs/classes directory to get it picked up. This is also some kind of security problem as common/lib is trusted. Another point is where would you draw the line ? If linking libmysql-java why not also jdbc for postgresql, sapdb, hsqldb ... you can add almost every library to this list. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#341928: dangling symlink for rmic man page
Hi Olafur, Olafur Jens Sigurdsson wrote: Package: kaffe Version: 2:1.1.6-3 Hi, my cron job turns up the following error: mandb: warning: /usr/share/man/man1/rmic.1.gz is a dangling symlink and checking the file gives that it is a symlink to /etc/alternatives/rmic.1.gz which is a broken symlink to /usr/lib/jvm/java-gcj/man/man1/rmic.1.gz instead of /usr/share/man/man1/rmic.kaffe.1.gz like I suspect it should be. This is/was caused by a bug in java-gcj-compat which registers a rmic alternative but has not the files in the package and therefore kills all rmic link stuff. This should be resolved in the latest java-gcj-compat package. However the problem will only be fixed by either upgrading kaffe (but we have no new upstream yet) or installing the java-gcj-compat-dev package. A manual fix will be: update-alternative --auto rmic which will fix it back to kaffe. Or use --config to select manual the alternative. I will leave this bug open for the next time as this apparently the second bug report against kaffe for this java-gcj-compat issue. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Why libapache2-mod-jk2 and no libapache2-mod-jk package?
Hi Holger, Holger Rauch wrote: [...] - Why is libapache2-mod-jk2 in Debian stable (Sarge)? Because when sarge was released it was the default for apache2. - Why is libapache-mod-jk only available for Apache 1.3 Wrong - thats onlythe case for sarge. As sarge is released there is no possiblity to make such a change there. In testing and unstable libapache2-mod-jk is available and libapache2-mod-jk2 is removed. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#338628: rmic.kaffe.1.gz: say more in NAME
Hi Dan, Dan Jacobson wrote: Package: kaffe-common Version: 2:1.1.6-3 Severity: wishlist File: /usr/share/man/man1/rmic.kaffe.1.gz 1. man: warning: /usr/share/man/man1/rmic.1.gz is a dangling symlink This is caused by a bug in java-gcj-compat which registers a rmic alternative but has not the files in the package and therefore kills all rmic link stuff (patch for java-gcj-compat is already submitted). update-alternative --auto rmic will fix it back to kaffe. Or use --config to select manual the alternative. 2. NAME rmic - rmic Say more here. Like: NAME cat - concatenate files and print on the standard output Right. Will be done in next upload. Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Removal of libant1.6-java
Hi all, the end of the ant transition ... There are only two packages - nice forrest - left but they are otherwise currently not buildable so we cannot NMU them just for this transition. As the packages have to be fixed by the maintainer anyway I think there is no reason to wait further with the removal of libant1.6-java. So I will request removal of libant1.6-java from the archive. If someone has objections please raise your hand now. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Bugs of libapache2-mod-jk2 package
Hi all, Wolfgang Baer wrote: Hi all, libapache2-mod-jk2 package has been removed from the archive. The open bugs are not for reassigning because mod-jk has a different codebase, configuration ... So the question is (as the package will be still available in sarge) how to properly close the bugs for testing/unstable with the new version tracking. The last version is 2.0.4-3 so I ask myself if closing with a version header of the not existing version 2.0.4-4 will correctly close it for testing/unstable ? Comments are welcome, No comments ? Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#337270: tomcat5: Suggest java-gcj-compat-dev
David N. Welton wrote: Package: tomcat5 Version: 5.0.30-7 Severity: minor Tomcat ought to suggest java-gcj-compat-dev so that it actually runs when you install it. As it was, I had to read the /etc/default/tomcat5 file to find the correct packages to install. Hi David, please explain why tomcat5 should suggest java-gcj-compat-dev. It already (conditional) depends on it. The current depends line is enough to get a working tomcat5 IMHO. It either pulls kaffe or java-gcj-compat-dev in. During startup it will pickup the first available on the path. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#337270: tomcat5: Suggest java-gcj-compat-dev
David N. Welton wrote: Wolfgang Baer wrote: please explain why tomcat5 should suggest java-gcj-compat-dev. It already (conditional) depends on it. The current depends line is enough to get a working tomcat5 IMHO. It either pulls kaffe or java-gcj-compat-dev in. During startup it will pickup the first available on the path. Hrm... then something else isn't right, because it was not starting. When I installed java-gcj-compat-dev, it started functioning correctly. So I assume before installing java-gcj-compat-dev you had only kaffe installed ? Or also a non-free runtime providing java2-runtime ? Can you say what did not work correctly before ? What is in the various tomcat logs (/var/log/tomcat5/*) ? Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#337270: tomcat5: Suggest java-gcj-compat-dev
Hi David, David N. Welton wrote: Wolfgang Baer wrote: So I assume before installing java-gcj-compat-dev you had only kaffe installed ? Or also a non-free runtime providing java2-runtime ? I had kaffe. Can you say what did not work correctly before ? What is in the various tomcat logs (/var/log/tomcat5/*) ? The JAVA_HOME environment variable is not defined correctly This environment variable is needed to run this program NB: JAVA_HOME should point to a JDK not a JRE OK. This explains it and I think I got it now. I assume - beside kaffe - you also had java-gcj-compat (not the -dev package) installed before. The JDK_DIRS variable in tomcat5 init script has the java-gcj-compat directory before the kaffe directory. As you had installed kaffe and java-gcj-compat on your system the tomcat5 installation found kaffe and the depends are satisfied. During startup when tomcat5 init script looks for a usable JDK directory it founds first /usr/lib/jvm/java-gcj (as this is there throught java-gcj-compat) and takes it although not the -dev package is installed. So its a bug which is not solvable by dependencies alone. We will have to implement some more logic into the init script to test if only java-gcj-compat or the wanted java-gcj-compat-dev is installed if we find /usr/lib/jvm/java-gcj directory. Please check if java-gcj-compat was also installed before so I know my analysis is correct. Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#335227: kaffe: rmic throws an exception when no -d option is given
Hi, this is a bug in the runtime library implementation exposed by the rmic implementation. A fix is already submitted upstream and will be part of a future kaffe upload or release. Thanks for reporting, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#335622: jmp: fails to start
reassign 335622 kaffe 2:1.1.6-3 forwarded 335622 kaffe@kaffe.org retitle 335622 kaffe shows error during jmp shutdown on ppc thanks Hi Benoît, I reassign the bug to kaffe which is the cause of the error during shutdown and forward it upstream. Benoît Dejean wrote: Can you please test if this is reproducible or only happens sometimes ? every time Thanks for testing. I noticed that i was unable to close jmp, the [x] buttons do nothing. Is that alright ? I think so - its the same here on x86 and also with SUNs JDK. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bugs of libapache2-mod-jk2 package
Hi all, libapache2-mod-jk2 package has been removed from the archive. The open bugs are not for reassigning because mod-jk has a different codebase, configuration ... So the question is (as the package will be still available in sarge) how to properly close the bugs for testing/unstable with the new version tracking. The last version is 2.0.4-3 so I ask myself if closing with a version header of the not existing version 2.0.4-4 will correctly close it for testing/unstable ? Comments are welcome, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#336245: libpgjava: use upstream package name
Hi Peter, Peter Eisentraut wrote: Package: libpgjava Version: 8.0-312-1 Severity: wishlist As long as you are randomly renaming the package, shouldn't you use the upstream package name? I would not call it randomly - it was a change to comply with java policy ! That would be postgresql-jdbc so the package should be called libpostgresql-jdbc-java. That would also have the nice side effect that people looking for postgresql or jdbc actually find something rather than having to guess at Debian's arbitrary abbreviation scheme. Well, I am open to suggestions and you are right that using upstreams name would be better from our users pov. So what are you proposing ? Currently the following programs rdepend on libpgjava: rhdb-explain - you are the maintainer libpostgis-java - RC buggy needs new upload anyway And openoffice.org-base depends on libpg-java. libpgjava is part of sarge and therefore a transitional package as now exists needs to be kept. We can just rename libpg-java into libpostgresql-jdbc-java. Comments ? Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#335883: libbatik-java: Fop in batik depends on libavalon-framework-java = 4.2.0
Hi Eric, while using FreeMind under Sarge + batik from unstable, I got the following error: java.lang.NoClassDefFoundError: org/apache/avalon/framework/container/ContainerUtil at org.apache.fop.svg.PDFTranscoder.transcode(PDFTranscoder.java:121) at org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(Unknown Source) at org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(Unknown Source) at plugins.svg.ExportPdf.startupMapHook(ExportPdf.java:70) At that time, I had libavalon-framework-java 4.1.2-2.1; after upgrade to version 4.2.0-1, the issue was solved. This means that batik should depend at least upon this version. Thanks for the notice - I will tighten the version in the next upload. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#335479: /usr/share/man/man1/rmic.1.gz is a dangling symlink
reassign 335479 java-gcj-compat 1.0.40-1 thanks Hi Thomas, I reassign this report to java-gcj-compat as its not a kaffe problem. Thomas Schoepf wrote: My system is is up-to-date, pure unstable. java-gcj-compat is version 1.0.41-1. OK is it correctly configured and do you have java-gcj-compat-dev installed and configured (its the one providing rmic) ? Please provide the output of: dpkg -l java-gcj-compat dpkg -l java-gcj-compat-dev On my system ll /usr/lib/jvm/java-gcj/man/man1/rmic.1.gz gives me a correct link to the _grmic_ named version of java-gcj: This like doesn't exist here: [EMAIL PROTECTED]:~$ ll /usr/lib/jvm/java-gcj/man/man1/rmic.1.gz ls: /usr/lib/jvm/java-gcj/man/man1/rmic.1.gz: No such file or directory [EMAIL PROTECTED]:~$ The installation of OpenOffice 2.0 caused the installatio of kaffe etc. Yes thats a known dependency problem atm. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#334878: libbatik-java: Wrong libraries included (?)
Hi Philipp, Philipp Matthias Hahn wrote: Package: libbatik-java Version: 1.6-1 Severity: important $ cat /usr/share/doc/libbatik-java/README.Debian ... batik.jar (full library) batik-ext.jar (batik dom and sax bindings) batik-all.jar (batik without dom and sax bindings) ... 1. There is no batik.jar as mentioned in the README.Debian Right the link got lost. 2. -all and -libs contains the same files Thanks for noticing - must be a change in the build script. I will prepare a -2 upload. 3. I'd like to also have Squiggle, the viewer application, please As it is included (the classes) I assume you mean with script, manpage ... That is not on my TODO list in the near future as this would require a reorganization of the batik package. Thats something to tackle if upstream changes to the new xml-graphics-common and the packages then needs to be reworked anyway. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#334629: FTBFS: Could not create task or type of type junit
Matt Kraai wrote: Package: jmock Version: 1.0.1-1 Severity: serious jmock fails to build: Needs a build-dep on ant-optional after ant reorganization. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Antlr package does not contain python module
Michael Koch wrote: On Mon, Oct 17, 2005 at 02:51:25PM +0530, Suman wrote: Python support has been added recently to antlr.The information for installation can be found in the antlr manual. Thanks for reporting this. Please file a bug report for this. Reports to mailing lists tend to get forgotten easily. There is already a bug open for this http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308356 Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#334012: eclipse - kaffe issue
Hi Carsten, Carsten Hey wrote: Hi. On Sat, Oct 15, 2005 at 10:47:41AM +0200, Wolfgang Baer wrote: Also I am missing the version of eclipse ? I think you mean eclipse 3.1.1-X from unofficial place or do you refere to eclipse 2.1 in the archive ? Sorry, I should have included this information in the bugreport. It is from http://www.backports.org/~mkoch/unstable/. I already talked with mkoch about that an he thinks it is a bug in kaffe (although he did not test it afaik). OK, there are currently newer eclipse packages in NEW queue. When they show up in unstable I will give it a test run. If it works for me with kaffe I will close that bug and otherwise I will forwared it upstream. However jit internals is unlikely to be a small fix. So I don't think we can backport it to 1.1.6. But we will see. After the user had installed gcj-4.0 and eclipse.*-gcj and purged kaffe.* eclipse started as expected. Yeah, thats the free vm Michael has used for packaging most the time I think. There are still quite a bit differences between the free vm's atm. Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#333884: ftp.debian.org: Please remove libapache2-mod-jk2 from archive
Package: ftp.debian.org Severity: normal Hi ftp-masters, the pkg-java maintainers request the removal of libapache2-mod-jk2 package (source and binary) from the archive. Reason: Deprecated upstream, no longer in development superceeded by the newly build libapache2-mod-jk binary package (built from libapache-mod-jk source package), RC buggy The superceeding binary package is now built on all architectures and scheduled for testing propagation tonight. Thanks, Wolfgang -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#249900: libapache2-mod-jk2 will be removed from the archive
Hi all, libapache2-mod-jk2 will be removed from the archive as it is abandoned upstream and superceeded by mod-jk. mod-jk packages for apache2 are now provided by the libapache2-mod-jk binary package on all architectures and will show up tomorrow also in etch. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: eclipse_3.1.1-1_i386.changes is NEW
Hi Michael, great job, thanks ! * Upload to contrib, the remaining reason is tomcat5 beeing in contrib. I am currently waiting for new upload of java-gcj-compat-dev to include a dummy jdb script for tomcat5. If this is done we can upload tomcat5 to main and it will be runnable by the current java-gcj-compat-dev and kaffe packages. Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: RFC: Removal of libapache2-mod-jk2 from archive
Hi all, On Wed, Oct 05, 2005 at 09:18:57AM +0200, Wolfgang Baer wrote: As the old mod-jk2 stuff (libapache2-mod-jk2) is deprecated upstream I want your opinion on removing it from the archive. 6+ (with me) for the removal. I will therefore request removal of libapache2-mod-jk2 package from archive after libapache2-mod-jk is also build on arm and has propagated to etch. Thanks, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#333164: /usr/share/java/asm-1.5.3.jar: new upstream version available
Alexander Dreweke wrote: Package: libasm-java Version: 1.5.3-2 Severity: normal File: /usr/share/java/asm-1.5.3.jar -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there are libasm-java versions available (http://forge.objectweb.org/projects/asm/) could you please update the package? Hi Alexander, this is not possible as asm is used by groovy. You refer to the new major upstream release 2 which is not compatible with this one. This needs to be packaged as a seperate package e.g. libasm2-java and we will consider this. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
FYI: Bug#332579: Please remove kaffe binaries on mipsel
Hi all, I now requested removal of mipsel binaries form etch so kaffe can propagate to testing once built on the remaining architectures. Wolfgang Original Message Subject: Bug#332579: Please remove kaffe binaries on mipsel Resent-Date: Fri, 07 Oct 2005 07:33:01 UTC Resent-From: Wolfgang Baer [EMAIL PROTECTED] Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Date: Fri, 07 Oct 2005 09:18:46 +0200 From: Wolfgang Baer [EMAIL PROTECTED] Reply-To: Wolfgang Baer [EMAIL PROTECTED], [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Package: kaffe Version: 2:1.1.6-3 Severity: normal Hi, kaffe is broken on mipsel due to a broken jikes on this architecture and the fact that gcj is not yet available. For testing propagation of kaffe it is therefore needed (as far as I understand) that the remaining old binaries from the kaffe source package are removed from testing on mipsel. kaffe on mipsel Version 2:1.1.5-3 binaries: kaffe-jthreads, kaffe-pthread Regards, Wolfgang -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages kaffe depends on: ii kaffe-jthreads2:1.1.6-3 A green threads enabled version of ii kaffe-pthreads2:1.1.6-3 A POSIX threads enabled version of kaffe recommends no packages. -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#227741: kaffe FTBFS on buildd for ARM
Dalibor Topic wrote: Barry Hawkins wrote: Arnaud Vandyck wrote: Dalibor Topic wrote: this may be fixed in 1.1.6-pre2/1.1.6 using ecj for building on arm (and other platforms where jikes screws up royally, like mipsel). Needs to be tried out. Shouldn't we use ecj for all the arches? Since it depends on gcj, I guess the dependency issues are similar to our other options, thought ecj is certainly more active than jikes, no? We need another upload, since there is a FTBFS on arm due to not found ecj again. I'll try to merge in jit3 for Kaffe tonight from pocketlinux, so that would fix the other FTBFS (sparc) too. Yep, arm is no problem - was a typo. For sparc we will use normal jit as a jit3 merge from pocketlinux would be a too big patch for 1.1.6 I assume. And we should first get 1.1.6 as it is into testing ... @Arnaud: I have uploaded a new kaffe revision which should fix the sparc, arm and mips issue. If you think its ÒK it can be uploaded. I wanted to wait for m68k first - however it seems kaffe builds already for 2 days on m68k without and end ... Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#330292: ant refuses to run in background
Hi Carsten, Carsten Pfeiffer wrote: Package: ant Version: 1.6.5-2 Severity: normal Hi, I'm running some Eclipse JUnit tests, that is, an ant-script checks out the test-environment from CVS, builds Plugins, launches an Eclipse workbench and runs the tests inside it. Beside your problem: For Junit tests you have to install ant-optional, as we had a ant reorganization and in the ant package there are only the core tasks now. With the ant 1.6.2 package (as in stable) this works perfectly, 1.6.5 however, can only be run in foreground. I.e. when I start the script from the shell as ant -f testrun.xml it will work just fine. Starting it as ant -f testrun.xml or background a foreground job with bg will quickly make it stop. Well, I cannot reproduce the problem here. I assume it must be some other problem (maybe related to a specific task ...). Please provide us the testrun.xml file so we can test it ourself and see what tasks are you using. Also please give us information which JDK (non-free or free) you are using for ant execution. Simple build files with normal core tasks targets are running for me in the background without problems. Please also test the attached simple buildfile to see if a simple buildfile will succeed in your setup. Thanks, Wolfgang project default=test basedir=. target name=test echohallo/echo /target /project ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Tomcat5 packages
Joel Johnson wrote: I am grateful to see the tomcat5 packages appear and am wondering why 5.0 is being packaged instead of 5.5? I would like to use 5.5 even though it requires a non-free JVM (I'm presuming that's one of the reasons, perhaps 5.0 can be built and run with gjc/kaffe?) Yes, thats the main reason. We will have to upload two more tomcat5 dependencies and a new kaffe package and then tomcat5 can be in main. This want be possible with the 5.5.x version atm. However ones I found some time I will have a look at 5.5.x - however I will only invest time packaging it if it builds/works with free runtimes. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#329245: Minor RFC 2109 / 2965 violation
Hi Joel, Joel Aelwyn wrote: However, while I believe that should make this a 'minor' bug, I do consider it more than 'wishlist' - the early RFCs had strong reasons for establishing 'be conservative in what you send' as well as 'be liberal in what you accept', and fixing this seems likely to be fairly straightforward (though given the state of 3.0RC3, I would, I would expect it may well not show up until 3.0.1 or 3.1 or 4.0 or... whatever comes next). Just received a comment from upstream that its targeted for 3.0 RC4. If you are interested in the followups from upstream: http://issues.apache.org/bugzilla/show_bug.cgi?id=36740 Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Fixed in upload of kaffe 2:1.1.5-pre2-1.1.6-1 to experimental
tag 255502 + fixed-in-experimental tag 305623 + fixed-in-experimental tag 307983 + fixed-in-experimental tag 308256 + fixed-in-experimental tag 308532 + fixed-in-experimental tag 308745 + fixed-in-experimental tag 317162 + fixed-in-experimental quit This message was generated automatically in response to an upload to the experimental distribution. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 19 Sep 2005 20:57:09 +0200 Source: kaffe Binary: kaffe-dev kaffe-common kaffe-pthreads kaffe-doc kaffe jikes-kaffe kaffe-jthreads Architecture: source all powerpc Version: 2:1.1.5-pre2-1.1.6-1 Distribution: experimental Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: jikes-kaffe - Wrapper for jikes using Kaffe classes kaffe - A JVM to run Java bytecode kaffe-common - Files shared between all Kaffe VM versions kaffe-dev - Header files and other resources for building against Kaffe kaffe-doc - Documentation for the Kaffe VM kaffe-jthreads - A green threads enabled version of the Kaffe VM kaffe-pthreads - A POSIX threads enabled version of the Kaffe VM Closes: 255502 305623 305623 307983 308256 308532 308745 317162 Changes: kaffe (2:1.1.5-pre2-1.1.6-1) experimental; urgency=low . * New upstream prerelease fixing bugs: + Upstream now uses nio libs instead of KaffeEncoder (closes: #308256) + Incorrect computation results resolved upstream (closes: #255502) + getMethodSignatureClass: Assertion `class-state = CSTATE_DOING_LINK' does no longer fail - tested with the provided testcase (closes: #308532) + Tomcat4 / kaffe SecurityManager issues resolved (closes: #308745) + java.nio.FileChannelImpl.lock() implemented (closes: #305623) + setting java.util.logging.Logger handlers works now (closes: #307983) + Un/compress contentlenght problem with HttpURLConnection fixed upstream (closes: #317162) + java/lang/Runtime.availableProcessors() implemented (closes: #305623) * Updated copyright to reflect newly included stuff in kaffe * Dropped pthreads-profile on i386 as profiling over JVMPI is now supported on all platforms - updated everything * Updated FileActions to reflect the recent move of tools.jar * Added lintian override for kaffe: binary-without-manpage as the manpage is available in another package which depends on kaffe * Reworked configure options for pthreads system + --enable-jvmpi for profiling + --enable-gtk-cairo for building against cairo, added libcairo2-dev as build depends to debian/control * Reworked engine options + Use interpreter by default + JIT is enabled in the arch-specific rule files (only i386, sparc atm) Files: 634f67893e61164c8e44c7056ba1516b 1139 interpreters optional kaffe_1.1.5-pre2-1.1.6-1.dsc c14a438523405f65f92b056e7cd80194 1076 interpreters optional kaffe_1.1.5-pre2-1.1.6.orig.tar.gz d66429bb4bdbe01f611a5c12b856f4ba 30762 interpreters optional kaffe_1.1.5-pre2-1.1.6-1.diff.gz 3a456fcff9d5162405f35aca9f8933e6 50564 interpreters optional kaffe_1.1.5-pre2-1.1.6-1_all.deb 81ac43cbbb7fce83ef0f30b77036b764 7424416 interpreters optional kaffe-common_1.1.5-pre2-1.1.6-1_all.deb 903420bcceeb50c397052b479354934d 66034 interpreters optional kaffe-dev_1.1.5-pre2-1.1.6-1_all.deb e2d3292c657c959ce63f85e686daa6fa 49166 interpreters optional jikes-kaffe_1.1.5-pre2-1.1.6-1_all.deb 00c2b1219b32bacb5657c3663c7939fe 136418 interpreters optional kaffe-doc_1.1.5-pre2-1.1.6-1_all.deb 0bbf187d5ff232fcc331db2556d762b4 413954 interpreters optional kaffe-jthreads_1.1.5-pre2-1.1.6-1_powerpc.deb cd4f901b1b548bebb8f97ef72e07cfc1 558164 interpreters optional kaffe-pthreads_1.1.5-pre2-1.1.6-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD4DBQFDLzmn4vzFZu62tMIRAqcvAJjfqTtUy4xObGFGL165QRI/AARIAKCYTYTp f2XtqJQiYHTHrVauKIgqbg== =VOHO -END PGP SIGNATURE- ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
FYI: Packages already transitioned / in work
Hi all, as I am away over weekend and to not duplicate work. I have the following packages already ready on disk or will work on some during my train ride to southern germany: Ready: jcifs libjdom1-java mysql-connector-java Will work on: commons-beanutils (will do a new upstream) libcommons-collections3-java (will do a new upstream) libregexp-java (will do a new upstream) tomcat5 (preparing move to main) Also note the packages I will take care of in the ant mail before. Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#328328: kaffe-pthreads: jar systematically throws NullPointerException
Hi Yann, Yann Dirson wrote: Package: kaffe-pthreads Version: 2:1.1.5-cvs20050808-2 Severity: grave In the sid chroot on escher: $ /usr/lib/kaffe/pthreads/bin/jar Internal error: caught an unexpected exception. Is only jar failing or also the other ones in /usr/lib/kaffe/pthreads/bin/ ? Regards, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#327790: tomcat5-webapps: jsp svg example links to the wrong url
Hi Pablo, Pablo Barbachano wrote: http://localhost:8180/jsp-examples/jsp2/jspx/svgexample.html points to this other URL: http://localhost:8080/jsp-examples/jsp2/jspx/textRotate.jspx?name=JSPX The port is wrong. I think the correct way to fix is to change it to: a href=/jsp-examples/jsp2/jspx/textRotate.jspx?name=JSPX ... /a ... so it takes the correct basedir. There might be some other issues likes this as debian changes the default port of tomcat to 8180 (upstream uses 8080). In a next upload I will patch it to a relative url. If you find/found other non-relative links please report them here so they can be fixed all at once. Thanks for reporting, Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#327354: libbatik-java: Batik doesn't bring pdf-transcoder.jar but doesn't work either with fop.
Hi Eric, Michael, Wolfgang Baer wrote: Michael Koch wrote: On Fri, Sep 09, 2005 at 03:17:30PM +0200, Wolfgang Baer wrote: See http://wiki.apache.org/xmlgraphics/XmlGraphicsCommonComponents for the problem and the upcomming solution. Can we include its sources as patch so they get compiled together with batik? This will be a huge patch - I would place the sources in a debian subdirectory. Will be around 200-400 kB source. Then its easy to remove this patch again when newer batik version dont need it anymore. Not a new batik version. A newer fop version would be needed to drop these patches (assuming the will be applied). Just an idea, maybe no possible at all. Yes thats possible - however one has to find the correct sources somewhere in the CVS. I am sure we can ask on the upstream ML to get them at least by email. I found the correct tag in upstream as I remembered an email on the fop list asking for tagging fop at the time batik checked out the pdf transcoder stuff. This however will need also an update of batik to 1.6. Eric, I will have a look into it as soon as I find time ... Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
[Fwd: ftp.debian.org: Please remove libant1.5-java from the archive]
Hi all, I now filed the removal bug for libant1.5-java as this is now long overdue. Wolfgang Original Message Subject: ftp.debian.org: Please remove libant1.5-java from the archive Date: Sat, 10 Sep 2005 23:25:11 +0200 From: Wolfgang Baer [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Package: ftp.debian.org Severity: normal Hi, please remove libant1.5-java (please note _1.5_) from the archive. Its decided already a long time by pkg-java maintainers and now only one package (with a bug open for over 100 days) build-deps on it. Its superceeded by libant1.6-java and ant (which is now in main). We will do an NMU of the last build-dep package if libant1.5-java is removed and I will take care of reassigning open bugs etc. Thanks, Wolfgang -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Tomcat5
Hi all, tomcat5 is now function in unstable - the last upload resolved the remaining issues. There is currently still an upstream problem in GNU classpath which prevents running tomcat5 with the security manager and kaffe. I used user tags to tag the bugs of tomcat4 which are fixed in tomcat5. So we will now which bugs can be closed if at some time tomcat4 will be removed from the archive and the bugs needs to be reassigned to tomcat5. I tagged with our pkg-java-maintainers email address and the tag fixed_in_tomcat5: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=tomcat4;[EMAIL PROTECTED] Wolfgang ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
