Your message dated Mon, 17 Aug 2009 21:31:29 +0100
with message-id <1250541089.166009.10877.nullmai...@kmos.homeip.net>
and subject line Package gmailfs has been removed from Debian
has caused the Debian Bug report #539865,
regarding gmailfs: Unable to use Gmail account - No space left on device
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 ow...@bugs.debian.org
immediately.)
--
539865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmailfs
Version: 0.8-5
Severity: grave
The gmailfs interface appears non-working. The FUESE module module
cannot access GMail.
0. All the following was done as a regular user (not root)
1. Create a fresh google account
2. Make ~/.gmailfs.conf + chmod 600 (see below)
3. Mount with
<I can send password for this in private mail>
/sbin/mount.gmailfs none ~/var/mnt/gmail -o
username=testa911,password=*****,fsname=test123
4. Check mount
$ mount | grep gmail
python on /home/foo/var/mnt/gmail type fuse.python
(rw,nosuid,nodev,user=jaalto)
5. Check mount point
$ ls /home/foo/var/mnt/gmail
ls: cannot access /home/foo/var/mnt/gmail: No space left on device
6. Check log file (see below)
-----------------------------------------------------------------------
# ~/.gmailfs.conf
# chmod 600 ~/.gmailfs.conf
[connection]
# The proxy URL
#proxy = http://user:p...@proxyhost:port
# or just
#proxy = http://proxyhost:port
# The number or retries for the proxy connection.
#retries = 3
[account]
username = foo
password = foo
[filesystem]
fsname = foo123
[references]
# reference = filesystem:username:password
[logs]
# Change this to DEBUG for verbose output (useful for debugging)
level = DEBUG
# if you'd like logs to go to stdout, comment out this variable.
# For logging to, say, stderr, use /dev/stderr of your system's
# equivalent for it
logfile = ~/var/log/gmailfs.log
# End of file
-----------------------------------------------------------------------
$ cat ~/var/log/gmailfs.log
08/04/09 09:38:52 ERROR OpenSSLProxy is missing. Can't use HTTPS proxy!
08/04/09 09:38:52 INFO Starting gmailfs in child process (PID 11989)
08/04/09 09:38:52 INFO waiting for /home/foo/var/mnt/gmail to become a
mountpoint
08/04/09 09:38:52 INFO Mountpoint: /home/foo/var/mnt/gmail
08/04/09 09:38:52 INFO Named mount options: {'username': 'testa911',
'password': '********', 'fsname': 'lx1ca2'}
08/04/09 09:38:55 INFO Connected to gmail
08/04/09 09:38:56 DEBUG get stat:/
08/04/09 09:38:56 DEBUG check getnodemsg:/
08/04/09 09:38:56 DEBUG ind:0
08/04/09 09:38:56 DEBUG dirpath:/ name:
08/04/09 09:38:56 DEBUG ind:0
08/04/09 09:38:56 DEBUG dirpath:/ name:
08/04/09 09:38:57 INFO Sent message failed
08/04/09 09:38:57 INFO Sent message failed
08/04/09 09:38:58 INFO Sent message failed
08/04/09 09:38:58 ERROR Send failed too many times
08/04/09 09:38:58 DEBUG get stat:/
08/04/09 09:38:58 ERROR gmailfs child died, exiting...
08/04/09 09:38:58 DEBUG check getnodemsg:/
08/04/09 09:38:58 DEBUG ind:0
08/04/09 09:38:58 DEBUG dirpath:/ name:
08/04/09 09:38:58 DEBUG ind:0
08/04/09 09:38:58 DEBUG dirpath:/ name:
08/04/09 09:38:59 INFO Sent message failed
08/04/09 09:38:59 INFO Sent message failed
08/04/09 09:38:59 INFO Sent message failed
08/04/09 09:38:59 ERROR Send failed too many times
08/04/09 09:39:21 DEBUG get stat:/
08/04/09 09:39:21 DEBUG check getnodemsg:/
08/04/09 09:39:21 DEBUG ind:0
08/04/09 09:39:21 DEBUG dirpath:/ name:
08/04/09 09:39:21 DEBUG ind:0
08/04/09 09:39:21 DEBUG dirpath:/ name:
08/04/09 09:39:22 INFO Sent message failed
08/04/09 09:39:22 INFO Sent message failed
08/04/09 09:39:22 INFO Sent message failed
08/04/09 09:39:22 ERROR Send failed too many times
08/04/09 09:44:47 DEBUG get stat:/
08/04/09 09:44:47 DEBUG check getnodemsg:/
08/04/09 09:44:47 DEBUG ind:0
08/04/09 09:44:48 DEBUG dirpath:/ name:
08/04/09 09:44:48 DEBUG ind:0
08/04/09 09:44:48 DEBUG dirpath:/ name:
08/04/09 09:44:48 INFO Sent message failed
08/04/09 09:44:49 INFO Sent message failed
08/04/09 09:44:49 INFO Sent message failed
08/04/09 09:44:49 ERROR Send failed too many times
-----------------------------------------------------------------------
$ dpkg -L gmailfs
/.
/sbin
/usr
/usr/bin
/usr/bin/mount.gmailfs
/usr/share
/usr/share/pyshared
/usr/share/pyshared/gmailfs.py
/usr/share/pyshared-data
/usr/share/pyshared-data/gmailfs
/usr/share/doc
/usr/share/doc/gmailfs
/usr/share/doc/gmailfs/README
/usr/share/doc/gmailfs/changelog.gz
/usr/share/doc/gmailfs/copyright
/usr/share/doc/gmailfs/examples
/usr/share/doc/gmailfs/examples/tests.py.gz
/usr/share/doc/gmailfs/NEWS.Debian.gz
/usr/share/doc/gmailfs/changelog.Debian.gz
/usr/share/man
/usr/share/man/man8
/usr/share/man/man8/mount.gmailfs.8.gz
/etc
/etc/gmailfs
/etc/gmailfs/gmailfs.conf
/sbin/mount.gmailfs
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gmailfs depends on:
ii fuse-utils 2.7.4-2 Filesystem in USErspace (utilities
ii python 2.5.4-2 An interactive high-level object-o
ii python-central 0.6.11 register and build utility for Pyt
ii python-fuse 1:0.2-pre3-9 Python bindings for FUSE (Filesyst
ii python-libgmail 0.1.11-1 Python bindings to access Gmail ac
Versions of packages gmailfs recommends:
ii encfs 1.5.2-1 encrypted virtual filesystem
gmailfs suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8-6+rm
You filled the bug http://bugs.debian.org/539865 in Debian BTS
against the package gmailfs. I'm closing it as fixed in *unstable*,
but it will remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/540773. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
--- End Message ---
