Your message dated Fri, 23 Sep 2005 09:35:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#329726: gnome-blog-poster doesn't work any more 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-done) by bugs.debian.org; 23 Sep 2005 07:36:04 +0000 >From [EMAIL PROTECTED] Fri Sep 23 00:36:03 2005 Return-path: <[EMAIL PROTECTED]> Received: from cytise.entrouvert.com (mail.entrouvert.be) [84.207.4.3] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1EIi6F-0007YH-00; Fri, 23 Sep 2005 00:36:03 -0700 Received: from 115-180.242.81.adsl.skynet.be ([81.242.180.115] helo=trap) by mail.entrouvert.be with asmtp (Exim) (TLSv1:DES-CBC3-SHA:168) id 1EIi6C-00058M-00; Fri, 23 Sep 2005 09:36:00 +0200 Received: from fred by trap with local (Exim 4.52) id 1EIi6B-0003u8-S5; Fri, 23 Sep 2005 09:35:59 +0200 Date: Fri, 23 Sep 2005 09:35:59 +0200 From: Frederic Peters <[EMAIL PROTECTED]> To: Paolo Benvenuto <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#329726: gnome-blog-poster doesn't work any more Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> X-Operating-System: Debian GNU/Linux (testing/unstable with kernel Linux 2.6.12) X-Uptime: 09:28:32 up 42 min, 6 users, load average: 1.14, 0.56, 1.44 User-Agent: mutt-ng devel-20050619 (Debian) 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 Paolo Benvenuto wrote: > Package: gnome-blog > Version: 0.8-4 > Severity: grave > Justification: renders package unusable > > > gnome-blog-poster crashes when run: > > $ 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 > I don't know how you did it but this line doesn't exist as is in gnome-blog, 0.8-4, where it uses gtk.TRUE and works. Looking at the history of that particular file http://cvs.gnome.org/viewcvs/gnome-blog/rich_entry.py?rev=1.23&view=log I can't even find when it would have been the line you suggest. (the only change is a move from gtk.TRUE to Python True constant in May) You probably should reinstall gnome-blog to fix your problem; feel free to reopen the bug if you still experience the same problem. Regards, Frederic -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]