Your message dated Tue, 18 Nov 2008 20:50:02 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Closing old zope bugs
has caused the Debian Bug report #244644,
regarding Logrotate still makes zope unusable
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.)


-- 
244644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=244644
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: zope
Version: 2.6.4-1.1
Severity: normal

As subject says.  The problem is known and persisted even after recent update.
Attached is a workaround patch which is most probable not acceptable for
distribution (i.e. stop zope before 'zopectrl logrotate' and restart
afterwards).

Furthermore a wishlist item for zope:  Please make root.adm the owner of
zope's logfiles as is in most other packages.


cheers,

andreas


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages zope depends on:
ii  adduser                     3.52         Add and remove users and groups
ii  debconf                     1.4.21       Debian configuration management sy
ii  dpkg                        1.10.20      Package maintenance system for Deb
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  python2.2                   2.2.3-9      An interactive high-level object-o
ii  python2.2-xml               0.8.3-5      XML tools for Python (2.2.x)
ii  zopectl                     0.3.4.1      Zope instances controlling utility

-- debconf information:
* zope/instance_home/move: true
  zope/upgrade/2.6.1-7:
* shared/zope/restart: end

--- /etc/logrotate.d/zope.dpkg-new	2004-04-19 10:43:42.000000000 +0200
+++ /etc/logrotate.d/zope	2004-02-24 14:06:53.000000000 +0100
@@ -25,12 +25,17 @@
 	weekly
 	missingok
 	rotate 52
+	copytruncate
 	compress                                                      
 	delaycompress
+	notifempty   
 	create 640 zope zope
 	sharedscripts
+	prerotate
+		/etc/init.d/zope stop
+	endscript
 	postrotate
-        zopectl logrotate
-#       invoke-rc.d apache reload > /dev/null
+#        	zopectl logrotate
+		/etc/init.d/zope start
 	endscript
 }

--- End Message ---
--- Begin Message ---
Hello,

I'm closing this bug report because it refers to the old zope (2.6) package
and the current zope in testing/unstable (2.10) doesn't show this problem.

-- 
Fabio Tranchitella                         http://www.kobold.it
Free Software Developer and Consultant     http://www.tranchitella.it
_____________________________________________________________________
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564


--- End Message ---

Reply via email to