If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Regression: 10-05-12m11 migration won't write 5.0 prefs

VERIFIED FIXED in M10

Status

MailNews Core
Profile Migration
P1
blocker
VERIFIED FIXED
18 years ago
9 years ago

People

(Reporter: laurel, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Using 1999100512m11 commercial build NT 4.0

After migrating a profile (and using messenger, accessing mail, then quitting),
you're left with just the 4.x prefs in the prefs.js file. No seamonkey prefs are
written/saved.

1.  Migrate a 4.x POP or IMAP profile.
2.  Go to Messenger. Server folders are present.
3.  Exit the application.
4.  Check the prefs.js file in the profile's mail directory for seamonkey.

Result:  the prefs are in 4.x format, no 5.0 prefs translations appear. There
are no prefs to indicate identity numbers. The entire prefs.js is written with
"generic" 4.x prefs based on a single identity.

Logged this as a blocker, because I can't test mailnews pref migration until
fixed.
(Reporter)

Updated

18 years ago
QA Contact: gbush → laurel
(Reporter)

Updated

18 years ago
Priority: P3 → P1
(Reporter)

Updated

18 years ago
OS: Windows NT → All
(Reporter)

Comment 1

18 years ago
changing OS field to All, since I assume this is the case, although mac and
linux current builds don't have installer working so I can't migrate.
Status: NEW → ASSIGNED
-installer (Linux) and Mozilla Installer (mac) are working.

accepting this bug.  working on a fix now.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
fixed checked in.
(Reporter)

Comment 4

18 years ago
This problem appears in linux m10 (1999-10-01-18m10).
This probelm appears in mac m10 (1999-10-01-20m10)
This problem doesn't appear in win32 m10 (1999-10-03-20m10)

putting leger on cc list.

Comment 5

18 years ago
Seth - do you think it's feasible to check your fix into the M10 branch as well
(considering we will have another M10 respin)?

If so, reopen the bug and mark target milestone M10.

Updated

18 years ago
Status: RESOLVED → REOPENED
Target Milestone: M10

Comment 6

18 years ago
seth is going to get this on the branch.
Seth,

SeaMonkey_M10_BRANCH  is the tag to pull for these files
(Reporter)

Comment 7

18 years ago
Verified for m11:
OK using 1999-10-06-08m11 linux 6.0
OK using 1999-10-06-08m11 NT 4.0
OK using 1999-10-06-08m11 mac OS 8.5.1

Updated

18 years ago
Resolution: FIXED → ---

Comment 8

18 years ago
Great - chris - when do you anticipate another M10 build?
Status: REOPENED → RESOLVED
Last Resolved: 18 years ago18 years ago
Resolution: --- → FIXED
marking fixed.  this fix is now on both the tip and the m10 branch.

Comment 10

18 years ago
Just a fyi,
On the Mac commercial seamonkey build 1999-10-1-20-m10, I was able to get
migrate your imap 4.x prefs to 5.0.  It works for IMAP and for POP I'm seeing.
For IMAP, it automatically wrote the 5.0 prefs.js file if I followed the
following scenarios.
After migrating, I quit apprunner and viewed my prefs.js file and saw it was
still in 4.x format.  I launched apprunner then open Messenger.  I logged in and
viewed a mail message.  I quit and check my prefs.js file.  It was migrated to
5.0 format.

To get my pop prefs to be written, I had to delete the panacea.dat file.  Then
open messenger and log into mail.
your mail prefs won't get migrated from 4.x style to 5.0 style prefs until you
launch mail.

so, until you launch messenger, they will look unmigrated.

I'm going to fix that so they will also get migrated if you open mail compose,
that's already a bug against me.
(Reporter)

Comment 12

18 years ago
OK using 1999-10-06-14m10 mac OS 8.5.1
OK using 1999-10-06-15m10 NT 4.0

Just in case, I will re-verify in the final final (ha!) m10 builds to come out
tonight or tomorrow.

Comment 13

18 years ago
Verified in the mac mozilla 1999-10-07-17-m10 build.  No Mac commercial build
yet.  Have not tried Win or Linux.

Comment 14

18 years ago
Oops.  The Mac mozilla build I tested was 1999-10-06-17-m10.  Sorry...need more
soda... :)

Comment 15

18 years ago
Verified on win32 commercial and mozilla build 1999-10-06-19-m10.
Please note that after you migrate, the 5.0 prefs is not written until you open
Messenger.  If I don't open messenger, my prefs.js is still in 4.x pref format.

No Mac commercial build or linux builds yet.

Comment 16

18 years ago
verified for linux M10 commercial build
-ftp://sweetlou/products/client/seamonkey/unix/linux_glibc/2.2/x86/1999-10-07-16
-M10/

Comment 17

18 years ago
hip, hip, spitzer

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 18

18 years ago
Verified on Mac mozilla and commercial build 1999-10-07-17-m10.
Verified on Linuz mozilla and commercial build 1999-10-07-16-m10.

These are final M10 build (crossing my fingers)
Marking build verified.  Great work Seth :)

Comment 19

18 years ago
Forgot to add...
 Verified on Win32 mozilla and commercial build 1999-10-07-16-m10.  :)
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.