Your message dated Wed, 06 Apr 2005 13:32:28 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#231621: fixed in pyblosxom 1.2-1
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; 7 Feb 2004 21:28:38 +0000
>From [EMAIL PROTECTED] Sat Feb 07 13:28:38 2004
Return-path: <[EMAIL PROTECTED]>
Received: from cpe00062579efac-cm014260028338.cpe.net.cable.rogers.com
(outpost.dnsalias.org) [65.49.88.87]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Apa0E-0001mG-00; Sat, 07 Feb 2004 13:28:38 -0800
Received: from outpost.dnsalias.org (localhost [127.0.0.1])
by outpost.dnsalias.org (8.12.11/8.12.11/Debian-1) with ESMTP id
i17LSakd002557;
Sat, 7 Feb 2004 16:28:36 -0500
Received: (from [EMAIL PROTECTED])
by outpost.dnsalias.org (8.12.11/8.12.11/Debian-1) id i17LSavN002556;
Sat, 7 Feb 2004 16:28:36 -0500
Message-Id: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jeff Bailey <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Version number should not be in config.py
X-Mailer: reportbug 2.42
Date: Sat, 07 Feb 2004 16:28:36 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_02_01
X-Spam-Level:
Package: pyblosxom
Version: 0.7beta1-1.3
Severity: normal
The version number should not be set in the config.py file. I
couldn't understand why the generator didn't show the new version number
after I upgraded.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.2-1-k7
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8
Versions of packages pyblosxom depends on:
ii apache [httpd] 1.3.29.0.1-5 Versatile, high-performance HTTP s
ii python 2.3.3-5 An interactive high-level object-o
-- no debconf information
---------------------------------------
Received: (at 231621-close) by bugs.debian.org; 6 Apr 2005 17:43:45 +0000
>From [EMAIL PROTECTED] Wed Apr 06 10:43:45 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 1DJEZ7-0006A8-00; Wed, 06 Apr 2005 10:43:45 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DJEOC-0006JK-00; Wed, 06 Apr 2005 13:32:28 -0400
From: Tollef Fog Heen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#231621: fixed in pyblosxom 1.2-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 06 Apr 2005 13:32:28 -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: 5
Source: pyblosxom
Source-Version: 1.2-1
We believe that the bug you reported is fixed in the latest version of
pyblosxom, which is due to be installed in the Debian FTP archive:
pyblosxom_1.2-1.diff.gz
to pool/main/p/pyblosxom/pyblosxom_1.2-1.diff.gz
pyblosxom_1.2-1.dsc
to pool/main/p/pyblosxom/pyblosxom_1.2-1.dsc
pyblosxom_1.2-1_all.deb
to pool/main/p/pyblosxom/pyblosxom_1.2-1_all.deb
pyblosxom_1.2.orig.tar.gz
to pool/main/p/pyblosxom/pyblosxom_1.2.orig.tar.gz
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.
Tollef Fog Heen <[EMAIL PROTECTED]> (supplier of updated pyblosxom 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: Wed, 6 Apr 2005 18:56:44 +0200
Source: pyblosxom
Binary: pyblosxom
Architecture: source all
Version: 1.2-1
Distribution: unstable
Urgency: low
Maintainer: Tollef Fog Heen <[EMAIL PROTECTED]>
Changed-By: Tollef Fog Heen <[EMAIL PROTECTED]>
Description:
pyblosxom - simple weblog ("blog") written in Python
Closes: 227080 229342 231621 271655 274830 282603 291726
Changes:
pyblosxom (1.2-1) unstable; urgency=low
.
* New upstream release (closes: #291726)
- no contributed plugins any more. License issues and upstream
splitting it out of the upstream tarball.
- No more xmlrpc.py (closes: #227080, #229342)
- Now actually uses ignore_directories correctly (closes: #271655)
- Corrected use of hex constants (closes: #274830)
- Uses $pyblosxom_version in default renderer (closes: #282603)
- No longer has version number in default config file (closes: #231621)
.
* Update new upstream URL in welcome.txt
* Update license to the MIT license.
Files:
faa89c6a19a3ea276948ed6370966583 625 web optional pyblosxom_1.2-1.dsc
de3cb536c0c86c1ce0450b2e425ff194 95469 web optional pyblosxom_1.2.orig.tar.gz
235960b49ee4e96ea8f5358bb68cef70 4966 web optional pyblosxom_1.2-1.diff.gz
0f7b50e9bbd463650aa55b26c3c30d4c 91936 web optional pyblosxom_1.2-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCVBoWQSseMYF6mWoRAlpMAJ9w6MGjCihoYe9sOSYHVT5xUig5XACglCvX
mv5x96RkSq6zc5171Uaeibk=
=eUlc
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
