Your message dated Thu, 02 Feb 2006 00:32:07 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348458: fixed in wordpress 2.0.1-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; 17 Jan 2006 03:04:53 +0000
>From [EMAIL PROTECTED] Mon Jan 16 19:04:53 2006
Return-path: <[EMAIL PROTECTED]>
Received: from mail.gmx.net ([213.165.64.21])
by spohr.debian.org with smtp (Exim 4.50)
id 1Eyh9Q-00039a-Nz
for [EMAIL PROTECTED]; Mon, 16 Jan 2006 19:04:53 -0800
Received: (qmail invoked by alias); 17 Jan 2006 03:04:21 -0000
Received: from unknown (EHLO test.wgdd.de) [195.227.105.180]
by mail.gmx.net (mp034) with SMTP; 17 Jan 2006 04:04:21 +0100
X-Authenticated: #17381962
Received: from dl by test.wgdd.de with local (Exim 3.36 #1 (Debian))
id 1Eyh8u-0003Nr-00; Tue, 17 Jan 2006 04:04:20 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Daniel Leidert <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Please announce that upgrade.php needs to be run after update
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.18
Date: Tue, 17 Jan 2006 04:04:20 +0100
Sender: Daniel Leidert <[EMAIL PROTECTED]>
X-Y-GMX-Trusted: 0
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-Level:
X-Spam-Status: No, hits=-6.9 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_SORBS,RCVD_IN_SORBS_WEB autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Package: wordpress
Version: 2.0-1
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Upgrading from 1.5.2 (and below) can lead to an error also described at
http://wordpress.org/support/topic/55431 and
http://wordpress.org/support/topic/54494. I tried to find useful
information inside README.Debian but got nothing. Of course,
/usr/share/doc/wordpress/readme.html contains a hint about running
http://domain.tld/wp-admin/upgrade.php which then also solved the above
mentioned issue. But it would be nice to inform the user via
NEWS(.Debian.gz) and also README.Debian.
Regards, Daniel
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.02060113
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDzF60dg0kG0+YFBERAvhWAJ0aqkpAhP12617vEC1Qbs52ukXOCQCfbtpM
mEA3CB3tmF6YftF9VQmXuaQ=
=ACYk
-----END PGP SIGNATURE-----
---------------------------------------
Received: (at 348458-close) by bugs.debian.org; 2 Feb 2006 08:40:18 +0000
>From [EMAIL PROTECTED] Thu Feb 02 00:40:18 2006
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1F4Zst-0004g0-4k; Thu, 02 Feb 2006 00:32:07 -0800
From: Kai Hendry <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#348458: fixed in wordpress 2.0.1-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 02 Feb 2006 00:32:07 -0800
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-Level:
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
Source: wordpress
Source-Version: 2.0.1-1
We believe that the bug you reported is fixed in the latest version of
wordpress, which is due to be installed in the Debian FTP archive:
wordpress_2.0.1-1.diff.gz
to pool/main/w/wordpress/wordpress_2.0.1-1.diff.gz
wordpress_2.0.1-1.dsc
to pool/main/w/wordpress/wordpress_2.0.1-1.dsc
wordpress_2.0.1-1_all.deb
to pool/main/w/wordpress/wordpress_2.0.1-1_all.deb
wordpress_2.0.1.orig.tar.gz
to pool/main/w/wordpress/wordpress_2.0.1.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.
Kai Hendry <[EMAIL PROTECTED]> (supplier of updated wordpress 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, 2 Feb 2006 11:22:31 +0900
Source: wordpress
Binary: wordpress
Architecture: source all
Version: 2.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Kai Hendry <[EMAIL PROTECTED]>
Changed-By: Kai Hendry <[EMAIL PROTECTED]>
Description:
wordpress - an award winning weblog manager
Closes: 328909 348458
Changes:
wordpress (2.0.1-1) unstable; urgency=low
.
* New upstream release
* CSS Security Vulnerability (Closes: #328909)
* Please announce that upgrade.php needs to be run after update
(Closes: #348458)
Files:
74d6a39f48b1c106efeda2b4523f12cf 564 web optional wordpress_2.0.1-1.dsc
5eb6685eba97c67ccaebc74de30cef4e 504946 web optional
wordpress_2.0.1.orig.tar.gz
2829cca9acd7951df4b31d4d774e0eb8 6847 web optional wordpress_2.0.1-1.diff.gz
f2c38ee5f746a76f81930c6ac96030dc 501174 web optional wordpress_2.0.1-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD4cJAK/juK3+WFWQRAjKCAJ9b1usSRsfOV2DZ7UfgeZULIhcNtACfS7Og
Oc7zV4CURwNv62WxHELC9XY=
=B84s
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
