https://bugs.freedesktop.org/show_bug.cgi?id=57061
Stephan Bergmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|[email protected] |[email protected] |desktop.org | --- Comment #15 from Stephan Bergmann <[email protected]> --- (In reply to comment #14) > I guess that the confusion here is caused by the MIGRATION file and Dev > builds. Once you run 4.0 Dev build, it migrates the LibreOffice\3 > configuration and crates the MIGRATED file in the LibreOffice\3 user config > dir. See comment 5: "It appears that on case-insensitive file systems (Mac OS X, Windows), existing '3' user profiles got the 'MIGRATED' flag file (<http://cgit.freedesktop.org/libreoffice/core/commit/?id=995a87e5cf63fe1626245b62fef4aa71fa02dc94> 'disable multiple migrations via MIGRATED stamp file') erroneously added when running LO 3 already, cf. <http://lists.freedesktop.org/archives/libreoffice/2012-February/027058.html> 'User installation migrated onto itself.'" > I am not sure what is the idea behind the MIGRATION file but it has been > there for ages. I guess that it was introduced to avoid another can of worms > when migrating OOo-2.x to OOo-3.x. See commit linked above. I had assumed that the issue with the MIGRATED file had been addressed (<http://lists.freedesktop.org/archives/libreoffice/2013-January/043769.html> "minutes of ESC call ...": "Completed Action Items: need to rename the MIGRATED flag and unwind / test re-migration (Michael): apparently no need to do this - the new directory name takes care of it." But it does not look like the issue is addressed (and I fail to see how the new directory name, LibreOffice\4 on Windows, would take care of anything there). The best solution is probably to either (a) change the name of the flag file from MIGRATED to MIGRATED4 for LO 4 (MIGRATION_STAMP_NAME in MigrationImpl::alreadyMigrated in desktop/soruce/migration/migration.cxx) or (b) get rid of the flag file completely by effectively reverting the commit linked above. Case (a) has the advantage that, when migrating existing user profiles to LO 4 and such a migration leads to a broken LO 4 profile, the user can get out of that by just removing the broken LO 4 profile and starting over. Both cases have the disadvantage that if an old profile already caused migration problems once in the past (but only once, as it was flagged as MIGRATED afterwards), it may cause migration problems now again. I will take care to get solution (a) into libreoffice-4-0-0. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
