-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This bug should have been close with new upload of kaffe
- --
Arnaud http://www.ressource-toi.org
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with
Michael Koch wrote:
On Thu, Jul 07, 2005 at 11:20:19PM +0200, Andreas Krüger wrote:
[...]
For Sarge its too late to change this. Your best option is to use a backport
of kaffe from testing/unstable. I will soon start to create them when kaffe
get uploaded in a new version.
Hi Michael, I
On Fri, Jul 08, 2005 at 09:24:31AM +0200, Wolfgang Baer wrote:
Michael Koch wrote:
On Thu, Jul 07, 2005 at 11:20:19PM +0200, Andreas Krüger wrote:
[...]
For Sarge its too late to change this. Your best option is to use a backport
of kaffe from testing/unstable. I will soon start to
On Thu, Jul 07, 2005 at 11:20:19PM +0200, Andreas Krüger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Koch wrote:
You are really suggesting to deactivate the security manager by default?
What I really suggest is: When I install Sarge Tomcat on a Sarge box,
together
On Sat, Jul 02, 2005 at 03:48:47AM +0200, Andreas Krüger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: tomcat4
Version: 4.1.31-3
Severity: normal
I installed tomcat4 and tomcat4-admin on a Sarge machine.
That machine is a server and has few other software
packages
5 matches
Mail list logo