Hide Forgot
Description of problem: When migrating Evolution settings from RHEL5.6 to RHEL6, folders are not migrated. "Migrating folders" window quickly popups but close itself immediately, no progress is shown. After Evolution starts no folders are displayed until it gets connected to mail server. This somehow effects only i686 arch, because on x86_64, ppc64 migration of folders is successful. Version-Release number of selected component (if applicable): evolution-2.28.3-24.el6.i686 How reproducible: 100% Steps to Reproduce: 1.Backup client evolution settings on RHEL5.6 Workstation 2.Open evolution on newly installed RHEL6, and perform a restore operation for evolution-backup.tar.gz created in step #1 Actual results: No folders after migration. Expected results: Folders are successfully migrated. Additional info: Testing this should just be a matter of setting up some kind of IMAP account on RHEL 5, letting Evolution download summary info for your mail folders so it has data to migrate, and then upgrading to RHEL 6 and running Evolution.
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