Control: tags -1 fixed-upstream

Hi Paul,

On Thu, Sep 15, 2016 at 06:39PM, Paul Wise wrote:
> Since the recent update I can no longer use offlineimap because it
> crashes with the sqlite status_backend and there doesn't appear to be
> any way to convert an existing status cache from the sqlite backend to
> the plain text backend.
> [...]
> ERROR: Exceptions occurred during the run!
> ERROR: While attempting to sync account '[email protected]'
>   'LocalStatusSQLiteFolder' object has no attribute 'purge'
> 
> Traceback:
>   File "/usr/share/offlineimap/offlineimap/accounts.py", line 263, in 
> syncrunner
>     self.__sync()
>   File "/usr/share/offlineimap/offlineimap/accounts.py", line 329, in __sync
>     remoterepos.sync_folder_structure(localrepos, statusrepos)
>   File "/usr/share/offlineimap/offlineimap/repository/Base.py", line 253, in 
> sync_folder_structure
>     src_repo.getsep(), status_repo.getsep()))
>   File "/usr/share/offlineimap/offlineimap/repository/LocalStatus.py", line 
> 97, in makefolder
>     folder.purge()

This is due to the following commit[1]:

| commit 038a433f69c5fae1631d00a81cba0b15e5038b32
| Author: Nicolas Sebrecht <[email protected]>
| Date:   Mon Jul 25 14:39:11 2016 +0200
| 
|     backport: sqlite: properly serialize operations on the databases

Upstream tried to backport a fix, but it seems that the purge() method
is not defined in version 6.7.0.3. Converting your status_backend to
plain will not help here, since purge() method is not defined for this
backend either. It was introduced by the following commit[2]:

| commit 1410a391bcec3d500ee61f4c42371c6630d726e7
| Author: Nicolas Sebrecht <[email protected]>
| Date: Fri, 17 Jun 2016 19:47:37 +0200
| 
|     Subject: [PATCH] avoid removing of data when user removed a maildir


I will try to upload the latest version of OfflineIMAP ASAP.

Best,
Ilias

[1] https://github.com/OfflineIMAP/offlineimap/commit/038a433f69c5fae1631d00a81c
[2] 
https://github.com/OfflineIMAP/offlineimap/commit/1410a391bcec3d500ee61f4c42371c6630d726e7#diff-c23c6906c765513bcd9008c1b49f6746R91

Reply via email to