Your message dated Tue, 11 Apr 2006 01:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#361666: fixed in zope-atcontenttypes 1.0.3-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)
--- Begin Message ---
Package: zope-atcontenttypes
Version: 1.0.3-1
Severity: wishlist
To change defaults for AT contenttypes one has to copy
ATCT/etc/atcontenttypes.conf.in to INSTANCE_HOME/etc/atcontenttypes.conf
and edit the file. In the Debian case this can also be
/etc/zopeX.X/<instance>
Because of the way debian installs instances it is
not obvious where to find this file. The original file is actually in
/usr/share/zope/Products/ATContentTypes/etc/atcontenttypes.conf.in
It would be handy if zope-atcontenttypes would copy this file to
/etc/zopeX.X/<instance> when running dzhandle.
Or else at least a mention of the file in a README.Debian is in order.
Yours,
Gerrit Jan.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages zope-atcontenttypes depends on:
ii python2.3-imaging 1.1.5-4 Python Imaging Library
ii zope-archetypes 1.3.7-1 framework for developing and deplo
ii zope-cmfplone 2.1.2-1 content management system based on
ii zope-common 0.5.21 common settings and scripts for zo
ii zope2.8 2.8.6-1 Open Source Web Application Server
zope-atcontenttypes recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: zope-atcontenttypes
Source-Version: 1.0.3-2
We believe that the bug you reported is fixed in the latest version of
zope-atcontenttypes, which is due to be installed in the Debian FTP archive:
zope-atcontenttypes_1.0.3-2.diff.gz
to pool/main/z/zope-atcontenttypes/zope-atcontenttypes_1.0.3-2.diff.gz
zope-atcontenttypes_1.0.3-2.dsc
to pool/main/z/zope-atcontenttypes/zope-atcontenttypes_1.0.3-2.dsc
zope-atcontenttypes_1.0.3-2_all.deb
to pool/main/z/zope-atcontenttypes/zope-atcontenttypes_1.0.3-2_all.deb
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-atcontenttypes
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: Tue, 11 Apr 2006 10:23:08 +0200
Source: zope-atcontenttypes
Binary: zope-atcontenttypes
Architecture: source all
Version: 1.0.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian/Ubuntu Zope Team <[EMAIL PROTECTED]>
Changed-By: Fabio Tranchitella <[EMAIL PROTECTED]>
Description:
zope-atcontenttypes - archetypes-based replacement for Plone/CMF types
Closes: 361666
Changes:
zope-atcontenttypes (1.0.3-2) unstable; urgency=low
.
* Added README.Debian with a note about atcontenttypes.conf.
(Closes: #361666)
Files:
928dd1977e89674630540d5cb54769af 733 web optional
zope-atcontenttypes_1.0.3-2.dsc
93a528e84bf3c6024e93834543373239 2228 web optional
zope-atcontenttypes_1.0.3-2.diff.gz
bde2aeaca76e711f11d233d74df33e25 280472 web optional
zope-atcontenttypes_1.0.3-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEO2h4K/juK3+WFWQRAmTPAJ9bZ0wlBiQuEvm04sikpymgI7cpYwCdEawh
Vs1UuE37Uc9VH4tDmFYVYDs=
=Etpq
-----END PGP SIGNATURE-----
--- End Message ---
