Your message dated Fri, 29 Dec 2006 12:34:39 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404889: python-fuse: Fuse.main() triggers TypeError
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 ---
Package: python-fuse
Version: 2.5-5
Severity: important
Calling Fuse.main() always results in a type error. One example for this
is /usr/share/doc/python-fuse/examples/xmp.py:
| Traceback (most recent call last):
| File "./xmp.py", line 183, in ?
| server.main()
| File "/usr/lib/python2.4/site-packages/fuse.py", line 126, in main
| apply(main, (), d)
| TypeError: argument 21 must be string, not None
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (700, 'testing'), (650, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.19-rc1
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages python-fuse depends on:
ii libfuse2 2.5.3-4.1 Filesystem in USErspace library
ii python 2.4.4-2 An interactive high-level object-o
ii python-central 0.5.12 register and build utility for Pyt
python-fuse recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
No problem...
Cheers,
--Seb
On Fri, Dec 29, 2006 at 10:56:09AM +0100, Lars Noschinski wrote:
> * Sebastien Delafond <[EMAIL PROTECTED]> [2006-12-29 10:48]:
> >gmailfs works here (same version of python-fuse, kernel 2.6.18), and
> >it does call Fuse.main(). I'd say xmp.py is deprecated, which is
> >indeed a bug (albeit a minor one), but I'd like you to tell me more
> >about the actual problem you're facing: do you only see this with
> >xmp.py, or also with a program of your own ?
>
> I saw this problem with my own program too, but xmp.py was my example.
> Unfortunately, it turns out, that I was a real blockhead yesterday: I
> tried for abaout an hour, but it never occured to me, that I didn't gave
> a mountpoint to my program.
>
> So I sincerely apologise for disturbing you with this non-bug.
>
> - Lars
>
--- End Message ---
