Bugzilla Bug 63785

Hello

Gmailfs allows you to mount your Google Mail account. It can be very useful since that enables a 1gb Netdrive.

Gmailfs uses fuse (not app-emulation/fuse). Fuse is allereay filed under http://bugs.gentoo.org/show_bug.cgi?id=59733. Gmailfs also depends on the fuse-python bindings and libgmail. I'll upload ebuilds for those later.

Unfortunately the Gmailfs archive has no version number in the filename. That makes it hard to update. I'll contact the devs later.

Moritz

Created an attachment (id=39445) [details]
sys-fs/gmailfs-0.2.ebuild

*** This bug has been marked as a duplicate of 62100 ***

As we all know, this is not the same as libgmail. It only depends on it.

gmail fs is quite a security (joke) risk. Plus it most likely violates the tos
in some way, as the mailcheckers did.

ebuild 0.3 http://bugs.gentoo.org/show_bug.cgi?id=87659

*** Bug 87659 has been marked as a duplicate of this bug. ***

Created an attachment (id=55142) [details]
gmailfs-0.3.ebuild

Credit to Cagnulein for this

It actually doesn't work with libgmail 0.0.8, you need CVS: "Grab the CVS
version of libgmail by following the instructions here. After checking out the
file, copy libgmail.py and constants.py to somewhere Python can find them
(/usr/local/lib/python2.3/site-packages/ works for Debian, others may vary)."

Also I added a dependancy for fuse-python bindings. Find this in bugzilla.

Created an attachment (id=55151) [details]
gmailfs-0.3.ebuild

gmailfs-0.3.ebuild updated

Created an attachment (id=55165) [details]
Fixed the instructions to get libgmail by cvs

In the previous ebuild the instructions to get libgmail was wrong, there was
libgmailfs instead of libgmail :)

Created an attachment (id=55166) [details]
correct the cvs' module

Just a question .. it seems like gmailfs doesn't work with fuse-2.x ... the
author's page suggest the use of fuse-1.3 .. so does it really work with 2.x ?

Created an attachment (id=61944) [details]
New version of gmailfs package.

I modified gmailfs-0.3.ebuild for use new version of gmailfs-0.4. It seems that
working...
Bye

(From update of attachment 61944 [details])
># Copyright 1999-2004 Gentoo Foundation
># Distributed under the terms of the GNU General Public License v2
># $Header: $
>
>
>KEYWORDS="~x86 ~ppc ~sparc ~mips ~alpha ~arm ~hppa ~amd64 ~ia64"
>DESCRIPTION="GmailFS provides a mountable Linux filesystem which uses your Gmail account as its storage medium."
>HOMEPAGE="http://richard.jones.name/google-hacks/gmail-filesystem/gmail-filesystem.html"
>SRC_URI="http://richard.jones.name/google-hacks/gmail-filesystem/gmailfs-0.4.tar.gz"
>LICENSE="GPL-2"
>SLOT="0"
>IUSE=""
>
>RDEPEND=">=dev-lang/python-2.3
>	>=sys-fs/fuse-python-0.1
>	>=sys-fs/fuse-1.3
>	>=net-libs/libgmail-0.0.8
>	sys-fs/fuse-python"
>
>src_install() {
>	dobin ${WORKDIR}/gmailfs-0.4/gmailfs.py || die "Can't dobin"
>	insinto /sbin
>	doins ${WORKDIR}/gmailfs-0.4/mount.gmailfs || die "Can't write to /sbin"
>}
>
>pkg_postinst() {
>	einfo "You should now be able to mount gmailfs."
>	einfo "To mount from the command line, do:"
>	einfo "mount -t gmailfs /usr/bin/gmailfs.py /path/of/mount/point -o username=gmailuser,password=gmailpass,fsname=zOlRRa"
>	einfo "To use fstab, create an entry /etc/fstab that looks something like:"
>	einfo "/usr/bin/gmailfs.py /path/of/mount/point gmailfs noauto,username=gmailuser,password=gmailpass,fsname=zOlRRa"
>	einfo " "
>	ewarn "Remember to choose a very creative, unguessable fsname, else someone"
>	ewarn "could manipulate your filesystem. Also remember that gmailfs is a"
>	ewarn "cruel hack. So don't expect things like good performance"
>	einfo " "
>	einfo "You actually need to use libgmail from CVS. So do this:"
>	einfo "cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/libgmail login"
>	einfo "cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/libgmail co libgmail"
>	einfo "then copy constants.py and libgmail.py to your"
>	einfo "/usr/lib/python-<ver>/site-packages directory"
	chmod a+x /sbin/mount.gmailfs
	ln -s /sbin/mount.gmailfs /sbin/mount.fuse
>
>}

Created an attachment (id=62039) [details]
gmailfs-0.4.ebuild

Now, running....
This new ebuild copy gmailfs.conf file in /etc. So, after that you have
modified this file with gmail account information it is possible mount gmailfs.

For mount gmailfs:
 mount -t gmailfs /usr/bin/gmailfs.py /mnt/gmailfs/

Bye

