Your message dated Wed, 23 Nov 2016 07:10:32 +0100
with message-id <20161123061032.GA26669@hz1>
and subject line Closing as wontfix
has caused the Debian Bug report #845059,
regarding python-fuse: Please provide a debug package
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
845059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845059
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-fuse
Version: 2:0.2.1-14
Severity: wishlist
Dear maintainer,
I was experiencing some surprising behavior with python-fuse and decided
to trace the function calls with gdb. Python and fuse both have a dbg
package, but python-fuse doesn't.
Please consider adding a package with the debug symbols, the same way
there is one for python-llfuse.
Thanks in advance.
Best regards,
Celelibi
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages python-fuse depends on:
ii fuse 2.9.7-1
ii libc6 2.24-5
ii libfuse2 2.9.7-1
python-fuse recommends no packages.
python-fuse suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
python-fuse-dbgsym provided by recent dh builds fits the build just
fine.
--Seb
--- End Message ---
