Your message dated Sat, 25 May 2013 17:53:10 +0300 (EEST) with message-id <[email protected]> and subject line Closing old bugs filed against tomcat5.5 (or related packages) has caused the Debian Bug report #418962, regarding tomcat5.5: Should not use relative symlinks 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 [email protected] immediately.) -- 418962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418962 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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-bootstrap 3.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-20 The 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-java 5.5.20-4 Java 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
--- End Message ---
--- Begin Message ---Version: 5.5.26-5 Hello, Some (long) time ago you filed this bug against tomcat5.5 or a related package. In the meantime the tomcat5.5 package has been renamed and this bug was "lost". Since the bug is already quite old now it is being closed. If the issue you encountered is still present in recent tomcat packages (as released with Debian 7.0 wheezy for example) the maintainer(s) would very much appreciate a fresh report using: reportbug <package> You should also mention the number of this bug if you think it contains valuable information. Please note that further information sent to this bug is likely to remain unread, because the bug is currently not assigned to any existing package. Thank you for for trying to improve Debian by reporting bugs. Kind regards, Andrei (with no relation to tomcat maintenance)
--- End Message ---
