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 #485600,
regarding the log files in /var/log/tomcat5.5/ should be belong to the group adm
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.)


-- 
485600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485600
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tomcat5.5
Version: 5.5.26-3
Severity: minor


The log files in /var/log/tomcat5.5/ should have the same group
permissions as the other log files in the debian system

-rw-r----- tomcat55 adm

Kind regards,
Detlev Brodowski

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

Kernel: Linux 2.6.25-2-db-vostro (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tomcat5.5 depends on:
ii  adduser              3.108               add and remove users and groups
ii  jsvc                 1.0.2~svn20061127-9 wrapper to launch Java application
ii  libecj-java          3.3.0+0728-9        Eclipse Java compiler (library)
ii  libtomcat5.5-java    5.5.26-3            Java Servlet engine -- core librar
ii  sun-java5-jre [java2 1.5.0-15-1          Sun Java(TM) Runtime Environment (
ii  sun-java6-jre [java2 6-06-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 ---

Reply via email to