Your message dated Fri, 23 Sep 2005 11:32:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329726: fixed in gnome-blog 0.8-5
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; 23 Sep 2005 02:03:46 +0000
>From [EMAIL PROTECTED] Thu Sep 22 19:03:46 2005
Return-path: <[EMAIL PROTECTED]>
Received: from master.debian.org [146.82.138.7]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EIcug-0000Qp-00; Thu, 22 Sep 2005 19:03:46 -0700
Received: from 159stb41.codetel.net.do (misiongenovesa.org) [64.32.109.159]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1EIcue-0005zw-00; Thu, 22 Sep 2005 21:03:45 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Paolo Benvenuto <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gnome-blog-poster crashes when run
Reply-To: Paolo Benvenuto <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.17
Date: Thu, 22 Sep 2005 22:03:40 -0400
Message-Id: <[EMAIL PROTECTED]>
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.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
OUR_MTA_MSGID autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: gnome-blog
Version: 0.8-4
Severity: grave
Justification: renders package unusable
$ gnome-blog-poster
/usr/lib/python2.3/site-packages/gtk-2.0/gnome/vfs.py:4:
DeprecationWarning: Module gnome.vfs is deprecated; please import
gnomevfs instead
DeprecationWarning)
Using gconf_prefix /apps/gnome-blog
Traceback (most recent call last):
File "/usr/bin/gnome-blog-poster", line 52, in ?
app = BloggerApp()
File "/usr/bin/gnome-blog-poster", line 35, in __init__
on_entry_posted=self._onEntryPosted)
File
"/usr/lib/python2.3/site-packages/gnomeblog/blog_poster.py",
line 37, in __init__
self.blogEntry = rich_entry.RichEntry()
File
"/usr/lib/python2.3/site-packages/gnomeblog/rich_entry.py",
line 21, in __init__
self.set_editable(TRUE)
NameError: global name 'TRUE' is not defined
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12-1-386
Locale: LANG=es_DO.UTF-8, LC_CTYPE=es_DO.UTF-8 (charmap=UTF-8)
Versions of packages gnome-blog depends on:
ii gconf2 2.10.1-2 GNOME configuration database syste
ii python 2.3.5-3 An interactive high-level object-o
ii python-gnome2 2.10.0-2 Python bindings for the GNOME desk
ii python-gnome2-extras 2.10.0-4 Python bindings for the GNOME desk
gnome-blog recommends no packages.
-- debconf-show failed
---------------------------------------
Received: (at 329726-close) by bugs.debian.org; 23 Sep 2005 18:40:03 +0000
>From [EMAIL PROTECTED] Fri Sep 23 11:40:03 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EIsLP-0001yI-00; Fri, 23 Sep 2005 11:32:23 -0700
From: Frederic Peters <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#329726: fixed in gnome-blog 0.8-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 23 Sep 2005 11:32:23 -0700
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.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: gnome-blog
Source-Version: 0.8-5
We believe that the bug you reported is fixed in the latest version of
gnome-blog, which is due to be installed in the Debian FTP archive:
gnome-blog_0.8-5.diff.gz
to pool/main/g/gnome-blog/gnome-blog_0.8-5.diff.gz
gnome-blog_0.8-5.dsc
to pool/main/g/gnome-blog/gnome-blog_0.8-5.dsc
gnome-blog_0.8-5_all.deb
to pool/main/g/gnome-blog/gnome-blog_0.8-5_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.
Frederic Peters <[EMAIL PROTECTED]> (supplier of updated gnome-blog 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: Fri, 23 Sep 2005 20:14:56 +0200
Source: gnome-blog
Binary: gnome-blog
Architecture: source all
Version: 0.8-5
Distribution: unstable
Urgency: low
Maintainer: Frederic Peters <[EMAIL PROTECTED]>
Changed-By: Frederic Peters <[EMAIL PROTECTED]>
Description:
gnome-blog - GNOME applet to post to weblog entries
Closes: 329726
Changes:
gnome-blog (0.8-5) unstable; urgency=low
.
* blog_poster.py: declare use_gtkspell as global (strange but works)
(really closes: #329726)
* *.py: replaced gtk.TRUE/FALSE by True/False to get rid of deprecation
warnings.
Files:
9d728feafcbece5d5aeee5a6588326cd 654 gnome optional gnome-blog_0.8-5.dsc
7b4b525b403c9c554bdab2752c41fbfa 29936 gnome optional gnome-blog_0.8-5.diff.gz
3bb4164219de2397baca3e6745ba8afe 61602 gnome optional gnome-blog_0.8-5_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDNEbMoR3LsWeD7V4RAs61AJ9kAA2NRYGjqoozofpiztzPJfoBJwCfdD/O
THCcLt6lBFAp1EBjG1tQZa0=
=a6x8
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
