Your message dated Tue, 13 Dec 2011 07:03:55 +0000
with message-id <e1ramp5-0004aw...@franck.debian.org>
and subject line Bug#650656: fixed in tomcat6 6.0.35-1
has caused the Debian Bug report #650656,
regarding tomcat6: Error in debian/rules causes tomcat to report no version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
650656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

--- Begin Message ---

Package: tomcat6
Version: 6.0.28-9+squeeze1
Severity: normal
Tags: patch
Hello,
The tomcat6 packaged in debian reports no version. This can be seen executing:
$ /usr/share/tomcat6/bin/version.sh
Which results in:
Using CATALINA_BASE: /usr/share/tomcat6
Using CATALINA_HOME: /usr/share/tomcat6
Using CATALINA_TMPDIR: /usr/share/tomcat6/temp
Using JRE_HOME: /usr
Using CLASSPATH: /usr/share/tomcat6/bin/bootstrap.jar
Server version: Apache Tomcat/6.0.28
Server built: February 12 2011 1443
Server number: ...0
OS Name: Linux
OS Version: 2.6.32-5-amd64
Architecture: amd64
JVM Version: 1.6.0_18-b18
JVM Vendor: Sun Microsystems Inc.
The server number should contain "6.0.28.0".
This doesn't seem to affect functionality, but it does affect the integration
of
tomcat with other development tools. For example, netbeans 7.0.1 refuses to
use this tomcat installation to deploy webapps as it can't determine the
version.
I've dug into it and found that the version number is fed to the build system
in the ant command line in the debian/rules script. The version is read from
the changelog, but then it's wrongly parsed into major/minor/build versions.
I've attached the patch I used to solve it.
I can confirm this happens in the tomcat6 packages in both squeeze and wheezy,
as well as in the tomcat7 packages from unstable and testing. I'll file another
bug report against it if needed.
--
Jorge Barreiro González
aCore
jbarre...@acore.es
http://www.acore.es
Tel. 881 927 189