Bug 700726 – [i686] Folders are not migrated

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 700726 - [i686] Folders are not migrated

Summary:	[i686] Folders are not migrated

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	evolution-data-server (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Matthew Barnes
QA Contact:	Desktop QE
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	883010
Blocks:	700733
	Show dependency tree / graph

Reported:	2011-04-29 04:34 EDT by Jiri Koten
Modified:	2014-01-02 05:40 EST (History)
CC List:	2 users (show)

See Also:
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 00:02:02 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
evo output (3.50 KB, text/plain) 2011-04-29 04:36 EDT, Jiri Koten	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:1540	normal	SHIPPED_LIVE	Low: evolution security, bug fix, and enhancement update	2013-11-20 19:40:51 EST

Groups: None (edit)

Description Jiri Koten 2011-04-29 04:34:20 EDT

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.

Comment 1 Jiri Koten 2011-04-29 04:36:51 EDT

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)

Comment 2 Milan Crha 2011-04-29 05:55:50 EDT

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.

Comment 3 Matthew Barnes 2011-04-29 13:34:28 EDT

Sounds like a dupe of bug #696881 to me.

Comment 4 Matthew Barnes 2011-04-29 13:36:36 EDT

Oh nevermind, I see what you're doing.  Didn't read through all my bugzilla spam.

Comment 5 RHEL Product and Program Management 2011-07-05 21:07:06 EDT

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.

Comment 6 Milan Crha 2013-05-09 14:13:33 EDT

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.

Comment 8 Tomas Pelka 2013-05-10 13:09:38 EDT

(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.

Comment 11 Milan Crha 2013-06-18 13:42:28 EDT

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.

Comment 19 errata-xmlrpc 2013-11-21 00:02:02 EST

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

Note You need to log in before you can comment on or make changes to this bug.