Tagged v6.5.6-RC1

[Eygene Ryabinkin]

Tomasz, good day.

Thu, May 22, 2014 at 09:57:24PM +0200, Tomasz Żok wrote:
> On 2014-05-22 at 20:01, Eygene Ryabinkin wrote:
> > Intend to roll out 6.5.6 Really Soon (tm), perhaps even today
> > or tomorrow.  So, if anyone has some concerns about -RC --
> > please, speak up.
> 
> OfflineIMAP v6.5.6-rc1 throws exception and displays this stacktrace:
> 
> Exception in thread Thread-16:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
>     self.run()
>   File "/usr/lib/python2.7/threading.py", line 763, in run
>     self.__target(*self.__args, **self.__kwargs)
>   File "/usr/lib/python2.7/site-packages/offlineimap/imapserver.py", line 706, in __idle
>     imapobj.__idle(callback=callback)
>   File "/usr/lib/python2.7/site-packages/offlineimap/imaplib2.py", line 404, in __getattr__
>     raise AttributeError("Unknown IMAP4 command: '%s'" % attr)
> AttributeError: Unknown IMAP4 command: '_IdleThread__idle'
> 
> And, unsurprisingly, the IDLE for my accounts does not work :), I have to wait
> for the sync to get my e-mail

Fixed in next/0005bcb2f013082ae13f3a466a8b3a9d75e7dea7,
  https://github.com/OfflineIMAP/offlineimap/commit/0005bcb2f013082ae13f3a466a8b3a9d75e7dea7.diff
Can you test this modification before it will go to the master?

> Also, as a side note:
> - The link to v6.5.6-rc1 tag on http://offlineimap.org/ points to GitHub 404
>   page
> - The link to "release tarballs" points to a page which says "There aren’t any
>   uploads for this repository". The link should point to
>   https://github.com/OfflineIMAP/offlineimap/tags

Will try to address these points today.

> - The Makefile in the tarball should IMHO use "python2" instead of "python"
>   command. More and more linux boxes have Python 3 installed as /usr/bin/python
>   and the current OfflineIMAP is only Python2-compliant (well, at least the
>   setup script *is*, but AFAIR the main application was also not Python3-ready
>   some time ago - correct me if I'm wrong). Using "python2" is more robust
>   since this will not interfere with older systems (i.e. those where
>   /usr/bin/python == /usr/bin/python2)

Not every distribution has 'python2' executable.  For example, FreeBSD
ports collection dating back to 2010 has no python2, just python 2.X
executables.  So, the proper thing will be to fix OI to be
Python3-compatible and to stay Python2-compatible.  I believe it
should take some time and testing, but I am marking as the viable item
for the next releases.

Thanks a lot!
-- 
rea