I get these errors when trying to mount a gmailfs mount...

gmailfs.py:Gmailfs:unnamed mount options: ['rw']
gmailfs.py:Gmailfs:named mount options: {}
fuse: reading device: Input/output error

Has anybody seen this before?

i just posted an updane bug for libgmail-0.1.0

when it will be here, i think we will not need cvs libgmail anymore but gmailfs
will need a change because constants.py has been renamed to lgconstants.py.

Created an attachment (id=72877) [details]
gmailfs-0.5

Version 0.5 is out!

http://richard.jones.name/google-hacks/gmail-filesystem/gmail-filesystem.html

version 0.6 is out

Created an attachment (id=80847) [details]
gmailfs-0.7.2-r1.ebuild

Created an attachment (id=80848) [details]
gentoo.patch

required for gmailfs-0.7.2-r1.ebuild

I might be interested in maintaining this.  I'm currently looking into the
feasibility of the package and fixing up some little things in the ebuild.  The
dep on fuse-python may be the ultimate showstopper, though.

Created an attachment (id=81982) [details]
gentoo.patch

I'm all for marking this a dup of 62100, not because it's the same as libgmail,
but because of the gmail developers' requests not to abuse their service.
Again, please read ALL the comments in bug #62100 especially comment 10. Gentoo
needs to respect developers of other projects, especially when a distribution
begins to abuse said projects.

*** Bug 134516 has been marked as a duplicate of this bug. ***

*** Bug 134516 has been marked as a duplicate of this bug. ***

Created an attachment (id=121804) [details]
gmailfs-0.7.3.patch

New version of gmailfs available... patch for ebuild attached

I'll take this.

(In reply to comment #27)
> I'll take this.
> 

w00t! :D

Created an attachment (id=123432) [details]
gmailfs-0.7.3.ebuild

Ebuild for the latest version

Created an attachment (id=123433) [details]
files/gmailfs-0.7.3.patch

Just renaming the patch to match Gentoo conventions

: jmglov@laurana; sudo mount -t gmailfs /usr/bin/gmailfs.py mnt/gmail 
Ignored option :rw
06/30/07 10:31:29 ERROR      Unable to find GMail account configuration
06/30/07 10:31:29 WARNING    Using default file system (Dangerous!)
Traceback (most recent call last):
  File "/sbin/mount.gmailfs", line 164, in ?
    main(mountpoint, namedOptions, useEncfs)
  File "/sbin/mount.gmailfs", line 90, in main
    gmailfs.main(mountpoint, namedOptions)
  File "/usr/bin/gmailfs.py", line 1135, in main
    server = Gmailfs(mountpoint, **namedOptions)
  File "/usr/bin/gmailfs.py", line 547, in __init__
    Fuse.__init__(self, mountpoint, **kw)
  File "/usr/lib/python2.4/site-packages/fuse.py", line 652, in __init__
    self.parser = parserclass(*args, **kw)
  File "/usr/lib/python2.4/site-packages/fuse.py", line 264, in __init__
    SubbedOptParse.__init__(self, *args, **kw)
  File "/usr/lib/python2.4/site-packages/fuseparts/subbedopts.py", line 240, in
__init__
    OptionParser.__init__(self, *args, **kw)
TypeError: __init__() got multiple values for keyword argument 'usage'
06/30/07 10:31:30 ERROR      gmailfs child died, exiting...

Hrm... need to take a look at this when I have time.

Created an attachment (id=123435) [details]
gmailfs-0.7.3.ebuild

Added strong language to the postinstall warning of possible TOS violations,
etc.

Created an attachment (id=123592) [details]
gmailfs-0.7.3.ebuild

Now depends on virtual/fuse-python; still doesn't work

Created an attachment (id=123601) [details]
gmailfs-log-path.patch

After a bit of hackery and black magic, I fixed the problem where it could not
find the config file. root can now mount a gmailfs filesystem... Our patch
breaks lots of stuff... it not only changes the config file to ~/.gmailfs
(which is a relative path, and breaks under the vanilla gmailfs code), and
changes the logfile to /var/log/gmailfs.log which i'm doubting our decision to
do, because users don't have write access to that, and fuse is supposed to be
usable by the user =) isn't that why we changed the config file to ~/.gmailfs?

I'll look into how easy it is to get this working (w/o dealing with the logfile
issue) and leave the logfile stuff up to you guys for now

I'm also looking into possibly having dual config files, one in /etc/ and one
in ~. Those changes should probably be merged into vanilla however, so i'll
send em to the gmailfs dev.

(From update of attachment 123601 [details])
><HTML><HEAD/><BODY><PRE>--- gmailfs.py	2007-07-02 05:20:37.000000000 -0400
>+++ gmailfs.py	2007-07-02 05:30:48.000000000 -0400
>@@ -89,9 +89,7 @@
>     global References
>     global DefaultUsername, DefaultPassword, DefaultFsname
>     global NumberQueryRetries
>-    try:
>-      cp.read(fname)
>-    except:
>+    if cp.read(os.path.expanduser(fname)) == []:
>       log.warning("Unable to read configuration file: " + fname)
>       return
> 
></PRE></BODY></HTML>

