Your message dated Mon, 6 Feb 2006 14:26:22 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#351462: python-fuse: cannot import fuse
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 ---
>From [EMAIL PROTECTED] Sat Feb 04 16:47:11 2006
Received: (at submit) by bugs.debian.org; 5 Feb 2006 00:47:11 +0000
Return-path: <[EMAIL PROTECTED]>
Received: from logilab.net2.nerim.net ([62.4.19.137] helo=tucana.logilab.fr)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1F5Y3b-0007Lx-6R
        for [EMAIL PROTECTED]; Sat, 04 Feb 2006 16:47:11 -0800
Received: from orion.logilab.fr (scutum.logilab.fr [172.17.0.2])
        by tucana.logilab.fr (Postfix) with ESMTP id A0B077142C1
        for <[EMAIL PROTECTED]>; Sun,  5 Feb 2006 01:46:38 +0100 (CET)
Received: from crater.logilab.fr (crater.logilab.fr [172.17.1.4])
        by orion.logilab.fr (Postfix) with SMTP id 8A8DE2BE7C
        for <[EMAIL PROTECTED]>; Sun,  5 Feb 2006 01:46:38 +0100 (CET)
Received: (nullmailer pid 3639 invoked by uid 1000);
        Sun, 05 Feb 2006 00:46:38 -0000
Date: Sun, 5 Feb 2006 01:46:38 +0100
From: Nicolas Chauvat <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: python-fuse: cannot import fuse
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
X-Mailer: reportbug 3.18
User-Agent: Mutt/1.5.11
Content-Transfer-Encoding: quoted-printable
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: python-fuse
Version: 2.4-1
Severity: grave
Justification: renders package unusable


Importing fuse used to work but broke with my last upgrade. I suspect
recompiling the package=20
would be enough as I think I remember seeing something about a fuse
upgrade.


>>> import fuse
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.3/site-packages/fuse.py", line 24, in ?
    from _fuse import main, FuseGetContext, FuseInvalidate
ImportError: /usr/lib/python2.3/site-packages/_fusemodule.so: symbol
fuse_mount, version FUSE_
2.2 not defined in file libfuse.so.2 with link time reference
>>>=20


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=3Dfr, LC_CTYPE=3Dfr (charmap=3Dlocale: Cannot set LC_CTYPE t=
o
default locale: No such f
ile or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or
directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968) (ignored: LC_ALL set to fr)

Versions of packages python-fuse depends on:
ii  python                        2.3.5-5    An interactive high-level
object-o
ii  python2.3-fuse                2.4-1      Python bindings for FUSE
(Filesyst

python-fuse recommends no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE =3D (unset),
        LC_ALL =3D "fr",
        LANG =3D "fr"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or
directory
locale: Cannot set LC_MESSAGES to default locale: No such file or
directory
locale: Cannot set LC_ALL to default locale: No such file or directory

--=20
Nicolas Chauvat

logilab.fr - services en informatique avanc=E9e et gestion de connaissanc=
es =20


--- End Message ---
--- Begin Message ---
>From [EMAIL PROTECTED] Mon Feb 06 14:26:56 2006
Received: (at 351462-done) by bugs.debian.org; 6 Feb 2006 22:26:56 +0000
Return-path: <[EMAIL PROTECTED]>
Received: from mail.gmx.de ([213.165.64.21] helo=mail.gmx.net)
        by spohr.debian.org with smtp (Exim 4.50)
        id 1F6Eoy-00026o-BW
        for [EMAIL PROTECTED]; Mon, 06 Feb 2006 14:26:56 -0800
Received: (qmail invoked by alias); 06 Feb 2006 22:26:24 -0000
Received: from adsl-70-231-230-238.dsl.snfc21.sbcglobal.net (EHLO localhost) 
[70.231.230.238]
  by mail.gmx.net (mp019) with SMTP; 06 Feb 2006 23:26:24 +0100
X-Authenticated: #18275278
Received: from foo.befour.org ([10.0.0.6])
        by localhost with esmtp (Exim 3.36 #1 )
        id 1F6EoQ-0002RC-00
        for <[EMAIL PROTECTED]>; Mon, 06 Feb 2006 14:26:22 -0800
Received: from seb by foo.befour.org with local (Exim 3.36 #1 (Debian))
        id 1F6EoQ-0002Uo-00
        for <[EMAIL PROTECTED]>; Mon, 06 Feb 2006 14:26:22 -0800
Date: Mon, 6 Feb 2006 14:26:22 -0800
From: Sebastien Delafond <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#351462: python-fuse: cannot import fuse
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11
Sender: Seb <[EMAIL PROTECTED]>
X-Y-GMX-Trusted: 0
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=-5.0 required=4.0 tests=BAYES_01,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Fixed in 2.5-1.

On Mon, Feb 06, 2006 at 11:23:06PM +0100, Nicolas Chauvat wrote:
> On Sat, Feb 04, 2006 at 08:29:26PM -0800, Sebastien Delafond wrote:
> > I don't see this bug with kernel 2.6.14-1-686. Can you try with the
> > new python-fuse 2.5-1, and see if you get the same exception ?
> 
> Works for me. You can close the bug as far as I am concerned.

Good to hear. Cheers,

--Seb

--- End Message ---

Reply via email to