MozillaZine

Migration of profiles prior to SM 2.0 removed with 2.8

Discussion about Seamonkey builds
rsx11m
Moderator
 
Posts: 14425
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted September 26th, 2011, 9:53 am

So, Mozilla Core wants to get rid of some functionality which was necessary to import/migrate profiles prior to Firefox 0.9.x stored in the Mozilla Suite style (bug 679352). There is a corresponding Thunderbird version (bug 689120) to remove that functionality from comm-central as well. My guess is that it somehow (i.e., equally) would affect SeaMonkey as well.

Consequences? Starting with, let's say, SM 2.6, profiles from SeaMonkey 1.x, Netscape 6.x/7.x, and early (pre-toolkit) Firefox/Thunderbird version would no longer be recognized and migrated to the new format used since 2.0 (which was introduced much earlier by Firefox/Thunderbird).

Workaround: Users on 1.x or earlier would have to migrate to 2.[0-5] first, then update to 2.6 or later to be current.

I'm wondering how many users are actually still on SM 1.x or Netscape/Suite versions, thus would be affected by dropping that migration code... :-k
Last edited by rsx11m on December 11th, 2011, 2:46 pm, edited 2 times in total.

rsx11m
Moderator
 
Posts: 14425
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted September 27th, 2011, 7:19 am

Ok, this is bug 689437 for SeaMonkey now. Anybody having concerns about this step should comment in either of these bugs.

rsx11m
Moderator
 
Posts: 14425
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted December 11th, 2011, 2:49 pm

The changes on the core side have been checked in last night (bug 679352), so this will become effective with SeaMonkey 2.8 for sure.

Trunk builds are currently busted due to this change, thus no 2.8a1 nightlies at this time.

Arlene Bingham
 
Posts: 1
Joined: October 21st, 2012, 7:38 am

Post Posted October 21st, 2012, 7:42 am

I am a newbie but would like to ask a question about this bug 679352. How does it effect mozilla's functionality?
Last edited by rsx11m on November 7th, 2013, 1:34 pm, edited 2 times in total.
Reason: Removed commercial links

rsx11m
Moderator
 
Posts: 14425
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted October 22nd, 2012, 5:29 pm

This should only be relevant if you are migrating from an older version (i.e., SeaMonkey 1.x, the old Mozilla Suite, or Netscape 6.x/7.x) to a current SeaMonkey release. In this case, you'd have to install, e.g., SeaMonkey 2.0.14 first to migrate that profile to the new format, then install a current release over it which should perform any remaining migration steps.

This has only an effect for migration tasks and shouldn't have any impact on day-to-day work.

Return to SeaMonkey Builds


Who is online

Users browsing this forum: No registered users and 1 guest