Hi! I use libgmail on a daily basis, now it does not work, to login. The reason for this is that gmail has changed login url. The fix is simple, enter in the latest libgmail into portage. url: http://sourceforge.net/project/showfiles.php?group_id=113492 I've tested the latest at the site above and it works. Best regards, Patrik
What version of libgmail causes you problems? Also, pasting the error here would be nice.
Hi! I'm using net-libs/libgmail-0.1.3.3. It has worked for me for quite a while now. This problem has happened to me before or to the lib to be exact. Python 2.4.3 (#1, Jul 26 2006, 11:15:39) [GCC 3.4.6 (Gentoo 3.4.6-r1, HTB-3.4.4-1.00, ssp-3.4.5-1.0, pie-8.7.9)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import libgmail >>> ga = libgmail.GmailAccount('patrik.mrx@gmail.com', 'mypasswd is my secret') >>> ga.login() Traceback (most recent call last): File "<stdin>", line 1, in ? File "/usr/lib64/python2.4/site-packages/libgmail.py", line 320, in login pageData = self._retrievePage(redirectURL) File "/usr/lib64/python2.4/site-packages/libgmail.py", line 333, in _retrievePage resp = urllib2.urlopen(req) File "/usr/lib64/python2.4/urllib2.py", line 130, in urlopen return _opener.open(url, data) File "/usr/lib64/python2.4/urllib2.py", line 356, in open req = meth(req) File "/usr/lib64/python2.4/urllib2.py", line 943, in do_request_ raise URLError('no host given') urllib2.URLError: <urlopen error no host given> There is a new version released for libgmail, as i said, i tried it, that works. Regards, Patrik
Regarding the error, I don't think it's any URL change. Google tends to change the login procedures of GMail from time to time, so the old ones don't work. I'll make an attempt to write an ebuild for it but don't expect it to enter the Portage tree and/or become stable any time soon. This means that you will have to set up an overlay and install it from there. I'll let you know.
I wrote the ebuild for net-libs/libgmail-0.1.5.1, tested it and it works without any problems on my system (x86). Note that I've removed its dependency on dev-python/logging since (after searching a bit) I don't think it's necessary (please enlighten me if I'm wrong). In 48hrs I will submit this ebuild to Project Sunrise. If anyone objects, please let me know. To Mr. Patrik Larsson: This ebuild isn't considered to be stable and tested enough. I tested it myself and it works just fine on my machine, yet your mileage may vary. To install it, you need this ebuild and to follow: http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds I hope this helps.
Created attachment 93914 [details] libgmail-0.1.5.1 ebuild
Hi! Thank you it's working great! Best of regards, Patrik
Hi! You might as well add ~amd64, it works just fine here. Regards, Patrik
Hiya! Thanks for letting me know. I will add ~amd64 to KEYWORDS as soon as it's time for me to send the ebuild to the Sunrise overlay (next couple of days).
This bug is assigned to net-p2p so I won't be commiting it to the sunrise overlay.
Created attachment 94102 [details, diff] libgmail-0.1.5.1.ebuild patch This patch incorporates the latest changes I've made to the ebuild I submitted.
Aggelos, why do we need the "this is believed to violate the gmail terms of use" footnote? The gmail developers said it was fine to use this when it was first added to portage. Please see bug #62100 for the previous debate on this issue (and reasons on why it took so long to initially add this package to portage). Reopen this bug or create a new one if the footnote is needed. Bump in portage.
Hello. I wan't aware of any previous debates on this matter and just thought that having this warning was the right thing to do. AFAIK, any *third party* programs that connect to GMail are violating the GMail Terms of Use -- but then again, I might be wrong. :-)
Just read the debate you are referring to. As I see it, they turn a blind eye on it rather than explicitly say "it's OK". IMHO, this note should stay as-is.
