Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-11 Thread Jeroen van Wolffelaar
severity 300209 serious thanks On Thu, Apr 07, 2005 at 02:37:30AM -0400, Jeff Breidenbach wrote: severity 300209 important stop This package works for me. Therefore at most the severity is important which is defined as a bug which has a major effect on the usability of a package, without

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-11 Thread Jeroen van Wolffelaar
tags 300209 + pending thanks On Fri, Apr 08, 2005 at 07:06:28AM -0400, Barry Hawkins wrote: Thanks for the information. I was afraid it was something of that nature. Since Blackdown 1.3 and IBM 1.4 are what's available for PowerPC right now, I am not able to build this package without

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-08 Thread Wolfgang Baer
Barry Hawkins wrote: [...] Guys, I have committed a debian/control file for the tomcat4 package that imposes both build (tomcat4 source) and runtime(tomcat4 binary) dependencies the following library versions: libcommons-digester-java = 1.5.0.1 libcommons-collections-java = 2.1.1

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-08 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wolfgang Baer wrote: Barry Hawkins wrote: [...] The following error occurred while executing this line: java.lang.UnsupportedClassVersionError: org/apache/commons/dbcp/ConnectionFactory (Unsupported major.minor version 48.0) Hi Barry,

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-08 Thread Kalle Kivimaa
Barry Hawkins [EMAIL PROTECTED] writes: classes that IBM does not have. So, if Arnaud or Stefan could build tomcat4 with what I have checked in and sponsor an upload, we will likely have resolved this issue and gotten tomcat4 back into Sarge. I'm trying to do this but as amd64 port is missing

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-08 Thread Kalle Kivimaa
Kalle Kivimaa [EMAIL PROTECTED] writes: I'm trying to do this but as amd64 port is missing some libraries (why, I have no idea) I'm having a slight difficulty with it. So, if Stefan/Arnaud beat me to it, feel free. Barry's changes looked fine to me and I tagged the HEAD already. Oh well, I

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Steve Langasek
On Thu, Apr 07, 2005 at 01:09:33AM -0400, Jeff Breidenbach wrote: The java packing team just got blindsided by bug #300209, which appears to have knocked tomcat4 out of Sarge. Heads up that you may hear some begging for re-inclusion in the near future. You mean there's no chance that people

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread killer
On Wed, Apr 06, 2005 at 10:55:12PM -0400, Barry Hawkins wrote: Could you tell us which version of libcommons-collections-java you have installed on this machine? On my powerpc sid install, I currently have: I took a look into the offending line of source and noticed that a null value is

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread killer
On Wed, Apr 06, 2005 at 10:55:12PM -0400, Barry Hawkins wrote: Could you tell us which version of libcommons-collections-java you have installed on this machine? On my powerpc sid install, I currently have: Right, this problem is caused by the ArrayStack.java with the Jakarta CVS version

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Kalle Kivimaa
Wolfgang Baer [EMAIL PROTECTED] writes: IMHO this bug can be closed as it is not related to a testing or unstable installation, nor a woody installation ! If you can end up with the problem using simply apt-get, then it is a real bug and needs to be fixed. I'm going to do it today, so if

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Wolfgang Baer
Kalle Kivimaa wrote: Wolfgang Baer [EMAIL PROTECTED] writes: IMHO this bug can be closed as it is not related to a testing or unstable installation, nor a woody installation ! If you can end up with the problem using simply apt-get, then it is a real bug and needs to be fixed. I'm going to do it

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Christoph Martin
Hi all, Wolfgang Baer schrieb: It seems as this is a mixed woody/testing/unstable/experimental installation. According to the System Information its woody 3.0 ! adduser is the woody version. apache-utils is the sarge version So this is not a bug in tomcat4 - just a mixed installation

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Christoph Martin
Christoph Martin schrieb: Hi. I just tested it on the other machines. After the update it is *working* on two more machines. So, I think this is fix. It is still *not* working on one other machine. I will investigate this special web application and its .jar files in WEB-INF/lib. Especially

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Kalle Kivimaa
Christoph Martin [EMAIL PROTECTED] writes: Ok. In jars.jar org/apache/commons/collections/ is included. Does someone know how I check the version in a .jar file? That's a bit difficult unless the jar file contains either a well written META-INF file or a version file... I think you need to

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Langasek wrote: On Thu, Apr 07, 2005 at 01:09:33AM -0400, Jeff Breidenbach wrote: The java packing team just got blindsided by bug #300209, which appears to have knocked tomcat4 out of Sarge. Heads up that you may hear some begging for

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Christoph Martin
Kalle Kivimaa schrieb: Christoph Martin [EMAIL PROTECTED] writes: Ok. In jars.jar org/apache/commons/collections/ is included. Does someone know how I check the version in a .jar file? That's a bit difficult unless the jar file contains either a well written META-INF file or a version

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Martin wrote: [...] I removed all the .jar files in the application and tomcat is still crashing. So I don't know what to check now to find the error. Any suggestions? [...] How about: $ dpkg -l libcommons-collections-java That should

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Christoph Martin
Barry Hawkins schrieb: Christoph Martin wrote: [...] I removed all the .jar files in the application and tomcat is still crashing. So I don't know what to check now to find the error. Any suggestions? [...] How about: $ dpkg -l libcommons-collections-java That should work unless you

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Martin wrote: [...] As I already said, I checked that before looking for other locations. It even happens if I remove my webapp. Then it happens in the default context and in webdav etc. BTW.: Which version of java do you use with

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-07 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wolfgang Baer wrote: Kalle Kivimaa wrote: Wolfgang Baer [EMAIL PROTECTED] writes: [...] If you can end up with the problem using simply apt-get, then it is a real bug and needs to be fixed. I'm going to do it today, so if somebody violently

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-06 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Martin wrote: [...] This is totally independent of the contents of the web.xml file. I even exchanged the files with the contents of /usr/share/tomcat4/.debian/web.xml but to no avail. Something seams to have changed between 4.1.30 and

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-06 Thread Barry Hawkins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Barry Hawkins wrote: [...] Could you tell us which version of libcommons-collections-java you have installed on this machine? On my powerpc sid install, I currently have: $ dpkg -l libcommons-collections-java

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-04-06 Thread Jeff Breidenbach
Hi Sarge release team, The java packing team just got blindsided by bug #300209, which appears to have knocked tomcat4 out of Sarge. Heads up that you may hear some begging for re-inclusion in the near future. Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade

2005-03-18 Thread Christoph Martin
Package: tomcat4 Version: 4.1.31-2 Severity: grave Justification: renders package unusable I tried to update tomcat4 on different servers from 4.1.30 to 4.1.31. Now all my webapps are not running anymore. I get the following error and tomcat dies: 2005-03-18 11:52:46