Bug 1867

Summary: Migration of evolution from Mandriva 2010.0 to Mageia 1 fails if .evolution is a symlink to another partition.
Product: Mageia Reporter: Edward d'Auvergne <true.bugman>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WONTFIX QA Contact:
Severity: minor    
Priority: Normal CC: dmorganec, fundawang, marja11, remco, stormi-mageia
Version: 1   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: evolution CVE:
Status comment:

Description Edward d'Auvergne 2011-06-20 11:39:23 CEST
Description of problem:

The migration of evolution data from Mandriva 2010.0 to Mageia 1 fails for my setup.  In my old setup, ~/.evolution was a symlink to a folder on another data partition, as the quantity of data was too great for my /home partition.  However the upgrade process fails with symlinks.  There is no clear way of fixing this, as the upgrade attempts to shift all of the evolution data into ~/.config and ~/.local.  The problem appears as:

[edward@localhost ~]$ evolution                                                                                                          
Migrating cached data
  mv /home/edward/.evolution/cache/http /home/edward/.cache/evolution/http
  FAILED: Invalid cross-device link
  mv /home/edward/.evolution/cache/tmp /home/edward/.cache/evolution/tmp
  FAILED: Invalid cross-device link
  rmdir /home/edward/.evolution/cache
  FAILED: Directory not empty (contents follows)
          tmp
          http
Migrating config data
  mv /home/edward/.evolution/calendar/views/current_view-.xml /home/edward/.config/evolution/calendar/views/current_view-.xml
  FAILED: Invalid cross-device link

This is repeated for all config and data files.  Some other messages are:

  mv /home/edward/.evolution/key3.db /home/edward/.local/share/evolution/key3.db
  FAILED: Invalid cross-device link


As not many people will have the .evolution folder on a different partition as /home, this will not affect many people.  For those affected though, it appears as if all data is lost from the program.  And many error messages are given.


Version-Release number of selected component (if applicable):


How reproducible:

100%


Steps to Reproduce:
1.  Move an old copy of .evolution to a different partition.
2.  Make a symlink to the moved folder.
3.  Run evolution from the prompt.
Samuel Verschelde 2011-10-01 18:00:54 CEST

CC: (none) => stormi
Source RPM: (none) => evolution

Comment 1 Marja Van Waes 2011-12-03 13:20:53 CET
Is this an issue when upgrading from Mga1 to Mga2alpha1, too?

CC: (none) => dmorganec, fundawang, marja11

Comment 2 Marja Van Waes 2012-01-25 21:44:35 CET
cc'ing one more evolution committer.

CC: (none) => jani.valimaa

Remco Rijnders 2012-02-29 06:46:00 CET

CC: (none) => remco

Jani Välimaa 2012-04-28 10:05:18 CEST

CC: jani.valimaa => (none)

Comment 3 Manuel Hiebel 2012-11-05 16:52:35 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 4 Manuel Hiebel 2012-12-02 14:32:06 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX