Bug#418962: tomcat5.5: Should not use relative symlinks

[Marcus Better]

severity 418962 normal
thanks

 Severity: grave
 Justification: renders package unusable

That's stretching it a bit, no? The default install works.

 If a users such as myself makes CATALINA_BASE some other directory like
 /srv/tomcat5.5, any upgrade of the product will delete the symlinks and
 replace them with the relative links above... breaking the tomcat
 installation.

Please explain this. If you redefine CATALINA_BASE, you need to create your 
own directory hierarchy in, e.g., /srv/tomcat5.5, with its own log directory. 
The original files in /var/lib/tomcat5.5 should not matter and can be left as 
they are. Upgrading the package will certainly not alter anything under /srv.

I'll try for myself and see what happens...

(In general, you can use dpkg-divert to move files belonging to packages so 
that the original files aren't touched by upgrades. But this shouldn't be 
necessary in this case.)

Marcus


pgpXXrgB2HxZM.pgp
Description: PGP signature

Processed: Re: Bug#418962: tomcat5.5: Should not use relative symlinks

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 severity 418962 normal
Bug#418962: tomcat5.5: Should not use relative symlinks
Severity set to `normal' from `grave'

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#418962: tomcat5.5: Should not use relative symlinks

[Mike Young]

Package: tomcat5.5
Version: 5.5.20-4
Severity: grave
Justification: renders package unusable


The installation of tomcat5.5 uses relative symlinks in many places 
including in the directories under CATALINA_BASE.
Example:
conf
logs - ../../log/tomcat5.5
shared
temp
webapps
work - ../../cache/tomcat5.5

This assumes that CATALINA_BASE is always going to be set to 
/var/lib/tomcat5.5

If a users such as myself makes CATALINA_BASE some other directory like 
/srv/tomcat5.5, any upgrade of the product will delete the symlinks and 
replace them with the relative links above... breaking the tomcat 
installation.

tomcat5.5 SHOULD NOT assume that a user-modifiable parameter is going to 
be at a set location every time.
I believe that tomcat5.5 CAN assume that certain configuration items are 
going to be in their correct debian places, and should always use 
fully qualified symlinks.

So, logs should point to /var/log/tomcat5.5
work should point to /var/cache/tomcat5.5
and the other links in the installtion (there are some in the conf 
directories that intend to point to /etc/tomcat5.5) should be corrected 
as well.

As it stands, there is no way to upgrade the installtion of tomcat5.5 if 
the user chooses a different CATALINA_BASE

--Mike

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tomcat5.5 depends on:
ii  adduser  3.102   Add and remove users and groups
ii  ecj-bootstrap3.2.1-6 standalone version of the Eclipse 
ii  gij [java2-runtime]  4:4.1.1-15  The GNU Java bytecode interpreter
ii  gij-4.1 [java2-runti 4.1.1-20The GNU Java bytecode interpreter
ii  ibm-j2sdk1.5 [java2- 1.5.0   Java(TM) JDK, Standard Edition, IB
ii  java-gcj-compat-dev  1.0.65-10   Java runtime environment with GCJ
ii  jsvc 1.0.2~svn20061127-4 wrapper to launch Java application
ii  libtomcat5.5-java5.5.20-4Java Servlet engine -- core librar
ii  sun-java5-jre [java2 1.5.0-11-1  Sun Java(TM) Runtime Environment (

tomcat5.5 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]