Your message dated Thu, 28 Jun 2007 12:52:52 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing old apt-proxy bugreport which is fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: apt-proxy
Version: 1.9.25
Severity: minor
apt-proxy.log is owned by aptproxy:nogroup. I generally add users to
the adm group to be able to read logs in /var/log, but this doesn't get
them access to the apt-proxy log, which is inconvenient.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages apt-proxy depends on:
ii bzip2 1.0.2-1 A high-quality block-sorting file
ii debconf 1.4.30.11 Debian configuration management sy
ii logrotate 3.7-2 Log rotation utility
ii python 2.3.4-5 An interactive high-level object-o
ii python-apt 0.5.10 Python interface to libapt-pkg
ii python-bsddb3 3.3.0-6 Python interface to libdb3
ii python-twisted 1.3.0-6 Event-based framework for internet
-- debconf information:
* apt-proxy/upgrading-v2:
* apt-proxy/upgrading-v2-result:
--- End Message ---
--- Begin Message ---
Hello,
My apt-proxy, version 1.9.36, creates log files for the group adm.
So bugreport #294329 is fixed.
And while this BR getting an update for two years,
I'm now closing it.
Cheers
Geert Stappers
--- End Message ---