Created an attachment (id=123603) [details]
gmailfs-log-path.patch

arrg, sorry about that, thought I could edit the attachment in place. I messed
up the paths in the attachment and tried to fix it... here's the fixed one.

Created an attachment (id=123606) [details]
gmailfs-0.7.3.ebuild

I fixed the gmailfs ebuild so now any user can mount a gmailfs file system. The
postinst message tells you how to use it. We were incorrectly using the
scripts, and completely ignoring the mount.gmailfs script. I also took out the
test.py script which is only used for testing purposes.

Created an attachment (id=123608) [details]
gmailfs-0.7.3.ebuild

Forgot to tell the ebuild to apply the patch I created in an earlier post =)

Created an attachment (id=123610) [details]
gmailfs-0.7.3.ebuild

ugh... attached the wrong file... you'll have to excuse me, i'm having an off
day...

Created an attachment (id=123612) [details]
gmailfs-encfs-mount.patch

the mount.gmailfs script supports encfs natively, so we should probably put
something in the postinst() about it. It also needs a patch in order to work
correctly with relative paths (i'm using encfs-1.3.2.1). Patch is attached

I retract what I said about not being able to write to /var/log.... it seems to
work (although idk why...)

My encfs-mount, and log-path patches are being applied to the next release...
So once it's up, they will no longer be needed.

Created an attachment (id=123736) [details]
gmailfs-multi-config.patch

I made a patch to allow a global and user-specific config file (one in /etc,
and one in ~). I will attach it, but it will probably be in the next release

Created an attachment (id=125416) [details]
gmailfs-0.8.0.ebuild

New version of gmailfs (0.8.0) has been released. New ebuild attached, and will
attach the only patch needed in my next post. All the older patches are now
obsolete.

Please note that this new version requires the new fuse-python-0.2 bindings. It
will not work with the python-fuse bindings or the fuse-python bindings
currently in portage. An ebuild for the new fuse-python-0.2 bindings can be
found at http://bugs.gentoo.org/show_bug.cgi?id=185944

Created an attachment (id=125418) [details]
gmailfs-0.8.0.patch

everything compiles fine, but it doesn't work.

I mount the partition (without encryption) -- OK
# mount.gmailfs none /mnt/gmailfs

# df -h
[...]
python                2,0G     0  2,0G   0% /mnt/gmailfs

# echo "hello world" /mnt/gmailfs/hello.txt

# ls -l /mnt/gmailfs
total 1
-rw-r--r-- 1 root root 12 16 ott 19:18 hello.txt

# cat /mnt/gmailfs/hello.txt
cat: gmailfs/hello.txt: Invalid argument


any ideas? I'm running on amd64.

(In reply to comment #46)
> # echo "hello world" /mnt/gmailfs/hello.txt

whoops obvious typo, it was
# echo "hello world" >/mnt/gmailfs/hello.txt

The above problem is fixed using libgmail-0.1.7

the appropriate dependencies should be added in the ebuild and the bug report.

It does not work. I get this error when using gmailfs.py:

Traceback (most recent call last):
  File "/usr/local/bin/gmailfs.py", line 541, in <module>
    class Gmailfs(Fuse):
  File "/usr/local/bin/gmailfs.py", line 635, in Gmailfs
    class GmailStat(fuse.Stat):
AttributeError: 'module' object has no attribute 'Stat'

Reassigning since jmglov has retired from Gentoo.

doesn't work for me:
# mount.gmailfs none /mnt/mmc
HTTP Error 302: The HTTP server returned a redirect error that would lead to an
infinite loop.
The last 30x error message was:
Moved Temporarily

Created an attachment (id=153897) [details]
fuse-python is now dev-python/fuse-python not sys-fs/fuse-python

The previous ebuild assumed the user had a portage overlay containing
fuse-python as sys-fs/fuse-python.  fuse-python is now in the main portage tree
as dev-python/fuse-python, this new ebuild reflects that change.

http://mail.google.com/mail/help/terms_of_use.html

"You also agree that you will not use any robot, spider, other automated
device, or manual process to monitor or copy any content from the Service."

Plus they cut you off by 

http://google.wikia.com/wiki/Gmail_sending_limit

automatically now.

(this is an automated message based on filtering criteria that matched this
bug)

Hello, The Gentoo Team would like to firstly thank you for your ebuild
submission. We also apologize for not being able to accommodate you in a timely
manner. There are simply too many new packages.

Allow me to use this opportunity to introduce you to Gentoo Sunrise. The
sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to
commit to and all users can have ebuilds reviewed by Gentoo devs for entry into
the overlay.
So, the sunrise team is suggesting that you look into this and submit your
ebuild to the overlay where even *you* can commit to. =)

Because this is a mass message, we are also asking you to be patient with us.
We anticipate a large number of requests in a short time. 

Thanks,
On behalf of the Gentoo Sunrise Team,
Jeremy.

[1]: http://www.gentoo.org/proj/en/sunrise/
[2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq