| Summary: | [i686] Folders are not migrated | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jiri Koten <jkoten> | ||||
| Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.1 | CC: | mcrha, tpelka | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | evolution-data-server-2.32.3-6.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-11-21 05:02:02 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | 883010 | ||||||
| Bug Blocks: | 700733 | ||||||
| Attachments: |
|
||||||
|
Description
Jiri Koten
2011-04-29 08:34:20 UTC
Created attachment 495733 [details]
evo output
Evolution output when running from console.
[snip]
(evolution:4964): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:4964): camel-WARNING **: Cannot load summary file: Success
em-migrate.c:2961:migrate_to_db: failed to get folder infos
addressbook_migrate (2.12.0)
Thanks for a bug report. This might be it:
> (evolution:4964): camel-WARNING **: Cannot load summary file: Success
> em-migrate.c:2961:migrate_to_db: failed to get folder infos
What architecture is the source RHEL5, please? I believe it's 64bit. The thing is that summary in RHEL5.x is a binary file, architecture dependant, so if you use such backup [1], then the pointer sizes doesn't match and a failure occurs. It's not much problem with IMAP accounts (in a sense of nothing lost, everything is stored on a server), but for local accounts, like POP or basically anything under On This Computer it is a problem (the summary might be recreated on the next start, but, if I recall correctly, it sometimes crashes due to this incompatibility too).
[1] backup utility is pretty simple, it just invokes couple commands at the background, it doesn't do any processing on them. It even cannot, as each provider or backend can use its own cache mechanism.
Sounds like a dupe of bug #696881 to me. Oh nevermind, I see what you're doing. Didn't read through all my bugzilla spam. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Jirko, would it be possible to get a zipped test home folder with configured evolution, on which the bug will be reproducible, please? If the rebase bug (bug #883010) will make it in, then it'll be good to make sure users will migrate without any issue, from both RHEL 5.6 and evo/eds-2.28.3. (In reply to comment #6) > Jirko, would it be possible to get a zipped test home folder with configured > evolution, on which the bug will be reproducible, please? If the rebase bug > (bug #883010) will make it in, then it'll be good to make sure users will > migrate without any issue, from both RHEL 5.6 and evo/eds-2.28.3. Setting NEED_INFO to get Jirka's attention. The two problematic types are off_t, time_t and gsize, all differ in size. On i386 they are 4 bytes, while on x86_64 they are 8 bytes. The main code resides in evoltuion-data-server, thus I move this there. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1540.html |