Your message dated Tue, 28 Jun 2005 20:26:26 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#269940: fixed in zope 2.6.4-2
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Sep 2004 12:31:59 +0000
>From [EMAIL PROTECTED] Sat Sep 04 05:31:59 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C3Zi3-0002cg-00; Sat, 04 Sep 2004 05:31:59 -0700
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id OAA05302
for <[EMAIL PROTECTED]>; Sat, 4 Sep 2004 14:31:57 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 59C89F21D
for <[EMAIL PROTECTED]>; Sat, 4 Sep 2004 14:31:57 +0200 (MEST)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
id 24787-26 for <[EMAIL PROTECTED]>;
Sat, 4 Sep 2004 14:31:57 +0200 (MEST)
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP
for <[EMAIL PROTECTED]>; Sat, 4 Sep 2004 14:31:57 +0200 (MEST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id i84CVuBk010237;
Sat, 4 Sep 2004 14:31:56 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 4 Sep 2004 14:31:56 +0200
To: [EMAIL PROTECTED]
Subject: install failure on new installs
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: zope
Version: 2.6.4-1.5
Severity: serious
Fails on new installs, if you answer the question that it should move
existing instances with:
Setting up zope (2.6.4-1.5) ...
touch: cannot touch `/var/lib/zope/instance/default/access': No such file or
directory
dpkg: error processing zope (--configure):
subprocess post-installation script returned error exit status 1
---------------------------------------
Received: (at 269940-close) by bugs.debian.org; 29 Jun 2005 00:39:54 +0000
>From [EMAIL PROTECTED] Tue Jun 28 17:39:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DnQcM-0007Xv-00; Tue, 28 Jun 2005 17:39:54 -0700
Received: from jeroen by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DnQPK-0000ox-00; Tue, 28 Jun 2005 20:26:26 -0400
From: Fabio Tranchitella <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: lisa $Revision: 1.30 $
Subject: Bug#269940: fixed in zope 2.6.4-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Jeroen van Wolffelaar <[EMAIL PROTECTED]>
Date: Tue, 28 Jun 2005 20:26:26 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 21
Source: zope
Source-Version: 2.6.4-2
We believe that the bug you reported is fixed in the latest version of
zope, which is due to be installed in the Debian FTP archive:
zope2.6_2.6.4-2_i386.deb
to pool/main/z/zope/zope2.6_2.6.4-2_i386.deb
zope_2.6.4-2.diff.gz
to pool/main/z/zope/zope_2.6.4-2.diff.gz
zope_2.6.4-2.dsc
to pool/main/z/zope/zope_2.6.4-2.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabio Tranchitella <[EMAIL PROTECTED]> (supplier of updated zope package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 16 Jun 2005 10:42:07 +0000
Source: zope
Binary: zope2.6
Architecture: source i386
Version: 2.6.4-2
Distribution: unstable
Urgency: high
Maintainer: Debian Zope team <[EMAIL PROTECTED]>
Changed-By: Fabio Tranchitella <[EMAIL PROTECTED]>
Description:
zope2.6 - open source web application server
Closes: 220370 222443 226818 227534 230216 232649 233749 237064 240774 244049
246991 250154 256615 267384 267384 267528 267667 267673 267752 267858 267925
269940 271092 271092 273504 276032 278592 298323 305270 306542 312536
Changes:
zope (2.6.4-2) unstable; urgency=low
.
* New maintainer.
* debian/control: package renamed to zope2.6.
* debian/TODO.Debian: removed.
* debian/po/ja.po: updated. (Closes: #312536)
* debian/po/fr.po: updated. (Closes: #306542)
.
zope (2.6.4-1.8) unstable; urgency=low
.
* NMU.
* debian/zope.init: removed bashism. (Closes: #305270)
.
zope (2.6.4-1.7) unstable; urgency=medium
.
* NMU, let's try to keep zope in a good shape for sarge release, maintainer
seems to be MIA (credits for this NMU go to Fabio Tranchitella).
* Urgency set to medium to make sure we make sarge.
* debian/po/ja.po: updated. (Closes: #271092)
* debian/po/de.po: updated. (Closes: #271092)
* debian/po/cz.po: added. (Closes: #273504)
* debian/zope.postrm: don't remove the user zope on remove, and let
zope2.7 use it. (Closes: #256615)
* debian/zope.config: Don't ask about instance home moving on fresh
install. (Closes: #232649)
* debian/: removed CVS directory (and make lintian happier).
* debian/README.Debian: fixed typo. (Closes: #298323)
* debian/patches: debian specific patches should be separated from the
original source tree.
* debian/patches/DateTime.dpatch: applied patch from zope-book to fix
the wrong DateTime.py shipped by zope 2.6.4. (Closes #224256)
* debian/README.Debian: Added a note about default HTTP port.
(Closes: #246991)
* debian/zope.logrotate: don't send useless emails.
(Closes: #240774, #226818)
* debian/zope.prerm: make sure to delete all .pyc and .pyo on upgrade.
(Closes: #237064)
* debian/zope.config, debian/zope.postinst: use debconf to configure the
initial admin user. (Closes: #230216, #220370, #278592, #276032)
* Added lintian/linda overrides for image-in-usr-lib warnings.
* debian/zope.default, debian/zope.init: modified to be consistent with
zope2.7 and debian zope packaging team: now INSTANCES="" means NONE.
* debian/rules: don't ship Debian Zope Policy, it's obsolete.
.
zope (2.6.4-1.6) unstable; urgency=high
.
* NMU
[This NMU has been prepared by Thaddeus H. Black <[EMAIL PROTECTED]>]
* Further fix /var/lib/zope/instance/default/access
(Closes: #267384)
* In postinst, because stdin is not connected directly to the
terminal, take password input from /dev/tty instead
.
zope (2.6.4-1.5.1) unstable; urgency=high
.
* Non-Maintainer Upload.
* Fix postinst to check for "true" instead of "yes" from debconf.
Also updated the default value in the template to "true" (fixes
lintian warning and ensures the problem won't surface again
suddenly). (Closes: #269940)
.
zope (2.6.4-1.5) unstable; urgency=high
.
* Fix /var/lib/zope/instances/default/access introcuced in 2.6.4.-1.2
* Remove -v swith to debiandoc2* tetex-base bug is now fixed
* Add pt_BR po-debconf translation (closes: #267925)
.
zope (2.6.4-1.4) unstable; urgency=high
.
* NMU
* Add -v to debiandoc2* to help debugging #267413) (closes: #267752)
* Update Danish, German and Japanese po-debconf translations
(closes: #267667, #267673, #267858)
.
zope (2.6.4-1.3) unstable; urgency=high
.
* NMU
* Test if /var/lib/zope/instance/default/access exists before creating it
(closes: #267528)
.
zope (2.6.4-1.2) unstable; urgency=high
.
* NMU (0-DAY NMU Sarge must be released)
[This NMU has been prepared by Thaddeus H. Black <[EMAIL PROTECTED]>]
* Pursuant to bug #251038 (filed against zopectl),
- fixed "/usr/lib/zope/zpasswd.py --username [username] [filename]"
so that it responds rationally when a username is given without a
password; then (closes: #267384)
- scripted debian/zope.postinst properly to create an
initial/emergency user, with proper regard for the configuration
in zopectl's /etc/zopectl/zopectlrc.
* Change Depends on zopectl (>=0.3.4.2)
* Add Japanese po-debconf translation (closes: #227534)
* Add Danish po-debconf translation (closes: #233749)
* Add Catalan po-debconf translation (closes: #250154)
* Update French po-debconf translation (closes: #244049)
.
zope (2.6.4-1.1) unstable; urgency=high
.
* NMU to help keep zope in sarge.
* debian/zope.logrotate: remove the 'copytruncate' and 'notifempty'
options, so logrotate actually creates the new log files (with the
already-specified correct ownership and permissions) before it calls
zopectl --logrotate.
Closes: #222443 "zopectl logrotate" leads to zope instances crash
Files:
a9f2881985c5a1deb5178c7ad19bcba2 844 web optional zope_2.6.4-2.dsc
b9b54ed94f1e1fa6b64785c9528af152 46249 web optional zope_2.6.4-2.diff.gz
e1e8d11681af56e289f59fea9a26f91d 2518534 web optional zope2.6_2.6.4-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCsWleK/juK3+WFWQRAk++AKCEbmuYUblEwDPC9m5DogFTrsb9HQCgkuMj
8R/DmEDCsiXeqsd2SZya+kQ=
=6AAi
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
